This problem turned out to be related to test order and not JDK6 per se. OJB internals are
based on static state and running multiple tests w/o forking lead to connections and their
pools to be reused from test to test. When a test ran first that did not allocate all connections
possible, subsequent tests attempted to get new connections from connection pools that
belonged to prior tests which were by now closed. These DB connection attempts failed.
Fix involves static tracking of OBJ specific connection manager implementation instances and
resetting their internal state on startup. This code does nothing on the initial invocation,
(for the first test and production instances), but serves to clear the statically held OJB
state between test cases.
Commit SVN revision: 775413