Skip to main content
Version: 7.2405.x.x LTS

CACH

The next table lists all error codes related to the session cache.

MajorMinorMessageDetails
CACH0001Neither the master nor the slave do support session reaping. Reaping will not work. Be aware that this will fill the databaseFor more information, contact support.
0002invoking session-listener failedFor more information, contact support.
0003illegal value for 'isNew'. Only 'true' or 'false' are allowedFor more information, contact support.
0004caught ExceptionSee the log for further details. For more information, contact support.
0005no entry found or createdFor more information, contact support.
0006missing id in query in CacheRestServer_1_0::getSessionFor more information, contact support.
0007missing id in query in CacheRestServer_1_0::destroySessionFor more information, contact support.
0008missing id in query in CacheRestServer_1_0::addKeyFor more information, contact support.
0009missing key in query in CacheRestServer_1_0::addKeyFor more information, contact support.
0010missing key in query in CacheRestServer_1_0::removeKeyFor more information, contact support.
0011missing interval in query in CacheRestServer_1_0::setMaxInactiveIntervalFor more information, contact support.
0012could not parse in CacheRestServer_1_0::setMaxInactiveIntervalFor more information, contact support.
0013missing lifetime in query in CacheRestServer_1_0::setMaxLifetimeFor more information, contact support.
0014could not parse in CacheRestServer_1_0::setMaxLifetimeFor more information, contact support.
0015missing id in query in CacheRestServer_1_0::updateSessionFor more information, contact support.
0016invalid request (no attribute given) in CacheRestServer_1_0::updateSessionFor more information, contact support.
0017an attribute can't be set in CacheRestServer_1_0::updateSessionFor more information, contact support.
0018sessionId is missing in CacheRestServer_1_0::sendSessionFor more information, contact support.
0019unsupported Content-TypeFor more information, contact support.
0020unexpected statuscode, the session could not be created in CacheRestClient_1_0::createFor more information, contact support.
0021unexpected statuscode, the session could not be gotFor more information, contact support.
0022unexpected statuscode, the session could not be created in CacheRestClient_1_0::getOrCreateFor more information, contact support.
0023unexpected statuscode, the session could not be destroyedFor more information, contact support.
0024unexpected statuscode, the key could not be addedFor more information, contact support.
0025unexpected statuscode, the key could not be removedFor more information, contact support.
0026the attribute could not be setFor more information, contact support.
0027the attribute could not be removedFor more information, contact support.
0028unexpected statuscode, the session could not be timestampedFor more information, contact support.
0029unexpected statuscode, the maximal inactive timeout could not be setFor more information, contact support.
0030unexpected statuscode, the maximal lifetime could not be setFor more information, contact support.
0031no entry could be foundThis 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.
0032the entry has already the keyThis 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.
0033can't remove the unique idFor more information, contact support.
0034the default value is missing in the Configuration-tableCheck that all defaults are specified in the configuration table in your MariaDB node. The table is usually called "conf".
0035for session-stickiness a value is missing in the Configuration-tableCheck that all needed values for session stickiness are specified in the configuration table in your MariaDB node. The table is usually called "conf".
0036for session-stickiness a value in the Configuration-table is invalidCheck that all needed values for session stickiness are specified correctly in the configuration table in your MariaDB node. The table is usually called "conf".
0037can't get entry because of some sql-problemsCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0038can't create or get new entry because of some sql-problemsCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0039could not store mapping into database (a different mapping exist)For more information, contact support.
0040could not store mapping into databaseFor more information, contact support.
0041could not remove alternate keyCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0042The attribute name might not fit into the DB, because it's too longIncrease the size in the MariaDB table. For example: alter table attribute modify NAME varchar(300) NOT NULL;
0043The attribute value might not fit into the DB, because it's too longIncrease the size in the MariaDB table and/or the parameter MaxAttributeSize of the MySQLSessionStoreServlet. This error may also occur if you have set the parameter StoreInterceptedRequest of the IdentityCreationFilter to "true". In this case, make sure that the value of the parameter StoreInterceptedRequest.Maxsize is lower than the value of the parameter MaxAttributeSize in the MySQLSessionStoreServlet.
0044could not set attributeCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0045could not remove attributeCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0046could not delete attributeCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0047could not update access timeCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0048could not update inactive timeoutCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0049could not update max lifetimeCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0050could not remove all zombie-entriesCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0051could not mark all timedout entriesCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0052could not delete sessions with a given owner_idCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0053could not store mappingCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0054could not store session into databaseCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0055could not store session into database. Affected not only 1 row...For more information, contact support.
0056could not store mapping into databaseCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0057could not store attribute into databaseCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0058could not delete attributeCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0059could not delete sessionCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0060could not delete key-id-mapCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0061could not delete entriesCheck the log file (navajo.log, mysql-log) for more information. The database seems to have a problem.
0062The reaper has been reaping for at least a certain amount of secondsThe 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.
0063The reaper has been reaping for at least a certain amount of seconds. Check the MySql-databaseThe 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.
0064unexpected statuscode, the session could not be createdSee the navajo.log log file for more information.
0065ID already exists in the cache table.The system generated an already used session ID. No session will be created for the given request.
0066ID already exists in the cache table.The system generated an already used session ID. No session will be created for the given request.
0067a critical amount of the memory is in useThe local session store is using at least 90% of the memory. No new sessions will be created, so that some customers may no longer be able to log in.
0068nearly the maximal amount of the memory is in useThe local session store is using at least 95% of the memory. No sessions will be created or changed anymore. This means that users will no longer be able to log in, perform a step-up or do similar actions.
0069A foreign key is missingThe database for the dynamic session store misses one or more foreign keys. This can lead to a filling up of the database. Check the chapter MySQLSessionStoreServlet on how to configure the database correctly. On certain MariaDB versions this error message is invalid due to a MariaDB bug. Check the DisableDatabaseSchemaCheck parameter of MySQLSessionStoreServlet.
0070A primary key is missingThe database for the dynamic session store misses one or more primary keys. This may lead to performance problems. Check the chapter MySQLSessionStoreServlet on how to configure the database correctly.
0071A column in the database table is missingThe database for the dynamic session store misses one or more numeric columns. As a consequence, the session store will not work as expected. Check the chapter MySQLSessionStoreServlet on how to configure the database correctly.
0072A column in the database table is missingThe database for the dynamic session store misses one or more data columns. As a consequence, the session store will not work as expected. Check the chapter MySQLSessionStoreServlet on how to configure the database correctly.
0073The session could not be backed upA session could not be backed up to the BackupServlet of the MultiLevelSessionStore. If another instance takes over the session, the session information may contain some old information.
0074The constraint 'uc_id_name unique (ID, NAME)' is missing in the table. The session store may not work as expected.The constraint 'uc_id_name' is missing in the database, Please check if the table has been setup correctly.