Jboss Messaging randomly implodes

[nbreau]

We're running Jboss messaging as a standalone app with JBoss application server (latest release of both) with a load of anywhere around 100-300 messages per second. I was wondering if someone could tell me what the issue could be, I'm not getting any hints of the following stack trace. Once the error occurs I need to restart my application in order to be able to start publsihing to JBoss again. Once the error starts occuring this stack trace gets printed on every attempt to send a message.

I'm not seeing any errors in the jboss logs.


Stack trace:

Error publishing to topic : org.jboss.jms.util.MessagingJMSException: Caught exception
org.jboss.jms.util.MessagingJMSException: Caught exception
at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:99)
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:253)
at sun.reflect.GeneratedMethodAccessor130.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:130)
at org.jboss.jms.client.delegate.ClientProducerDelegate$send_3961598017717988886.invokeNext(ClientProducerDelegate$send_3961598017717988886.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.ClientProducerDelegate$send_3961598017717988886.invokeNext(ClientProducerDelegate$send_3961598017717988886.java)
at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:69)
at org.jboss.jms.client.delegate.ClientProducerDelegate$send_3961598017717988886.invokeNext(ClientProducerDelegate$send_3961598017717988886.java)
at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
at org.jboss.jms.client.delegate.ClientProducerDelegate$send_3961598017717988886.invokeNext(ClientProducerDelegate$send_3961598017717988886.java)
at org.jboss.jms.client.delegate.ClientProducerDelegate.send(ClientProducerDelegate.java)
at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:172)
at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:220)
at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:147)
at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:138)
at com.mycom.sphere.postcrawler.services.mq.LinkDiscoveryMQProducer.publish(LinkDiscoveryMQProducer.java:50)
at
...

any help would be appreciated.
Nick.

[clebert.suconic]

In your try... catch do something like this:

try
{
}
catch (JMSException e)
{
 e.getLinkedException().printStackTrace();
 e.printStackTrace();
}

That will give you more clue about what's going on with that exception.

I will see the possibility of calling initCause(cause) on future releases.



Also.. if you have you log4j setting in your client, these exceptions are being sent to the log output.