Re: [JBoss-dev] Deprecating oswego in favor of (java.util.concurrent backport?

I'd suggest something like the following strategy: * Add this backport to the thirdparty * Allow projects currently under development to use it, e.g. JMS, MC * When those projects confirm it is usable worry about porting old code using oswego The idea being that people doing development are

[JBoss-dev] ejb3-4.0-testsuite Build Failed

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=log20060121122008 BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-ejb3-4.0-testsuite.xml:83: Exit code: 1 See tests.log in Build Artifacts for details.Date of

[JBoss-dev] jboss-3.2-testsuite Build Completed With Testsuite Errors

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060121131459 TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:191: The following error occurred while executing this line:

[JBoss-dev] RE: ejb3-4.0-testsuite Build Failed

This is just the org.jboss.ejb3.test.microbench.unit.BenchUnitTestCase requiring too much memory. Memory usage during this test goes from 40m to 130m even using the default config so the memory usage of this needs to be looked at. -Original Message- From: Bill Burke Sent: Sunday,

[JBoss-dev] jboss-portal-2.0-testsuite Build Completed With Testsuite Errors

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.0-testsuite?log=log20060121171702 TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-portal.xml:67: The following error occurred while executing this line:

[JBoss-dev] jboss-portal-2.2-testsuite Build Completed With Testsuite Errors

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.2-testsuite?log=log20060121171936 TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-portal.xml:67: The following error occurred while executing this line:

[JBoss-dev] jboss-remoting-testsuite-1.4 Build Timed Out

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060121175352 BUILD TIMED OUTAnt Error Message:build timeoutDate of build:01/21/2006 17:53:52Time to build:Last changed:12/31/2005 20:37:24Last log entry:JBREM-272:Added tests for (clientPool

[JBoss-dev] jboss-seam-testsuite Build Completed With Testsuite Errors

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-seam-testsuite?log=log20060121225429 TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-seam-testsuite.xml:118: The following error occurred while executing this line:

[JBoss-dev] jboss-remoting-testsuite-1.5 Build Timed Out

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060121195405 BUILD TIMED OUTAnt Error Message:build timeoutDate of build:01/21/2006 19:54:05Time to build:Last changed:12/31/2005 20:37:24Last log entry:JBREM-272:Added tests for (clientPool

RE: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed

So after profiling this the problem looks to be recent changes in org.jboss.util.timeout.TimeoutFactory as the leaks are related to transaction timeouts. By clearing the TimeoutFactory$TimeoutImpl references the test gets past the OME, but there are 73k TimeoutFactory$TimeoutImpl left after the