title: Wildfly - Failed to auto release data source connection to pool after session closed
body: <p>As we know in jboss 6 if the code not handled with closing DB connection then the application server will close it and throws a warning message which will occur immediately after the transaction session closed, but this option is not available by default in Wildfly server which we come know after a code with connection left open.By search for solution in this context came to know about flush-strategy needs to be configured to take care of the idle connection, but its strikes the mind,</p>
  
  <ol>
  <li>why this option is removed is not available by default in wildfly server ?</li>
  <li>is this part of improvising the performance of server activity for scanning idle connection?</li>
  </ol>
  
  <p>But because of the default auto release option missing, application code which was not touched for a long time need to be revisited again to manage the connection manually, so it will put a lot of work in front.</p>
  
  <p>To overcome that, if i provide the flush strategy as "IdleConnections" and idle-timeout-minutes as 0 then will it be the equivalent to immediate connection release configuration and at the same time is this advisable to take this configuration setup to production.</p>
  
  <p><strong>Update:</strong></p>
  
  <p>we tried with below configuration, but the connection left open are not auto closed after the idle time out period 1 minute, so the below configuration also an inappropriate approach for handling idle connection then what would be the exact configuration to accomplish it ?</p>
  
  <pre><code> &lt;pool&gt;
       &lt;min-pool-size&gt;10&lt;/min-pool-size&gt;
       &lt;max-pool-size&gt;20&lt;/max-pool-size&gt;
       &lt;flush-strategy&gt;IdleConnections&lt;/flush-strategy&gt;    
   &lt;/pool&gt;
   &lt;timeout&gt;
       &lt;idle-timeout-minutes&gt;1&lt;/idle-timeout-minutes&gt;
   &lt;/timeout&gt;
  </code></pre>
  
  <p><strong>Update 2:</strong>
  Have tried in wildfly version 8.2.1 final too with above configuration but still no luck</p>