[jboss-jira] [JBoss JIRA] Commented: (JBAS-3568) UnackedUnitTestCase test failure when using the IBM JVM

[Adrian Brock (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-3568?page=comments#action_12342074 ] 
            
Adrian Brock commented on JBAS-3568:
------------------------------------

The issue is in question is this one;
http://jira.jboss.com/jira/browse/JBAS-3221

Which was raised by Scott (after a long discussion on the dev list).
i.e. The JBossMQ tests are poorly written in that any failure
is usually a random false negative (due to ambient conditions
of the machine running the test) and that once they fail
the next tests fail because they don't tidyup after themselves
properly.

Absent random false negatives the tests work fine.

I'm not surprised you didn't find it since the title was
also very specific, dealing with the specific issue
that Scott encountered.

I've changed its title to reflect its generic nature.

> UnackedUnitTestCase test failure when using the IBM JVM
> -------------------------------------------------------
>
>                 Key: JBAS-3568
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3568
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>    Affects Versions: JBossAS-4.0.4.GA
>         Environment: IBM 1.4.2 JDK
> Linux Kernel 2.6.9 
>            Reporter: Matt Wringe
>
> The org.jboss.test.jbossmq.test.UnackedUnitTestCase testUnackedDurableTopic test fails when the IBM JDK is used.
> Error from the test report:
> The durable subscription is already in use. DurableSubscription[clientId=DurableSubscriberExample name=test selector=null]
> javax.jms.IllegalStateException: The durable subscription is already in use. DurableSubscription[clientId=DurableSubscriberExample name=test selector=null]
> 	at org.jboss.mq.server.JMSTopic.addSubscriber(JMSTopic.java:92)
> 	at org.jboss.mq.server.ClientConsumer.addSubscription(ClientConsumer.java:142)
> 	at org.jboss.mq.server.JMSDestinationManager.subscribe(JMSDestinationManager.java:541)
> 	at org.jboss.mq.server.JMSServerInterceptorSupport.subscribe(JMSServerInterceptorSupport.java:311)
> 	at org.jboss.mq.security.ServerSecurityInterceptor.subscribe(ServerSecurityInterceptor.java:157)
> 	at org.jboss.mq.server.TracingInterceptor.subscribe(TracingInterceptor.java:779)
> 	at org.jboss.mq.server.JMSServerInvoker.subscribe(JMSServerInvoker.java(Inlined Compiled Code))
> 	at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java(Compiled Code))
> 	at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java(Compiled Code))
> 	at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java(Compiled Code))
> 	at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java(Compiled Code))
> 	at java.lang.Thread.run(Thread.java(Compiled Code))

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira