| Author |
Message
|
| Yemi |
 Posted: Tue Feb 04, 2003 3:41 am Post subject: Intepreting WebClient Logs |
 |
|
Newbie
Joined: 04 Sep 2002
Posts: 6
|
Hi All,
I'm trying to troubleshoot a session management problem but need help understanding the logs generated by webclient.
Is there anyone out there with information that can help?
Also, has anybody encountered and solved the following exception before?
========
2003-02-03 14:38:32.951 Servlet.Engine.Transports:9: doGet (queryWorkItems): com.ibm.workflow.servlet.client.NoSessionException: No active session available.
com.ibm.workflow.servlet.client.NoSessionException: No active session available.
========
Note that this happens intermittently.
Any help/infor will be appreciated
Yemi |
|
| Back to top |
|
 |
| yaakovd |
| Posted: Tue Feb 04, 2003 11:56 pm Post subject: |
|
|
Partisan
Joined: 20 Jan 2003
Posts: 319
Location: Israel
|
This error appears when your session expired on WEB Server.
default expiration time on most of servers is 30 min. When you take a long coffebrake, just log in again 
You van increase this parameter on server or implement some automatic reconnect mechanism.
_________________
Best regards.
Yaakov
SWG, IBM Commerce, Israel |
|
| Back to top |
|
|
| kriersd |
| Posted: Sat Feb 08, 2003 9:01 am Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Hello..
We see this message a lot in our logs. It's really nothing to worry about. We probably see it more offten than most because we use the command stacking to our advantage.
Here is why we see a bunch of these messages.
We designed our system to send and email with a link to a custom command within our Workflow Web client at the activity step just before any JSP human activity step. The link is a direct link to a command that will either open up an existing private work list or build the work list and then open it up. Because the user does not have an existing session the Web Client will throw up the sigon page and cash the original URL that was passed in. Once the user completes the logon page the original URL is then automaticly sent to the server. In the documentation they call this STACKING the commands. This is exactly what happens when you come back from lunch hit the submit button and see the logon screen. If you actually look at the html when this happens you'll notice some extra parms like COMMAND2.
Go a head and give it a try..
You can simulate it your self by stacking the logon command with the logoff command.
http://yourdomain.com/MQWF_WebClient/servlet/Main?command=logon&userID=admin&password=password&command2=logoff
Good luck..
Dave
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| mkhadse |
| Posted: Thu Feb 20, 2003 10:37 am Post subject: |
|
|
Acolyte
Joined: 31 Dec 1969
Posts: 73
|
I have not seen this exception before, but if this is not due to the webserver's session timeout, you can look at the domain's session timout value defined in the buildtime.
Look at the properties of DOMAIN or SYSTEM GROUP or SYSTEM and select the SESSION tab.
Hope it helps. |
|
| Back to top |
|
|
| yaakovd |
| Posted: Thu Feb 20, 2003 10:44 am Post subject: |
|
|
Partisan
Joined: 20 Jan 2003
Posts: 319
Location: Israel
|
Milind,
| Quote: |
| 01/27 12:54:48 error (JRun) doGet (queryWorkItems): com.ibm.workflow.servlet.client.NoSessionException: No active session available. [com.ibm.workflow.servlet.client.NoSessionException: No active session available.] |
This is from JRun\logs\fmc_event.log
_________________
Best regards.
Yaakov
SWG, IBM Commerce, Israel |
|
| Back to top |
|
|
|
|
