A timeout occurred during a lock request. (J2EE application = aa....aa, context root = bb....bb, global session ID = cc....cc, last accessed time = dd....dd, max inactive interval = ee....ee, session info size = ff....ff, lock timeout J2EE server = gg....gg : hh....hh, locked J2EE server = ii....ii : jj....jj, request = kk....kk)

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: Size (in bytes) of the global session information
gg....gg: IP address of the J2EE server in which a timeout occurred during the lock request
hh....hh: Server name of the J2EE server in which a timeout occurred during the lock request
ii....ii: IP address of the locked J2EE server
jj....jj: Server name of the locked J2EE server
kk....kk: Contents of the request from the J2EE server

Description

A timeout occurred during the request for locking the global session.

The locked J2EE server might have either slowed down or stopped.

The contents of the request from the J2EE server will be output in kk....kk. The output messages and their meaning is described below:

get

The global session information is acquired from the SFO server, since the HTTP session does not exist on the J2EE server.

lock

The HTTP session exists on the J2EE server. To process the request, the global session present on the SFO server is locked.

Action

Check the working state of the locked J2EE server.

If no problem exists in the working state of the locked J2EE server, confirm that the set value for lock timeout is appropriate.

To change the settings, 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. Create and start J2EE applications from the Web application in which the settings have been applied.