[jboss-user] [JBoss Messaging] - Receiving IllegalStateExceptions in client
Hello
I'm performing a series of JMS stress tests that we've developed against JBoss
Messaging 1.0.1.SP4 and have a test scenario failing. My particular test is generating
frequent IllegalStateExceptions which causes message delivery to fail. The following is a
sample:
ERROR 2007-02-14 16:30:58,984 [Manager Queue Eight.1.4]
org.jboss.jms.client.remoting.MessageCallbackHandler: Failed to deliver message
javax.jms.IllegalStateException: Should only be one entry in list. There are 8908
at
org.jboss.jms.client.container.SessionAspect.handlePostDeliver(SessionAspect.java:203)
at
org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect6.invoke(SessionAspect6.java)
at
org.jboss.jms.client.delegate.ClientSessionDelegate$postDeliver_5319211143798977162.invokeNext(ClientSessionDelegate$postDeliver_5319211143798977162.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:182)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:117)
at
org.jboss.jms.client.delegate.ClientSessionDelegate$postDeliver_5319211143798977162.invokeNext(ClientSessionDelegate$postDeliver_5319211143798977162.java)
at
org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:69)
at
org.jboss.jms.client.delegate.ClientSessionDelegate$postDeliver_5319211143798977162.invokeNext(ClientSessionDelegate$postDeliver_5319211143798977162.java)
at
org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
at
org.jboss.jms.client.delegate.ClientSessionDelegate$postDeliver_5319211143798977162.invokeNext(ClientSessionDelegate$postDeliver_5319211143798977162.java)
at
org.jboss.jms.client.delegate.ClientSessionDelegate.postDeliver(ClientSessionDelegate.java)
at
org.jboss.jms.client.remoting.MessageCallbackHandler.postDeliver(MessageCallbackHandler.java:162)
at
org.jboss.jms.client.remoting.MessageCallbackHandler.callOnMessage(MessageCallbackHandler.java:137)
at
org.jboss.jms.client.remoting.MessageCallbackHandler$ListenerRunner.run(MessageCallbackHandler.java:722)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(Unknown Source)
at java.lang.Thread.run(Thread.java:534)
Essentially, this test does the following:
1. creates a set of text message payloads
2. creates a set of object message payloads
3. dispatches the message payloads to separate queues using a multi-threaded dispatcher
(the multi-threaded dispatcher obtains a jms session from a jms session pool)
4. at the same time, it receives the messages arriving on the queues using a
multi-threaded message listener
5. it then compares the payloads received on the text queue with the payloads dispatched
to that queue (and likewise for the object queue)
So far we've found 1.0.1.SP4 is a big improvement over the 1.0.1.GA release (we used
to get messages arriving on the wrong queues on older versions for some of our tests) but
this test in particular is still causing problems for JBoss Messaging.
Can any JBoss developers explain the significance of 'Should only be one entry in
list. There are 8908'?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4016222#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...