TA的每日心情 | 擦汗 2017-5-18 09:45 |
---|
签到天数: 29 天 连续签到: 1 天 [LV.4]偶尔看看III
中级会员
- 积分
- 419
|
楼主 |
发表于 2016-6-1 11:40:31
|
显示全部楼层
Issue/Symptoms:
Browses with more than 5 minutes of execution time are being timed out with the messages:
Error: Browse Timeout
2013-11-14 11:11:17, ERROR, [0], QAD.Browse.AutoCancel.LogKill(3), Stop Requested: <Browse Name> - xxbr999.p, 5
Facts/Environment:
QAD .Net UI 2.9.4 Cumulative Patch 7
Environment was migrated from QAD .Net UI 2.8.1 to 2.9.4
TreatGetAllAsOneRequest parameter in client-session.xml is set to True
<timeout browseId=/> parameter is not set.
client-session.xml
Root Cause:
To control long running browses, a time limit on how long an appserver agent can be tied up running a browse has been implemented. So, if the running browse exceeds this limit, the browse will time out.
Resolution/Fix:
In the Browse section of the client-session.xml file the block below can be added:
<Notification>
<!-- NotifyRole indicates which users get notified on any browse alert
users with this role will be notified via the inbox.
-->
<!-- Browse Timeout section
browseId : regular expression to select browse(s)
Blank indicates default
warnAt : messages will be sent to users with the above role
when a browses waits this time (minutes)
0 indicates no warning
Warning will continue at this interval
cancelAfter : Browse will be stopped after this interval (minutes)
0 indicates no cancel
Default is no warnings and a 5 minute cancel for all browses
-->
<NotifyRole></NotifyRole>
<timeout browseId="" warnAt="0" cancelAfter="0"></timeout>
<!-- Add additional specific browse setting as required.
<timeout browseId="pp100" warnAt="2" cancelAfter="5"/>
<timeout browseId="so*" warnAt="2" cancelAfter="5"/>
-->
</Notification>
If this setup, browses should no longer being timed out automatically.
The browse timeout is controlled by the value set at cancelAfter. It can be set for all browses when the timeout browseId ="". Note that modifying cancelAfter to 0 may have an impact in the system resources for keeping longer the browse active.
Article Properties
Article Type: Functional
Review Status: Unverified
Notes: No
How to resolve browse time out error in the dialog on the NetUI Java applet.
Author: QAD Support Article ID: AA-08735 Views: 414 Created: 08-09-1999 06:12 PM Last Updated: 01-31-2008 02:41 PM 0 Rating/ Voters
goal: How to resolve browse time out error in the dialog on the NetUI Java applet.
symptom: Error: Browse Timed Out.
symptom: Time out messages when scrolling through NetUI browses.
fact: NetUI
fact: Java applet
fact: MFG/PRO 9.0 and above
fact: Error: Browse Timed Out.
cause: Each NetUI user ID record has a separate browse timeout setting, expressed in minutes. The default is 2 minutes, which probably won't be enough.
fix: To change the timeout setting, run 36.20.10.1, User Option Maintenance (mgusromt.p), and increase the "Browse Timeout" field value. Note: The timeout period will be extended if the user requests another block of records within the timeout period by scrolling past the last record in the browse data window.
Article Properties
Article Type: Functional
Review Status: Verified
Original Solution ID: 1.0.10678057.2268863
|
|