It'd be good to have a test case that can reproduce it. It's best to raise a Jira for this and attach the test (in any form).
Regards -- Dejan Bosanac Senior Software Engineer | FuseSource Corp. [email protected] | fusesource.com skype: dejan.bosanac | twitter: @dejanb blog: http://www.nighttale.net ActiveMQ in Action: http://www.manning.com/snyder/ On Wed, Jun 27, 2012 at 1:52 PM, Steve.V. <[email protected]> wrote: > I don't think it was the encoding issue. I now suspect it encounters trouble > in a low-memory situation. I have a test case I run on my PC that POSTs a > number of messages and then GETs them back off of the queue. If I keep the > number of messages under 650, I can run it over and over again without > problems. When I attempt more, it may work, but most times I encounter > trouble. When using 5.4.3, it reports: > > 2012-06-27 07:33:02,544 | DEBUG | Async client internal exception occurred > with no exception listener registered: java.lang.IllegalStateException: > DISPATCHED,initial | org.apache.activemq.ActiveMQConnection | ActiveMQ > Session: ID:d22275-4106-1340794703957-2:37:1 > java.lang.IllegalStateException: DISPATCHED,initial > at > org.eclipse.jetty.server.AsyncContinuation.dispatch(AsyncContinuation.java:364) > at > org.eclipse.jetty.server.AsyncContinuation.resume(AsyncContinuation.java:769) > at > org.apache.activemq.web.MessageServlet$Listener.onMessageAvailable(MessageServlet.java:368) > at > org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1250) > at > org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:134) > at > org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:205) > at > org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:98) > at > org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:36) > > Shortly before the trouble, I start seeing some messages like this: > > 2012-06-27 07:33:01,435 | DEBUG | Main:memory:queue://myqueue:memory: usage > change from: 67% of available memory, to: 68% of available memory | > org.apache.activemq.usage.Usage | VMTransport: vm://localhost#71 > > When using 5.6.0, the exception call stack is: > > 2012-06-27 07:44:04,007 | DEBUG | Async client internal exception occurred > with no exception listener registered: java.lang.IllegalStateException: > REDISPATCHING,initial,resumed | org.apache.activemq.ActiveMQConnection | > ActiveMQ Session Task-2 > java.lang.IllegalStateException: REDISPATCHING,initial,resumed > at > org.eclipse.jetty.server.AsyncContinuation.dispatch(AsyncContinuation.java:403) > at > org.eclipse.jetty.server.AsyncContinuation.resume(AsyncContinuation.java:810) > at > org.apache.activemq.web.MessageServlet$Listener.onMessageAvailable(MessageServlet.java:368) > at > org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1320) > 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:122) > at > org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43) > 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:619) > > > > > ----- > Stephen Vincent > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-5-6-IllegalStateException-MessageServlet-java-368-tp4651797p4653612.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
