An attempt to clear the global session information failed because an error occurred in the operation of the EADs server. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc)

aa....aa: J2EE application name
bb....bb: Context root name
cc....cc: Information of the occurred exception

Description

An attempt to delete the global session information or delete the invalid global session information has failed, because an error occurred in communication with the EADs server or in the user functionality that is provided by the EADs session failover functionality.

Action

If this message is output, one or more global session information items remain on the EADs server.

The global session information remaining on the EADs server is inherited by the J2EE server as an available session when the Web application is restarted or when a request with the same session ID is received.

To delete the global session information remaining on the EADs server, use the command for deleting global session information (cjezclearsession command). For details on how to delete global session information, see 7.8.1 Deleting global session information on the EADs server (session information storage destination server) in the uCosminexus Application Server Expansion Guide.

If this message is displayed, check whether the EADs server is running normally, and whether there is any problem in the communication channel between the EADs server and J2EE server.

If an error occurs on the EADs server, take action based on the EADs server restoration procedures. 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 there is a problem in the communication channel between the EADs server and the J2EE server, resolve the problem.

Also, check whether the user application JAR files provided by the EADs session failover functionality are allocated to the EADs server, and whether any invalid operations are being performed for the EADs server from an external source.