I don't understand your question/comment.
If it is "how do I reproduce it?" then you need to set up some ejb calls that does
something like the following.
1) Start a transaction, e.g. invoke a CMT/Required ejb method
2) Make an ejb invocation on a different bean that opens a connection handle
but doesn't close it (e.g. like the thread local connection tests in the testsuite)
3) Force the transaction to timeout
Previously we would wait until the transaction ends when the method in step (1)
returns before checking for unclosed connections. This allows something
to close the connection that was "cached".
But since jboss-4.2.x the transaction timeout does the rollback which can
will give a spurious warning in this case.
NOTE: This usage is an anti-pattern and doesn't cause any real problems
which is why I'm not really too worried about this issue.
How it gets fixed is a different issue. It's tied up with the other JIRA issue
about the CachedConnectionManager rewrite that is required such
that it better understands the ejb lifecycle(s) and the "Debug" feature
needs redoing so it isn't so contentious on the WeakHashMap.
Search for other forum threads and links from the JIRA issues
for more information and ideas.
Thanks Adrian, I will do more investigate.