On 5 Jun 2008, at 23:43, NateS wrote:
We had been using 4.1.1 and recently upgraded to 5.1. Everything
seemed fine
at first, but after a while we found some messages were not being
received.
I wrote the test below that reproduces the problem. With 5.1, after
running
the test for a little while the test will stop because a message was
sent
and not received within the (very liberal) timeout. Reverting back
to 4.1.1
and the test works fine. It also appears to work fine on 4.1.2.
To run the test, change SERVER in the provider URL of both source
files.
Then run the JmsReceiverTest first, then run the JmsSenderTest. With a
timeout of 2 seconds we see failure with 5.1 after about 200
messages. With
a timeout of 60 seconds failure happens at ~8000 messages.
This appears to be a bug with ActiveMQ 5.1, however I'd appreciate
any input
you might have if you think there is a better solution to achieve
the same
goal.
http://www.nabble.com/file/p17681102/JmsReceiverTest.java
JmsReceiverTest.java
http://www.nabble.com/file/p17681102/JmsSenderTest.java
JmsSenderTest.java
--
View this message in context:
http://www.nabble.com/ActiveMQ-5.1-broken---repro-test-included-tp17681102s2354p17681102.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I created a jira for this - AMQ-1778
cheers,
Rob
http://open.iona.com/products/enterprise-activemq
http://rajdavies.blogspot.com/
