I had another thought. The issue appears to have something to do with timestamps assigned to stored procedures. All of the posts I have seen on this recommend recompiling the client code so that the client picks up the new timestamps. Well, in Java, I suspect that the Oracle JDBC driver loads the timestamps. If the Oracle JDBC driver provides a way to reload the timestamps, then if you wrote a valid-connection-checker-class-name class, you could have it make that Oracle JDBC driver call to reload the timestamps. So the question then becomes, does the Oracle JDBC driver provide such a feature? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200848#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...