-
1. Re: wildfly-failed to auto release datasource connection to pool
ataylor Jan 10, 2016 3:20 AM (in response to seetha-s)I would post this on the Wildfly forums, this has nothing to do with HornetQ.
-
2. Re: wildfly-failed to auto release datasource connection to pool
jaysensharma Jan 10, 2016 5:38 AM (in response to seetha-s)In WildFly as well you should be able to see the message "Closing a connection for you. Please close them yourself" generated, If you will enable the jca "cached-connection-manager" debug as following:
/subsystem=jca/cached-connection-manager=cached-connection-manager/:write-attribute(name=debug,value=true)
Generated XML Snippet
<subsystem xmlns="urn:jboss:domain:jca:2.0"> <archive-validation enabled="true" fail-on-error="true" fail-on-warn="false"/> <bean-validation enabled="true"/> <default-workmanager> . . . </default-workmanager> <cached-connection-manager debug="true"/> <!-- #### NOTICE --> </subsystem>
What it will do ?
>>> After enabling the above debug you should be able to see the following message in your logs "Closing a connection for you. Please close them yourself"
>>> It will also produce a stacktrace indicating where the leaked connection was opened and it will then Close the leaked connection.
Regards
Jay SenSharma
-
3. Re: wildfly-failed to auto release datasource connection to pool
seetha-s Jan 12, 2016 3:49 AM (in response to jaysensharma)we had tried the above configuration but that too not closing the IdleConnections,and we didn't get this message in sever log" Closing a connection for you. Please close them yourself"..
-
4. Re: wildfly-failed to auto release datasource connection to pool
srinu.ydlp Jan 14, 2018 4:24 AM (in response to seetha-s)Hi, did you find solution for this. I am also facing same problem.
Thank you