The global session ID was not found in the SFO server. An attempt to transfer the global session has failed. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee, GS control = ff....ff)
- 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: Global session ID
ff....ff: Method of acquiring the global session ID
For cookie, acquire from the HTTP Cookie of the request
For url-rewriting, acquire from the path parameter of the request URL
- Description
- The global session cannot be inherited because it was not found in the SFO server.
- Take action based on the following causes for not finding the global session:
- The validity period has expired.
- The processing in the application present on the J2EE server has already deleted the global session.
- The global session is lost due to restarting the SFO server.
- Action
- Confirm that the value of the validity period set in the HTTP session is correct.
- To change the validity period of the HTTP session, follow the procedure given below:
- Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
- Restart the SFO server.
- Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.
- Create and start J2EE applications from the Web application in which the settings have been applied.
All Rights Reserved. Copyright (C) 2012, 2013, Hitachi, Ltd.