[JBoss-dev] jboss-3.2-testsuite build.98 Build Fixed

[qa]

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20050328204559Lbuild.98

BUILD COMPLETE -  build.98

Date of build: 03/28/2005 20:45:59

Time to build: 84 minutes 55 seconds

Last changed: 03/28/2005 12:33:36

Last log entry: JBAS-1448 ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really.

Unit Tests: (1967)  Total Errors and Failures: (10)

testNoClassDefFoundError org.jboss.test.classloader.test.BasicLoaderUnitTestCase testSessionHandleNoDefaultJNDI org.jboss.test.cts.test.StatefulSessionUnitTestCase testBMTSessionHandleNoDefaultJNDI org.jboss.test.cts.test.StatefulSessionUnitTestCase testMDBDeepRunAs org.jboss.test.security.test.EJBSpecUnitTestCase testSessionHandleNoDefaultJNDI org.jboss.test.securitymgr.test.StatefulSessionUnitTestCase testBMTSessionHandleNoDefaultJNDI org.jboss.test.securitymgr.test.StatefulSessionUnitTestCase testStatefulPassiviationExpiration org.jboss.test.testbeancluster.test.BeanUnitTestCase testThreadedAccess_SimpleLock org.jboss.test.cache.test.generic.IdentityLockUnitTestCase testSessionTimeout org.jboss.test.cluster.test.SimpleTestCase testSRPLoginWithAuxChallenge org.jboss.test.security.test.SRPLoginModuleUnitTestCase

Modifications since last build:  (2)
1.9.2.4	modified	andd	system/src/main/org/jboss/system/server/ServerInfo.java	JBAS-1448 ServerInfo.listThreadDump() will use the platform ThreadMXBean when running under jdk5+, in order to print out additional information (id, state, lockName, and a full StackTrace per thread). We also fixed the bug, where the listThreadDump() reported number of groups/threads was inconsistent with the output list. The numbers are still different with the ActiveThreadCount and ActiveThreadGroupCount attributes, but this is problem of the jdk, really.
1.4.4.2	modified	starksm	server/src/main/org/jboss/tm/usertx/client/ClientUserTransaction.java	Use the org.jboss.naming.NamingContextFactory.lastInitialContext thread local to allow the UserTransactionSessionFactory to be obtained using the same JNDI env used to lookup the UserTransaction. Resolves (JBAS-1270) UserTransaction with non default ProviderURL.