| Author |
Message
|
| drgincbia |
 Posted: Fri Feb 27, 2004 12:45 pm Post subject: WebClient Times Out While in Web Application |
 |
|
Apprentice
Joined: 23 Dec 2003
Posts: 35
Location: Omaha NE
|
Some of the java applications associated with an activity in the WebClient take considerable time, so by the time you are ready to go back to the worklist (approx 15 minutes), it says the session has expired and reverts you back to the logon screen.
Can anyone tell me how to adjust this timeout value? (maybe HTTP Session?) The end users will not want to log back in all of the time.
Any help would be appreciated.
_________________
D. Grandia |
|
| Back to top |
|
 |
| jmac |
| Posted: Fri Feb 27, 2004 1:44 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Are you not using checkout/checkin? It just seems strange to me that you are doing something that takes more than 3 minutes which is what the default is.
If you want to change the time you can, the method is:
| Code: |
| Service::setTimeout(int TIMEOUT) |
 NOTICE that I beat out Venny by 1 second 
_________________
John McDonald
RETIRED
Last edited by jmac on Fri Feb 27, 2004 1:49 pm; edited 1 time in total |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Feb 27, 2004 1:45 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| There is a method called setTimeout in the ExecutionService. You can set the timeout value. |
|
| Back to top |
|
|
| drgincbia |
| Posted: Mon Mar 01, 2004 5:49 am Post subject: TimeOut |
|
|
Apprentice
Joined: 23 Dec 2003
Posts: 35
Location: Omaha NE
|
From the WebClient a checkout is done to process a work item. However, the amount of processing going on within java applications (called from the workflow jsp) while the item is checked out can be quite extensive. When processing is complete for that step, the user selects a button on the jsp that does a check in of the work item. The browser bounces out to the Logon page with a message 'You are not yet logged on or your session has expired'. This is where our workflow customer wants us to override a value so they don't have to log in again.
Where is the Execution Service SetTimeout method set that you are referring to? Does this apply to the WebClient vs a Java program running on the fat cleint? In the FDL the Domain, Session tab, the Session expiration time is 20 hours.
Any assistance is appreciated!
_________________
D. Grandia |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Mar 01, 2004 5:58 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
These ar 2 different values:
Session Expiration, is NOT affected by setTimeout().
The setTimeout affects the 3 minutes that you get by default. I don't believe this value is specified anywhere in the Network hierarchy.
However, I don't think that this is your problem in the case where setTimeout would help you would be getting the FMC_ERROR_TIMEOUT rc=14 value.
Are you sure that there is not a logoff being done someplace? Or maybe a logon, with PRESENT_HERE for this user that is forcing the user off?
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| drgincbia |
| Posted: Mon Mar 01, 2004 6:08 am Post subject: Timeout |
|
|
Apprentice
Joined: 23 Dec 2003
Posts: 35
Location: Omaha NE
|
I log on using my network ID, so no one other than me is logging on / off with my ID.
Just this morning when I was trying to find out the exact message to put in the reply, I logged onto the WebClient, checked out a work item, then went off and worked on something else (not workflow related). I went back to my workflow session, typed in some data values, and selected to check in my work item. I was promptly returned to the logon page instead of my worklist with the error I listed above.
_________________
D. Grandia |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Mar 01, 2004 6:33 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
This is probably your AppServer that is timing out. I really don't have much experience in this area, but maybe one of our other readers will have your answer.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| praveenchhangani |
| Posted: Mon Mar 01, 2004 1:38 pm Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
Hi drgincbia
I understand that some applications(steps in particular) take longer than others interms of processing time, however,
I also think that if a step is taking that much time to process there are a few things to consider and you probably
are already aware of these, but let's just make sure...
1.) Important or non-important step (Synchronous=imp or Asynchronous=nonimp) - If the step is important and you want to
keep track of the data and perhaps use it for the next step then the step is synchronous, otherwise it's not. In Synchronous
processing, workflow expects a return code/condition which is evaluated in the workflow runtime engine and reacts to that
condition based on your process model design. If you have declared that step to be as that of an asynchronous step then,
workflow will not wait for a return code/condition on the execution of the step and will simply move on.
PS: Yours sounds more like the Synchronous processing. Now although there are ways such as looking into the API, however
try to revert from that if you are able to, because a 20 minute timeout I believe is a default and there are reasons related
to security as to why IBM has that time out figure in place. At anyrate, I would recommend the following in order to deal
with something of this nature:
a) Examine the application(java) to see if it can be made faster (i.e. more server power, memory, multi-threading, application
load testing to encounter bottlenecks and fixing those bottlenecks.) Usually this is hard to do because of lack of time to
perform modifications, lack of access to the application(s) requiring such modifications.
b) Modify your workflow - Don't be afraid to make use of some of the life saving features included in the workflow product
such as suspending of workitems, expiries etc. Again this is another tough task as modifying the process model can be
quite the task in itself ...especially if the model contains multiple steps that are also faced with the timeout issue.
c) Examine your infrastructure - Refer to the workflow best practices guide to see if performance tuning and things like
database maintenance improves application response time, other such related measures...
d) Make use of the API as the other highly knowledgeable members of this forum are recommending, however sometimes making use of such
API calls can come back to haunt one.
Typically a webpage step should not take that long, but if it has to, it has to.
From the sounds of it, I think this is a workflow thing. I could be wrong here, but I believe that the workflow webclient
by default timesout after 20 minutes, after which a re-logon is required back.
Also are you making use of any J2EE frameworks in conjuntion with workflow. Are you running on websphere, what version?
Any specifics on the application in itself and any other workflow details you can think of? Are you making use of any
authentication exits? Are there any LDAP authentication settings that workflow is communicating to on your system?
Sorry I can't think of anything else right now!
Good luck!
_________________
Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
| Back to top |
|
|
| dsim |
| Posted: Mon Mar 01, 2004 8:45 pm Post subject: |
|
|
Acolyte
Joined: 11 Aug 2003
Posts: 67
Location: Toronto
|
As John said above:
| Quote: |
| This is probably your AppServer that is timing out. |
You can try to increase the Http session expiration time. For WAS I think the default is 30 minutes ... it can be changed in the admin console.
Dan |
|
| Back to top |
|
|
| newbiedude |
| Posted: Tue Mar 02, 2004 2:21 pm Post subject: |
|
|
Voyager
Joined: 22 Dec 2002
Posts: 87
|
This I think is more of a workflow deal cos I got similar activities with WAS 5 and my app servers aren't timing out. Re-examine your flow. Now ofcourse if the app server itself is having issues, then that's a whole different ball game in itself. i personally don;t think it's a WAS issue. i could be wrong too..
_________________
Newbiedude |
|
| Back to top |
|
|
| drgincbia |
| Posted: Wed Mar 03, 2004 5:15 am Post subject: Timeout |
|
|
Apprentice
Joined: 23 Dec 2003
Posts: 35
Location: Omaha NE
|
We changed the timeout value on the workflow JVM (reduced it from 30 minutes to 2 minutes), but the web client did not fail until 7 minutes. I did not get the browser logon page with the message 'You are not yet logged on or your session has expired'; instead I got a 'The page cannot be displayed' with the HTTP 500 - Internal server error.
That leads me to believe the JVM setting is not the one in control. Since it previously reverted to the workflow Logon screen, it seems like it is within workflow somewhere.
_________________
D. Grandia |
|
| Back to top |
|
|
| jmac |
| Posted: Wed Mar 03, 2004 5:33 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Being off by 5 minutes is somewhat suspicious since that is what the Check Interval is for the Admin server checking on all the WF components. Maybe you need to open a PMR on this.
GOOD LUCK, and keep us posted on the results.
Thanks
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
|
|
