Troubleshooting
Problem
Connection from TADDM to Oracle database server times out
Symptom
TADDM hangs - needs a restart
Logs will show connection errors to the database such as
2012-11-28 21:42:39,710 TopologyManager [RMI TCP Connection(1934)-10.1.0.2] ERROR changemgr.ChangeManagerPersisterImpl -
java.sql.SQLException: IO Error: Connection timed out
at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:874)
or
2012-12-02 16:19:40,583 ChangeManager [pool-2-thread-1] ERROR changemgr.ChangeManagerPersisterImpl -
java.sql.SQLException: Closed Connection
at oracle.jdbc.driver.PhysicalConnection.needLine(PhysicalConnection.java:5373)
Cause
TADDM uses database connection pooling for improved performance. When using Oracle with a firewall, dormant connections in the pool may be ended by the firewall. Oracle never cleans up these connections, so eventually the number of defunct connections to the database increases, until the database will allow no more connections. All of the available connections on the database appear "used" although they are not actually in use. This may be more likely to happen when TADDM is less active because fewer database connections will be active and therefore more connections will time out.
Resolving The Problem
There are two solutions to this.
1) extend the firewall inactive connection timeout
2) Enable Oracle Net DCD by setting SQLNET.EXPIRE_TIME=1 in the sqlnet.ora file on the database server.
More information is available from Oracle here:
http://docs.oracle.com/cd/B19306_01/java.102/b14355/apxtblsh.htm
(Scroll down to the "Using JDBC with Firewalls" section.)
Product Synonym
TADDM
Was this topic helpful?
Document Information
Modified date:
23 June 2018
UID
swg21619731