> I found how to reproduce this bug (or whatever it is).
> 1. Get the connection to the database,
> 2. do some selects (don't know if it is needed)
> 3. then get another connection to the same database while first
> connection is still open
> 4. do some selects with second connection
> 5. close second connection
> 6. close first connection.
> 7. wait 25 min. and try to get connection
> 8. you'll get an exception in Datasource.getConnection()

Thanks for the test case!

More testing is needed, but the behavior is a bit strange. It seems that
JBoss after 25 minutes of work destroys two managed connections and then
tries to enlist them in a new transaction.

I will check it again with more care, but I believe that JCA container
should not access managed connection that was already destroyed.

Roman