A new global session cannot be created because the number of global sessions has reached the maximum. (J2EE application = aa....aa, context root = bb....bb, max sessions = cc....cc, J2EE server = dd....dd : ee....ee, request = ff....ff)

aa....aa: J2EE application name
bb....bb: Context root name
cc....cc: Maximum number of global sessions
dd....dd: IP address of the J2EE server that requested the creation of a global session
ee....ee: Server name of the J2EE server that requested the creation of a global session
ff....ff: Contents of the request from the J2EE server

Description

There was a request for creation of a global session from the J2EE server, but, since the number of global sessions has reached the maximum value, a new session cannot be created.

The contents of the request from the J2EE server will be output to ff....ff. The output messages and their meaning is described below:

create from the initial HTTP session

A global session is created from the new HTTP session created on the J2EE server.

create from the existing HTTP session

A global session is created from the HTTP session that already exists on the J2EE server. In such a case, the J2EE server disconnects once from the SFO server, and then re-connects.

Action

If you want to create a global session, revise the maximum value of the number of HttpSession and the validity period of the HTTP sessions.

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.