An unexpected error occurred in the SFO server. (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, requested J2EE server = gg....gg : hh....hh, last updated J2EE server = ii....ii : jj....jj, request = kk....kk, error reason = ll....ll)
- aa....aa: J2EE application name
bb....bb: Context root name
cc....cc: Global session ID
dd....dd: Last accessed time of 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 the request to the SFO server resulted in an error
hh....hh: Server name of the J2EE server in which the request to the SFO server resulted in an error
ii....ii: IP address of the J2EE server in which the global session was last updated
jj....jj: Server name of the J2EE server in which the global session was last updated
kk....kk: Contents of the request from the J2EE server
ll....ll: Maintenance information
- Description
- An unexpected error occurred in the SFO server while the request from the J2EE server was being processed.
- The contents of the request from the J2EE server will be output to ff....ff. The output messages and their meaning is described below:
- create from the initial HTTP session
- A global session is created from the new HTTP session that was created on the J2EE server.
- create from the existing HTTP session
- A global session is created from the HTTP session that already exists on the J2EE server. In such a case, the J2EE server disconnects once from the SFO server, and then re-connects.
- 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.
- unlock
- The global session information present on the SFO server is updated and released when the request processing on the J2EE server is finished.
- invalidate
- The global session information present on the SFO server is discarded because the HTTP session was discarded on the J2EE server.
- update the last accessed time
- After locking the global session on the J2EE server, only the last accessed time of the global session present on the SFO server is updated since a request with the same session ID was received during the request processing.
- Action
- Make sure that other error messages are not output in the log of SFO server. If error messages are output, take action as per the contents of the error message. If no error message is output, the followings might be the causes. Take action based on the following causes:
- A problem occurred in the host in which the J2EE server is running.
Remove the cause of the problem occurred in the host.
- A problem occurred in the communication path between the J2EE server and the SFO server.
Remove the cause of the problem that occurred in the communication path.
- A problem occurred in the host in which the J2EE server is running.
Remove the cause of the problem occurred in the host.
- If no problem exists, acquire the maintenance information, and then contact maintenance personnel.
All Rights Reserved. Copyright (C) 2012, 2013, Hitachi, Ltd.