An attempt to clear the global session information failed because an error occurred during communication with the EADs slave server. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc, application ID = dd....dd, HTTP session ID =ee....ee)

aa....aa: J2EE application name
bb....bb: Context root name
cc....cc: Information of the occurred exception
dd....dd: Application identifier
ee....ee: Session ID of the HTTP session

Descritpion

An attempt to delete the global session information on the copy destination server or delete the invalid global session information has failed, because an error occurred during communication with the copy destination server in the session information.

Action

If this message is output, the global session information of one level above is remained on the copy destination server.

For details on the actions to be taken, see 7.8.2 Deleting the global session information that remains on the EADs server (Copy destination server of the session information) in the uCosminexus Application Server Expansion Guide.

If this message is output, check that the EADs server is operating correctly and that there is no error in the communication route of the EADs and J2EE servers.

If an error occurs on the EADs server, take action according to the restoration procedures for the EADs server. For details on the restoration procedures when an error occurs on the EADs server, see 2.5.4 When an error occurs in the EADs session failover functionality in the uCosminexus Application Server Maintenance and Migration Guide.

If an error occurs in the communication route of the EADs and J2EE server, remove the error.