org.jboss.aop.NotFoundInDispatcherException under heavy load
pradeepbhat Aug 17, 2006 4:19 AMWhen too many messages are sent to the JBoss Messaging system i.e around 10K messages I frequently encounter this exception for both Queue and Topic. I am using Oracle 9i as the persistent datastore. I also see the exception when using the default Hypersonic database as well.
org.jboss.aop.NotFoundInDispatcherException: Object with oid: -2147483596 was not found in the Dispatcher at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:126) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:842) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:691) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:443) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:530) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:253) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163) at org.jboss.remoting.Client.invoke(Client.java:610) at org.jboss.remoting.Client.invoke(Client.java:602) at org.jboss.jms.client.delegate.DelegateSupport.invoke(DelegateSupport.java:112) at org.jboss.jms.client.delegate.ClientSessionDelegate$send_N3028277934545793941.invokeNext(ClientSessionDelegate$send_N3028277934545793941.java) at org.jboss.jms.client.container.TransactionAspect.handleSend(TransactionAspect.java:170) at org.jboss.aop.advice.org.jboss.jms.client.container.TransactionAspect10.invoke(TransactionAspect10.java) at org.jboss.jms.client.delegate.ClientSessionDelegate$send_N3028277934545793941.invokeNext(ClientSessionDelegate$send_N3028277934545793941.java) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:134) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:117) at org.jboss.jms.client.delegate.ClientSessionDelegate$send_N3028277934545793941.invokeNext(ClientSessionDelegate$send_N3028277934545793941.java) at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:69) at org.jboss.jms.client.delegate.ClientSessionDelegate$send_N3028277934545793941.invokeNext(ClientSessionDelegate$send_N3028277934545793941.java) at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107) at org.jboss.jms.client.delegate.ClientSessionDelegate$send_N3028277934545793941.invokeNext(ClientSessionDelegate$send_N3028277934545793941.java) at org.jboss.jms.client.delegate.ClientSessionDelegate.send(ClientSessionDelegate.java) at org.jboss.jms.client.container.ProducerAspect.handleSend(ProducerAspect.java:237) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
The jProfiler graph shows that the maximum heap size has not been reached.What is causing this exception to occur. My application has a producer sending lot of messages and consumer which processes those messages.