An unlocked global session was discarded because it had expired. (J2EE application = aa....aa, context root = bb....bb, global session ID = cc....cc, last accessed time = dd....dd, max inactive interval = ee....ee, lock request count = ff....ff, J2EE server = gg....gg : hh....hh)

aa....aa: J2EE application name
bb....bb: Context root name
cc....cc: Global session ID
dd....dd: Last updated time of the global session
ee....ee: Validity period of global session
ff....ff: Lock request count for awaiting unlocking
gg....gg: IP address of the J2EE server in which the discarded global session is locked
hh....hh: Server name of the J2EE server in which the discarded global session is locked

Description

A global session, in which the lock is not released, was discarded because of expiry of the validity period. The information of the discarded global session is output.

Take action based on the following causes for expiry of validity period while the lock was still not released:

• The set value of the validity period of HTTP session is inappropriately small.
• The locked J2EE server has slowed down due to some reason, and the processing has not finished during the validity period.
• The locked J2EE server has stopped.

Action

Check the working state of the locked J2EE server. Also, check the validity period of the HTTP session.

To change the validity period of the HTTP session, follow the procedure given below:

1. Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
2. Restart the SFO server.
3. Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.
4. Create and start J2EE applications from the Web application in which the settings have been applied.