[JBoss-dev] jboss-3.2-testsuite build.21 Build Successful

[qa]

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

BUILD COMPLETE -  build.21

Date of build: 12/09/2004 04:35:41

Time to build: 61 minutes 27 seconds

Last changed: 12/08/2004 16:31:37

Last log entry: Move the onException reconnection to a seperate thread in all cases. It has been seen that the thread calling onException can have its interrupted state set which results in the reconnection immeadiately failing as though the container has been shutdown.

Unit Tests: (1885)  Total Errors and Failures: (30)

unknown org.jboss.test.jbossmq.test.LargeMessageUnitTestCase unknown org.jboss.test.jbossmq.test.OILConnectionUnitTestCase testQueueMessageOrder org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testRequestReplyQueue org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testTemporaryQueueDelete org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testTemporaryTopicDelete org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testInvalidDestinationQueueSend org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testInvalidDestinationQueueBrowse org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testInvalidDestinationTopicPublish org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testErrorsTopicSubscribe org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testCreateQueue org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testMessageListener org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testApplicationServerStuff org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testTopics org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testTopicNoLocal org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testTopicNoLocalBounce org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testTopicSelectorChange org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testTopicSelectorNullOrEmpty org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testSendReceiveOutdated org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testSendListenOutdated org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testProgramaticProxy org.jboss.test.jmx.test.JMXInvokerProxyUnitTestCase testServerFound org.jboss.test.jmx.test.JMXInvokerProxyUnitTestCase testEviction org.jboss.test.cache.test.eviction.ReplicatedLRUPolicyUnitTestCase testEvictionReplication org.jboss.test.cache.test.eviction.ReplicatedLRUPolicyUnitTestCase testStateTransfer org.jboss.test.cache.test.replicated.AsyncUnitTestCase testSyncRepl org.jboss.test.cache.test.replicated.AsyncUnitTestCase testSyncRepl org.jboss.test.cache.test.replicated.SyncTxUnitTestCase testASyncRepl org.jboss.test.cache.test.replicated.SyncTxUnitTestCase testPut org.jboss.test.cache.test.replicated.SyncTxUnitTestCase testPutTx org.jboss.test.cache.test.replicated.SyncTxUnitTestCase

Modifications since last build:  (1)
1.50.2.18	modified	starksm	server/src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoker.java	Move the onException reconnection to a seperate thread in all cases. It has been seen that the thread calling onException can have its interrupted state set which results in the reconnection immeadiately failing as though the container has been shutdown.