I would post this on the Wildfly forums, this has nothing to do with HornetQ.
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:
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.
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"..