A memory shortage occurred in the SFO server. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

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 on the SFO server

Description

A memory shortage occurred in the SFO server during the negotiation with the SFO server. Take action based on the following causes:

• The memory of SFO server is insufficient.
• The maximum size of the global session information set in the Web applications on the J2EE server is large.
• The maximum value for the number of HttpSession set in the J2EE server is inappropriately large.

Action

Take the following actions depending upon the cause:

When the memory of the SFO server is insufficient

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 6. 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 option definition file (usrconf.cfg) for the J2EE server, 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, and then redeploy the J2EE application.

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.