NVST
The next table lists all error codes related to the Navajo servlet management.
| Major | Minor | Message | Details |
|---|---|---|---|
| NVST | 0001 | An attribute with the same name has already been added to the ServletContext | Contact support. |
| 0002 | A possible memory-leak has been detected | Contact support. | |
| 0003 | A possible memory-leak has been detected | Contact support. | |
| 0004 | The session could not be synchronized | Some 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. | |
| 0005 | The intercepted request could not be copied to store it. | No intercepted request was available after a successful login. | |
| 0006 | A runtime-exception occurred while renegotiating the ssl-session. | Check the log file for further information. | |
| 0007 | An io-exception occurred while renegotiating the ssl-session. | Check the log file for further information. | |
| 0008 | invalid format of property 'ch.nevis.navajo.tracing.TraceId.Format', a '[' was expected. | Check your configuration (usually the file bc.properties). | |
| 0009 | invalid format of property 'ch.nevis.navajo.tracing.TraceId.Format', a ']' was expected. | Check your configuration (usually the file bc.properties). | |
| 0010 | invalid format of property 'ch.nevis.navajo.tracing.TraceId.Format'. Check the log for further detail. | Check your configuration (usually the file bc.properties). | |
| 0011 | maxInactiveInterval overlimits limitMaxInactiveInterval. | Increase the value of the attribute limitMaxInactiveInterval in the tag HttpSessionCache. | |
| 0012 | No 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). | |
| 0013 | requested client identification is not configured. | Check your configuration. | |
| 0014 | client identification failed. Check the log for more information | For security reasons, the session will be invalidated. The user may have to log in again. | |
| 0015 | client identification failed. No client-id has been recieved | For security reasons, the session will be invalidated. The user may have to log in again. | |
| 0016 | client identification failed. The client-id does not match | For security reasons, the session will be invalidated. The user may have to log in again. | |
| 0017 | session identification failed. No client-id has been found for the given session-id | For security reasons, the session will be invalidated. The user may have to log in again. | |
| 0018 | A possible memory-leak hase been detected | Contact support. | |
| 0019 | The intercepted request could not be copied from the session. | Contact support. | |
| 0020 | The 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. |