Hi Roman,

so far I couldn't build a simple sample application that shows this behaviour. But I found out that commenting line #285 in AbstractPingablePooledConnection.java seems to "solve" the problem.

Maybe "someone" in the JBoss environment is closing an already closed connection. Maybe it's possible to make the code a bit more robust for scenarios like this? What do you think? Maybe via some configuration value!?

--Heiko

protected void internalClose() throws SQLException {
/* checkValidity(); */

if (currentConnection != null)
currentConnection.deallocate();

jdbcConnection.close();

statements.clear();

invalidate();
}