I've got those messages, but I'd like to trace down in the code where the statement was not closed. Is there a way to tell Jboss to show the stack trace of this warning, so I can discover the precise class and line where the error is in ?
This statement check feature is a great thing!
There's no easy way to do it. We track down the issues through our unit tests which is the only advice I can really give. The commitment of the transactions/cleanup of the connection are in a sense separated from the code that actually performed the statement executions.