[
https://issues.apache.org/jira/browse/JS2-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randy Watler resolved JS2-1014.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
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
> Unit tests fail in Portals Components using JDK6
> ------------------------------------------------
>
> Key: JS2-1014
> URL: https://issues.apache.org/jira/browse/JS2-1014
> Project: Jetspeed 2
> Issue Type: Bug
> Components: Components Core, Testing
> Affects Versions: 2.2.0
> Environment: J2 2.2 Trunk
> JDK6/Linux/x86_64
> Reporter: Randy Watler
> Assignee: Randy Watler
> Fix For: 2.2.0
>
>
> Portals Components unit tests fail to execute using JDK 6 with various error
> messages indicating DB connection pool is closed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-dev-h...@portals.apache.org
