4 Replies Latest reply on Jun 18, 2009 3:47 AM by sem

Problem with management.esb in cluster

sem Jun 17, 2009 4:07 AM

I'm trying to configure JBOSS ESB 4.3 in cluster ( using JBOSS messaging clustering)
everything looks fine except monitoring
after sometime running without any problem I have following log apearing every 10 minutes in server.log file

2009-06-17 00:09:53,474 ERROR [org.jboss.soa.esb.monitoring.server.DataFilerJob]
org.jboss.soa.esb.couriers.CourierTransportException: Caught exception during delivery having successfully recovered!
at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:268)
at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:213)
at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:189)
at org.jboss.soa.esb.monitoring.server.DataFilerJob.execute(DataFilerJob.java:84)
at org.quartz.core.JobRunShell.run(JobRunShell.java:203)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
Caused by: org.jboss.jms.exception.MessagingJMSException: Failed to invoke
at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:271)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:205)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160)
at org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$send$aop(ClientSessionDelegate.java:499)
at org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java)
at org.jboss.jms.client.container.SessionAspect.handleSend(SessionAspect.java:661)
at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect28.invoke(SessionAspect28.java)
at org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java)
at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java)
at org.jboss.jms.client.delegate.ClientSessionDelegate.send(ClientSessionDelegate.java)
at org.jboss.jms.client.container.ProducerAspect.handleSend(ProducerAspect.java:269)
at org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect39.invoke(ProducerAspect39.java)
at org.jboss.jms.client.delegate.ClientProducerDelegate$send_3961598017717988886.invokeNext(ClientProducerDelegate$send_3961598017717988886.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
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:164)
at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:207)
at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:145)
at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:136)
at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:264)
... 5 more
Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id s2-3wok5zvf-1-gsza5zvf-j40z2x-x1kwa
at org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(SessionSendRequest.java:101)
at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:866)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:420)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
at org.jboss.remoting.Client.invoke(Client.java:1634)
at org.jboss.remoting.Client.invoke(Client.java:548)
at org.jboss.remoting.Client.invoke(Client.java:536)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)
... 30 more

Does anyone knows how to fix this?
thanks in advance
Sem

1. Re: Problem with management.esb in cluster

kaba Jun 17, 2009 8:54 AM (in response to sem)

Hello sem
i would like to cluster the JBossESB, would you mind describing the stps, that i need to take to cluster?
Thank you

/Kaba
Actions
2. Re: Problem with management.esb in cluster

sem Jun 17, 2009 10:01 AM (in response to sem)

I just followed Administrator guide.
All scenarios are explained there
Actions
3. Re: Problem with management.esb in cluster

tcunning Jun 18, 2009 1:27 AM (in response to sem)

What you have looks like a JMS error. My suggestion would be to just remove management.esb for now. You will still be able to monitor in real time using the jmx-console (and have access to all of the same metrics), but it will stop collecting data and you will not see this error again.
Actions
4. Re: Problem with management.esb in cluster

sem Jun 18, 2009 3:47 AM (in response to sem)

This is might be good idea for test system, but I would like to have data collection working on production. Is it something wrong in management.esb configuration to make it work in the cluster or did I made some mistake in my cluster config ?
Actions

Go to original post