CACH
The next table lists all error codes related to the session cache.
| Major | Minor | Message | Details |
|---|---|---|---|
| CACH | 0001 | Neither the master nor the slave do support session reaping. Reaping will not work. Be aware that this will fill the database | Contact support. |
| 0002 | invoking session-listener failed | Contact support. | |
| 0003 | illegal value for 'isNew'. Only 'true' or 'false' are allowed | Contact support. | |
| 0004 | caught Exception | See the log for further details. Contact support. | |
| 0005 | no entry found or created | Contact support. | |
| 0006 | missing id in query in CacheRestServer_1_0::getSession | Contact support. | |
| 0007 | missing id in query in CacheRestServer_1_0::destroySession | Contact support. | |
| 0008 | missing id in query in CacheRestServer_1_0::addKey | Contact support. | |
| 0009 | missing key in query in CacheRestServer_1_0::addKey | Contact support. | |
| 0010 | missing key in query in CacheRestServer_1_0::removeKey | Contact support. | |
| 0011 | missing interval in query in CacheRestServer_1_0::setMaxInactiveInterval | Contact support. | |
| 0012 | could not parse in CacheRestServer_1_0::setMaxInactiveInterval | Contact support. | |
| 0013 | missing lifetime in query in CacheRestServer_1_0::setMaxLifetime | Contact support. | |
| 0014 | could not parse in CacheRestServer_1_0::setMaxLifetime | Contact support. | |
| 0015 | missing id in query in CacheRestServer_1_0::updateSession | Contact support. | |
| 0016 | invalid request (no attribute given) in CacheRestServer_1_0::updateSession | Contact support. | |
| 0017 | an attribute can't be set in CacheRestServer_1_0::updateSession | Contact support. | |
| 0018 | sessionId is missing in CacheRestServer_1_0::sendSession | Contact support. | |
| 0019 | unsupported Content-Type | Contact support. | |
| 0020 | unexpected statuscode, the session could not be created in CacheRestClient_1_0::create | Contact support. | |
| 0021 | unexpected statuscode, the session could not be got | Contact support. | |
| 0022 | unexpected statuscode, the session could not be created in CacheRestClient_1_0::getOrCreate | Contact support. | |
| 0023 | unexpected statuscode, the session could not be destroyed | Contact support. | |
| 0024 | unexpected statuscode, the key could not be added | Contact support. | |
| 0025 | unexpected statuscode, the key could not be removed | Contact support. | |
| 0026 | the attribute could not be set | Contact support. | |
| 0027 | the attribute could not be removed | Contact support. | |
| 0028 | unexpected statuscode, the session could not be timestamped | Contact support. | |
| 0029 | unexpected statuscode, the maximal inactive timeout could not be set | Contact support. | |
| 0030 | unexpected statuscode, the maximal lifetime could not be set | Contact support. | |
| 0031 | no entry could be found | This may occur if the entry has been expired or timed out, or if another request performed a logout on the same entry at the same time. | |
| 0032 | the entry has already the key | This may occur if another request has set the same key at the same time, which could happen in case of a misconfigured, custom-based SessionManagementFilter. | |
| 0033 | can't remove the unique id | Contact support. | |
| 0034 | the default value is missing in the Configuration-table | Check that all defaults are specified in the configuration table in your MariaDB node. The table is usually called "conf". | |
| 0035 | for session-stickiness a value is missing in the Configuration-table | Check that all needed values for session stickiness are specified in the configuration table in your MySQL node. The table is usually called "conf". | |
| 0036 | for session-stickiness a value in the Configuration-table is invalid | Check that all needed values for session stickiness are specified correctly in the configuration table in your MySQL node. The table is usually called "conf". | |
| 0037 | can't get entry because of some sql-problems | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0038 | can't create or get new entry because of some sql-problems | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0039 | could not store mapping into database (a different mapping exist) | Contact support. | |
| 0040 | could not store mapping into database | Contact support. | |
| 0041 | could not remove alternate key | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0042 | The attribute name might not fit into the DB, because it's too long | Increase the size in the MySQL table. For example: alter table attribute modify NAME varchar(300) NOT NULL; | |
| 0043 | The attribute value might not fit into the DB, because it's too long | Increase the size in the MySQL table and/or the parameter MaxAttributeSize of the MySQLSessionStoreServlet. |
For example:
alter table attribute modify VALUE MEDIUMBLOB;
and in the MySQLSessionStoreServlet:
<init-param>
<param-name>MaxAttributeSize</param-name>
<param-value>120000</param-value>
</init-param>
| Major | Minor | Message | Details |
|---|---|---|---|
| 0044 | could not set attribute | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0045 | could not remove attribute | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0046 | could not delete attribute | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0047 | could not update access time | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0048 | could not update inactive timeout | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0049 | could not update max lifetime | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0050 | could not remove all zombie-entries | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0051 | could not mark all timedout entries | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0052 | could not delete sessions with a given owner_id | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0053 | could not store mapping | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0054 | could not store session into database | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0055 | could not store session into database. Affected not only 1 row... | Contact support. | |
| 0056 | could not store mapping into database | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0057 | could not store attribute into database | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0058 | could not delete attribute | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0059 | could not delete session | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0060 | could not delete key-id-map | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0061 | could not delete entries | Check the log file (navajo.log, mysql-log) for more information. The database seems to have a problem. | |
| 0062 | The reaper has been reaping for at least a certain amount of seconds | The local session store seems to have performance problem. This could happen under heavy load or if thousand of sessions expire at the same time. To avoid this error, increase the value of the parameter ReaperTimeOut of the LocalSessionStoreServlet. | |
| 0063 | The reaper has been reaping for at least a certain amount of seconds. Check the MySql-database | The MariaDB node seems to have some performance problems. This could happen under heavy load or if thousand of sessions expire at the same time. Check in the logs of the MariaDB if something is wrong. To avoid this error, you can increase the value of the parameter ReaperTimeOut of the MySQLSessionStoreServlet. | |
| 0064 | unexpected statuscode, the session could not be created | See the navajo.log log file for more information. |