1) yes
2) It's the default setting for connections outside a managed tx, per the JDBC
spec
3) no
4) You can't, the AS connection management code needs to be fixed fixed so it
invalidates the connection. https://jira.jboss.org/jira/browse/JBAS-5080
5) You're crazy, but you can use a CheckedAction
In case anyone who reads this cares, this is verified fixed in 4.2.3. Works
exactly as it should now. The next jdbc insert or update call after the
timeout occurs throws an exception and everything gets rolled back.
Thanks,
Joe
View the original post :
4) You can't, the AS connection management code needs to be fixed fixed so it
invalidates the connection. https://jira.jboss.org/jira/browse/JBAS-5080
Jboss 4.2.3 fixes this bug. We will upgrade to this. Thanks for pointing
to the bug.
5) You're crazy, but you can use a CheckedAction if
4) You can't, the AS connection management code needs to be fixed fixed so it
invalidates the connection. https://jira.jboss.org/jira/browse/JBAS-5080
Jboss 4.2.3 fixes this bug. We will upgrade to this. Thanks for pointing
to the bug.
5) You're crazy, but you can use a CheckedAction if
