Skip to navigation

How does idle-timeout-minutes works in datasource ?

Updated 2014-03-28T11:57:52+00:00

Issue

  • What is idle-timeout-minutes in datasource configuration ?
  • Why does the connection is not removed after idle-timeout-minutes ?
  • We are relying on idle-timeout-minutes to flush idle connections and get below error :
IO Error: End of TNS data channel; nested exception is java.sql.SQLRecoverableException: IO Error: End of TNS data channel

Followed by :

 Closed Connection; nested exception is java.sql.SQLRecoverableException: Closed Connection
  • How to set idle timeout in data source?
  • Why are we seeing this error
<TIMESTAMP> TRACE [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (IdleRemover) Destroying timedout connection org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@3b729fa1[state=NORMAL managed connection=org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@624e2184 connection handles=0 lastUse=1388075895091 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@42b996d7 pool internal context=SemaphoreArrayListManagedConnectionPool@3a6f01bf[pool=<POOL NAME>]

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 5.x
      • idle-timeout-minutes as defined in a -ds.xml
    • idle-timeout-minutes for EAP 6 as defined in
      • jboss-as-resource-adapters_1_0.xsd
      • jboss-as-datasources_1_0.xsd
      • jboss-as-datasources_1_1.xsd

Subscriber content preview. For full access to the Red Hat Knowledgebase, please log in.

Not a subscriber? Learn more about the benefits of Red Hat Subscriptions.