New datasources have idle-timeout-minutes set to 0 in EAP 6

Solution Verified - Updated -

Issue

  • Connections from a newly created datasource are not timed-out by JBoss after more than 30 minutes1 of idle time
  • Though no timeout period was specified during creation (in the web console), the following is added to each new datasource2 created
<timeout>
    <set-tx-query-timeout>false</set-tx-query-timeout>
    <blocking-timeout-millis>0</blocking-timeout-millis>
    <idle-timeout-minutes>0</idle-timeout-minutes>
    <query-timeout>0</query-timeout>
    <use-try-lock>0</use-try-lock>
    <allocation-retry>0</allocation-retry>
    <allocation-retry-wait-millis>0</allocation-retry-wait-millis>
</timeout>

  1. Default idle-timeout-minutes in EAP 6 

  2. See <standalone|domain>.xml 

Environment

  • Red Hat JBoss Enterprise Application Server (EAP) 6.3.0 and later
  • All datasource types

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.