Skip to main content
Version: 7.2402.x.x RR

NVST

The next table lists all error codes related to the Navajo servlet management.

MajorMinorMessageDetails
NVST0001An attribute with the same name has already been added to the ServletContextContact support.
0002A possible memory-leak has been detectedContact support.
0003A possible memory-leak has been detectedContact support.
0004The session could not be synchronizedSome session attributes may not have been stored. As a consequence, a user may have to log in again. Check the log file for further information.
0005The intercepted request could not be copied to store it.No intercepted request was available after a successful login.
0006A runtime-exception occurred while renegotiating the ssl-session.Check the log file for further information.
0007An io-exception occurred while renegotiating the ssl-session.Check the log file for further information.
0008invalid format of property 'ch.nevis.navajo.tracing.TraceId.Format', a '[' was expected.Check your configuration (usually the file bc.properties).
0009invalid format of property 'ch.nevis.navajo.tracing.TraceId.Format', a ']' was expected.Check your configuration (usually the file bc.properties).
0010invalid format of property 'ch.nevis.navajo.tracing.TraceId.Format'. Check the log for further detail.Check your configuration (usually the file bc.properties).
0011maxInactiveInterval overlimits limitMaxInactiveInterval.Increase the value of the attribute limitMaxInactiveInterval in the tag HttpSessionCache.
0012No session management has been configured.Check your configuration. You have to configure either a dynamic session management (using the SessionManagementFilter) or a legacy one (in the servlet container).
0020The PATH_INFO is not yet to be determined. It is temporarily set to unknown.The error occurs if you use the PATH_INFO inside a Condition for the local trace groups. At that moment, the PATH_INFO is not yet known, so the condition cannot be used yet. You can use 'REQUEST_URI' instead.