There is not enough memory to start replicating the global session information. (J2EE application = aa....aa, context root = bb....bb, max sessions = cc....cc, max session info size = dd....dd)

aa....aa: J2EE application name
bb....bb: Context root name
cc....cc: Maximum number of global sessions
dd....dd: Maximum value (in bytes) of the size of global session information

Description

Sufficient memory is not available to start replicating the global session information.

Take action based on the following causes:

• The estimation of memory usage set in the SFO server is wrong
• The maximum size of the global session information set in the Web application present on the J2EE server is large
• The maximum value of the number of HttpSession set in the J2EE server is inappropriately large

Action

Take the following actions depending upon the cause:

When the memory usage set in the SFO server is wrong

Revise the estimation of the memory required in the SFO server.

The memory required in the SFO server is proportionate to the maximum number of global sessions, and the maximum size of the global session information. For details, see 7. Memory Session Failover Functionality in the manual Cosminexus Application Server Function Guide - Expansion.

In the case of a problem in setting the required memory, set the appropriate value in the JavaVM definition file (usrconf.cfg), and then restart the SFO server.

When the maximum size of the global session information is large

Revise the maximum size of the global session information set in the Web application.

In the case of a problem in the maximum size of the global session information, set the appropriate value in the Deployment Descriptor (web.xml) of the Web application.

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.

When the maximum value of the number of HttpSession is large

Revise the maximum value of the number of HttpSession set in the Web application.

If the maximum value of the number of HttpSession is more than required, change to an appropriate value, and then restart the J2EE application.