You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Romain Manni-Bucau <rm...@gmail.com> on 2012/10/10 14:06:28 UTC

issues on OpenEJB tests with AMQ 5.7.0

Hi,

since i upgraded AMQ version to 5.7.0 in OpenEJB/TomEE build we got some
issues we didn't have before (
http://ci.apache.org/builders/openejb-trunk-ubuntu/builds/3179/steps/test/logs/stdio
)

This is mainly due to some messages which are not receieved in the time we
are waiting them (5s)

Here a sample of stack:

javax.jms.InvalidDestinationException: Cannot publish to a deleted
Destination: temp-queue://ID:L80464-2-39372-1349863652533-3:2:3
 at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1731)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:277)
 at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:212)
at
org.apache.activemq.ActiveMQMessageProducerSupport.send(ActiveMQMessageProducerSupport.java:241)
 at org.apache.openejb.core.mdb.MdbInvoker.onMessage(MdbInvoker.java:114)
at
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1321)
 at
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:131)
at
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:202)
 at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:129)
at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:47)
 at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)


You can find a test here for instance
http://svn.apache.org/repos/asf/openejb/trunk/openejb/container/openejb-core/src/test/java/org/apache/openejb/core/mdb/JmsProxyTest.java

Locally running a single test it passes well but on our CI platform
(buildbot) we always have a failling test.

Note: we rely mainly on AMQ resource adapter

Any idea/pointer is welcomed :)

If you need you can ping me on IRC (i'm often on freenode #openejb channel)

*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*

Re: issues on OpenEJB tests with AMQ 5.7.0

Posted by Romain Manni-Bucau <rm...@gmail.com>.
FYI incresing the timeout time from 1s (original until amq 5.6.) to 30s
made the build passing but it doesnt sound so nice (5s was not enough and
we are on 127.0.0.1)

*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*




2012/10/10 Romain Manni-Bucau <rm...@gmail.com>

> Hi,
>
> since i upgraded AMQ version to 5.7.0 in OpenEJB/TomEE build we got some
> issues we didn't have before (
> http://ci.apache.org/builders/openejb-trunk-ubuntu/builds/3179/steps/test/logs/stdio
> )
>
> This is mainly due to some messages which are not receieved in the time we
> are waiting them (5s)
>
> Here a sample of stack:
>
> javax.jms.InvalidDestinationException: Cannot publish to a deleted
> Destination: temp-queue://ID:L80464-2-39372-1349863652533-3:2:3
>  at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1731)
> at
> org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:277)
>  at
> org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:212)
> at
> org.apache.activemq.ActiveMQMessageProducerSupport.send(ActiveMQMessageProducerSupport.java:241)
>  at org.apache.openejb.core.mdb.MdbInvoker.onMessage(MdbInvoker.java:114)
> at
> org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1321)
>  at
> org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:131)
> at
> org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:202)
>  at
> org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:129)
> at
> org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:47)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>  at java.lang.Thread.run(Thread.java:662)
>
>
> You can find a test here for instance
> http://svn.apache.org/repos/asf/openejb/trunk/openejb/container/openejb-core/src/test/java/org/apache/openejb/core/mdb/JmsProxyTest.java
>
> Locally running a single test it passes well but on our CI platform
> (buildbot) we always have a failling test.
>
> Note: we rely mainly on AMQ resource adapter
>
> Any idea/pointer is welcomed :)
>
> If you need you can ping me on IRC (i'm often on freenode #openejb channel)
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>