Try the latest trunk. A bug fix was made.
Daniel Ellis wrote:
>
> We have also experienced this issue when using ActiveMQ 1.2 with NMS.
>
> On the server, the wrapper.log file is full of these errors:-
>
> INFO | jvm 1| 2009/10/17 13:07:00 | ERROR Service
> - As
We have also experienced this issue when using ActiveMQ 1.2 with NMS.
On the server, the wrapper.log file is full of these errors:-
INFO | jvm 1| 2009/10/17 13:07:00 | ERROR Service
- Async error occurred: javax.jms.JMSException: Unmatched acknowledege:
MessageAck {c
I captured some stats from the broker before after this happened...
http://www.nabble.com/file/p25721340/stats2.txt Before
http://www.nabble.com/file/p25721340/stats5.txt After
Does anyone see any stat that sticks out as a problem?
magellings wrote:
>
> I found something interesting.
>
> I
I found something interesting.
If I remove delete privs on the ACTIVEMQ_MSGS TABLE (we're doing JDBC
Master/Slave) there are a couple things happening...
#1) I receive Async errors to the looks of it the same as before.
#2) The same messages are getting delivered to the listener after a restart
I was able to replicate this problem and am attaching a console application
written with .NET/VS 2008 using the official NMS 1.1. provider. We are
using ActiveMQ 5.2 with same config file as I attached previously.
To replicate send 1,000,000 messages through. Make a copy of the console
applicat
Hello. We are stress testing ActiveMQ 5.2 using NMS for .NET
producers/consumers. We are sending 200,000 messages through our system and
we ran into the error "Async error occurred" shortened for brevity. Log
file is attached. It seems this error keeps reoccuring after the first one
and fills
