Eserver or Aserver will not reconnect to the SQL DB after a DB restart
2 years ago
Originally Published: 2009-03-24
Article Number
000047602
Applies To
RSA Access Manager 6

SQL datastore

Issue
eserver or aserver will not reconnect to the SQL DB after a DB restart

An exception similar to the following is appearing in the eserver/aserver debug log:
 sirrus.da.exception.DataStoreException: SQLException : Code:08006;TextAn I/O
 error occured while sending to the backend.

Cause
When restarting the SQL DB used by AxM as its datastore, it has been noticed that the eserver and aserver processes are unable to reconnect to the DB. A restart of these processes is needed to resume normal operation.

An exception similar to the following would appear in the server's debug logs.

20:44:55:960 [*] [APIClientProxy-0] - Thread requesting stream.
sirrus.da.exception.DataStoreException: SQLException : Code:08006;TextAn I/O error occured while sending to the backend
        at
sirrus.da.sql.util.SQLEntityHelper.getUsers(SQLEntityHelper.java:669)
        at
sirrus.da.sql.util.SQLConnectionImpl.searchUsers(SQLConnectionImpl.java:702)



Resolution
Please take note of the error code returned by the JDBC driver (in the example above: 08006) that is appearing in your debug logs and add it to the paramet in sql.conf, as follows:

cleartrust.data.sql.server.postgresql.databasefatalcodes  :08006

Then restart your AxM server for the change to take effect.

Failed DB connection will then be removed from the DB connection pool as the error code above is encountered. It might take a few SQL queries for all failed DB connections to be flushed from the connection pool.

Related Articles

Trending Articles

Don't see what you're looking for?