HTTP Session Subsystem Messages

The HTTP Session1.0 catalog contains messages in the range BEA-100000 - BEA-100999. Messages in this catalog are part of the weblogic.servlet.internal.session Internationalization package and the weblogic.servlet.internal.session Localization package.

Action Check if the secondary server is down. Note that it is not recommended to kill both the primary and secondary server at the same time. Remember the replication happens lazily, upon request. So if you need to bring down the secondary server too give sufficient time so that the active end users hit their sessions and they get replicated. Warning: Web application: logContext tried to place a non-serializable attribute: name into the session: id . This attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be replicated to the secondary server. This message is logged only once per session.

Description Web application: logContext tried to place a non-serializable attribute: name into the session: id . This attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be replicated to the secondary server. This message is logged only once per session. Warning: Web application: logContext tried to place a non-serializable attribute: name into the session: id . This attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be persisted to the disk. This message is logged only once per session.

Description Web application: logContext tried to place a non-serializable attribute: name into the session: id . This attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be persisted to the disk. This message is logged only once per session. Warning: Web application: logContext tried to place a non-serializable attribute: name into the session: id . The attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be persisted to the database. This message is logged only once per session.

Description Web application: logContext tried to place a non-serializable attribute: name into the session: id . The attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be persisted to the database. This message is logged only once per session. Action This happens if the object has been cleaned up underneath or the version number does not match with the secondary object. This should not happen normally. Unwanted failovers at the front-end can cause unnecessary session failovers in the backend, which could result in this error in certain situations. Check the error for more information. Action This happens if the object has been cleaned up underneath or the version number does not match with the secondary object. This should not happen normally. Unwanted failovers at the front-end can cause unnecessary session failovers in the backend, which could result in this error in certain situations. Check the error for more information. Description The session id: sessionID has been accessed from currentServer , a server that is neither the primary ( primaryServer ) nor the secondary ( secondaryServer ). Repeated occurrences of this can cause memory problems and performance degradation, as sessions are loaded into memory on more than two servers at a time. Description The global JDBC connection pool reserve timeout seconds is changed when JDBC Session Context initialize. The value is set to be default value (120s) or the value of in which defined in weblogic.xml or weblogic-application.xml, and the jdbc-connection-timeout-secs is deprecated. This issue will be fixed in the future release.