A timeout occurred during a lock request. The rewritable global session information was removed from the HTTP session. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, HTTP session ID = ee....ee, global session ID = ff....ff, locked J2EE server name = gg....gg, locked J2EE server IP = hh....hh)

aa....aa: J2EE application name
bb....bb: Context root name
cc....cc: SFO server name
dd....dd: Address and port number of the Naming Service
ee....ee: HTTP session ID
ff....ff: Global session ID
gg....gg: Server name of the J2EE server in which the global session is locked
hh....hh: IP address of the J2EE server in which the global session is locked

Description

This global session cannot be used because a timeout occurred during a global session lock request to the SFO server.

The rewritable global session information registered in the HTTP session was deleted.

Take action based on the following causes:

• Either the J2EE server in which the global session is locked has slowed down, or has stopped.
• When a request is sent before the response of the previous request is returned, both the requests will be forwarded to different J2EE servers by the schedule functionality of the load balancer. This occurs when requests using the same session are sent simultaneously while using the frames in a page or when a request is sent twice due to the user operation.

Action

Check the working state of the J2EE server in which the global session is locked. 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.