Some connection pool implementations (like the one from BitMechanic) allow you to specify a max time that a connection is allowed to remain open for before it is forcibly closed and returned to the pool.
This can be very useful if, for example, you're dealing with crappy code that doesn't always close connections in a finally block. (yes, I know, the right thing to do is to fix the code...)
Is it possible to do this with a JBoss managed connection pool? (in particular, a non-tx pool, since the client code doesn't use UserTransactions at present)?