Express (Distributed operating systems), v8.0 > Reference > Messages
SESN
SESN0006E: Attempted to create a session while the WAS was stopping.
Explanation This error occurs when a session request is received while the Application Server is stopping. Action Restart the Application Server.
SESN0007E: Attempted to access a session while the WAS was stopping.
Explanation This error occurs when a session request is received while the Application Server is stopping. Action Retart the Application Server.
SESN0008E: A user authenticated as {0} has attempted to access a session owned by {1}.
Explanation The Session Security Integration feature has detected an attempt to access a session by an unauthorized user. Action No user action is required.
SESN0012E: Null key entered. The HttpSession.putValue or HttpSession.setAttribute method was called from a servlet or JSP with a null key.
Explanation The HttpSession.putValue or HttpSession.setAttribute method cannot be called with a null key. Action Fix the servlet or JSP to pass a non-null key.
SESN0013E: Null value entered for key {0}. The HttpSession.putValue method was called from a servlet or JSP with a null value.
Explanation The HttpSession.putValue method cannot be called with a null value. Action Fix the servlet or JSP to pass a non-null value.
SESN0066E: The response is already committed to the client. The session cookie cannot be set.
Explanation The response is already committed to client so the session cookie cannot be sent to client. Action Correct the application to access the HTTP session before writing anything to the response.
SESN0116W: Session identifier {0} has exceeded the max length limit of {1}.
Explanation The value specified for the SessionIdentifierMaxLength property has been exceeded. Action Only set this property if absolutely necessary. If this property is required, set it to the largest value that your installation can tolerate. If still experiencing this problem, it is likely due to repeated failovers. Investigate and fix the root cause of the failovers.
SESN0117I: Global sessions is enabled for Web modules running with the Web container-level session management configuration.
Explanation This message is for informational purposes only. Action If global sessions is not desired, disable global sessions by setting the Servlet21SessionCompatibility property to false.
SESN0118W: Time-based write is enabled with global sessions. Accessing a global session from more than one server or cluster may result in loss of session data integrity.
Explanation The time-based write feature is enabled with global sessions. Unless all Web modules that access the session are in the same server or cluster, session data integrity may be lost. Action Disable the time-based write if Web modules that access global sessions are split across servers or clusters.
SESN0119W: Memory-to-memory replication is enabled with global sessions. Accessing a global session from more than one server or cluster may result in loss of session data integrity.
Explanation The memory-to-memory replication feature is enabled with global sessions. Unless all Web modules that access the session are in the same server or cluster, session data integrity may be lost. Action Disable memory-to-memory replication if Web Modules that access global sessions are split across servers or clusters.
SESN0120I: Web module {0} will not participate in global sessions because the Web container-level session management configuration has been overridden.
Explanation The specified Web module will not participate in global sessions because the Web container-level session management configuration has been overridden either at the enterprise application- or Web module-level. Action If you want the Web module to participate in global sessions, disable the session management configuration specified at the enterprise application- or the Web module-level and restart the server.
SESN0121E: Session crossover detected in Web application {0}. Session {1} was retrieved when session {2} was expected -
Explanation A call to the request.getSession method returned a session other than the requested session. Action More info at:
SESN0122E: Session crossover detected in Web application {0}. Session {1} was referenced by method {2} when session {3} was expected -
Explanation An application referenced a session other than the session associated with the request. Action More info at:
SESN0123E: Session crossover detected in Web application {0}. Session {1} was returned to the client when session {2} was expected -
Explanation A cookie or URL was returned to the client containing a session ID that is not associated with the request. Action More info at:
SESN0124W: Session crossover detection is enabled.
Explanation Checks for session crossover are being initiated. Action For better performance, you may choose to disable these checks by setting the Webcontainer custom property DebugSessionCrossover=false.
SESN0169I: Session Manager found the custom property {0} with value {1}.
Explanation Session Manager will use the specified property and value to control behavior. Action Verify that the specified property and value will result in the desired behavior.
SESN0170W: Session Manager found the custom property {0} with a non-numeric value {1} so it will be ignored.
Explanation Session Manager expected the specified property to contain a numeric value. The property will be ignored. Action Correct the specified property value to make it a valid number.
SESN0171W: Session Manager found the custom property {0} with out-of-range value {1} so it will use {2}.
Explanation Session Manager expected the specified property to have a value within a certain range. Session Manager will use the closest valid value. Action Correct the specified property value to make it within the documented range.
SESN0172I: Using the default SecureRandom implementation for ID generation.
Explanation Session Manager is using the java default SecureRandom implementation for session ID generation. Action No action is required.
SESN0175I: Will use an existing session context for application key {0}
Explanation An existing session context is going to be shared for this application key. Action No action is required.
SESN0176I: Will create a new session context for application key {0}
Explanation A new session context will be created for this application key. Action No action is required.
SESN0194W: Session Manager found custom property {0} with value {1}. It cannot override server level configuration with value {2}. It will be ignored.
Explanation The custom property can only be set at the server level configuration. The property will be ignored. Action Remove the custom property from the application/module level configuration. Change the server level configuration if applicable.
SESN0195I: Session Manager found custom property {0} with value {1}. Because it is the same as the server level configuration property, it will be used.
Explanation The custom property can only be set at the server level configuration. Since it is the same as the server level configuration property, it will be used. Action No action is required.
SESN0196W: The Id Generator generated an id that already exists.
Explanation The Id Generator generated an id that already exists. We will create another id. Action No action is required.
SESN0800W: Property CloneSeparator should be exactly one char and it cannot be space. The current value of CloneSeparator specified is "{0}"
Explanation The property CloneSeparator should be exactly one char and it cannot be space. Action Modify the CloneSeparator custom property.