long live consumer stops working| JBoss.org Content Archive (Read Only)

15. Re: long live consumer stops working

timfox Feb 1, 2008 11:31 AM (in response to bodrin)

"bodrin" wrote:
It is strange that the messaging is using some configuration inside $JBOSS_HOME/docs/examples.

Don't blame messaging! It is using the config from there because you (or someone else on your side) configured it to use that. Do a search in the wiki for ServiceBindingManager to find out more.

You are getting the warning on the server because the server thinks the client has suddenly died.

This is because you are either killing the client suddenly or in your code you are exiting without closing your connections properly.

16. Re: long live consumer stops working

bodrin Feb 1, 2008 11:46 AM (in response to bodrin)

Don't blame messaging!..

I just wonder if I'm understanding the installation steps correctly..

But, as I said I reproduce the problem, then I kill the long-live-consumer (bacause it does not receive anything) and then the warning appears. So, this is not related to the problem itself, right?

17. Re: long live consumer stops working

timfox Feb 3, 2008 9:33 AM (in response to bodrin)

http://jira.jboss.org/jira/browse/JBMESSAGING-1228

18. Re: long live consumer stops working

bodrin Feb 6, 2008 2:59 AM (in response to bodrin)

Thanks!

So, now we move the discussion to JIRA? Or I just wait you to reproduce the problem and analyse it?

19. Re: long live consumer stops working

ataylor Feb 14, 2008 11:26 AM (in response to bodrin)

Ive investigated this Jira following your steps precisely and there were no problems with the consumer. I can only assume that maybe you have network problems that are causing this as Clebert previously mentioned.

20. Re: long live consumer stops working

bodrin Feb 18, 2008 3:23 AM (in response to bodrin)

Ok.
So, I think there should be some error/warning log(s) in case of network problems at least?

How can I switch the logging level of JBM and jboss-remoting and the other related modules ?

I can also reproduce the problem and debug it myself. I just need some directions. I have already tried to debug the client side (the consumer), but there are only two threads blocked on a socket.read(). I haven't yet tried to debug the Jboss side of the JBM/remoting.

21. Re: long live consumer stops working

timfox Feb 18, 2008 5:52 AM (in response to bodrin)

I would double check again that you haven't changed any of the remoting settings from those in the distribution.

If you are using service binding manager, ensure you have copied *exactly* those settings from the ones in the distro.

22. Re: long live consumer stops working

ebenezersamuel Jun 10, 2008 12:49 PM (in response to bodrin)

I am facing the same problem. I tried to have two instances of Jboss Messaging in a singe Jboss server (messaging-node0 & messaging-node1). I have followed all the steps given in the JBoss Messaging 1.4 User's Guide to create clustered JMS. I am using Jboss 4.2.2 GA with Jboss Messaging 1.4.0 SP3. When I try to run the server, it gives me the following error

11:16:30,875 ERROR [ConnectionFactory] Parameter pingFrequency is not specified in the remoting congiguration
11:16:30,875 ERROR [ExceptionUtil] org.jboss.jms.server.connectionfactory.ConnectionFactory@7a279c startService
java.lang.IllegalArgumentException: Failed to deploy connection factory since remoting configuration seems incorrect.
at org.jboss.jms.server.connectionfactory.ConnectionFactory.startService(ConnectionFactory.java:155)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy52.start(Unknown Source)
at org.jboss.deployment.XSLSubDeployer.start(XSLSubDeployer.java:197)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy10.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:595)

11:16:31,282 WARN [ServiceController] Problem starting service jboss.messaging.connectionfactory:service=ConnectionFactory
java.lang.IllegalArgumentException: Failed to deploy connection factory since remoting configuration seems incorrect.
at org.jboss.jms.server.connectionfactory.ConnectionFactory.startService(ConnectionFactory.java:155)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy52.start(Unknown Source)
at org.jboss.deployment.XSLSubDeployer.start(XSLSubDeployer.java:197)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy10.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:595)

Thanks in advance for any help.

Regards,
Ebe

23. Re: long live consumer stops working

ebenezersamuel Jun 10, 2008 6:52 PM (in response to bodrin)

I got it fixed. As Tim had pointed out, I had the older version of the sample-bindings.xml. Sorry for the trouble.

Regards,
Ebe

24. Re: long live consumer stops working

poonamagarwal Sep 22, 2009 6:56 AM (in response to bodrin)

Hi bodrin,

I am facing a similar issue of connection getting invalidated.
I am using JBM 1.4.0 SP3 and Jboss 4.20GA.
I have a consumer(client) created for a queue(on server).
I am successful in creating a connection and my consumer does receive messages. However, If I leave my server and consumer for sometime may be some(2-4) hours, I see a log trace in my client:

[21 Sep 2009 15:24:02] DEBUG [Timer-3] (ConnectionValidator.java:674) - ConnectionValidator[SocketClientInvoker[1017ca1, bisocket://myserver:4457], pingPeriod=2000 ms]'s connections is invalid
[21 Sep 2009 15:24:02] DEBUG [Timer-3] (InvokerRegistry.java:628) - removed SocketClientInvoker[1017ca1, bisocket://myserver:4457] from registry
[21 Sep 2009 15:24:02] DEBUG [Timer-3] (MicroSocketClientInvoker.java:384) - SocketClientInvoker[1017ca1, bisocket://myserver:4457] disconnecting ...
[21 Sep 2009 15:24:02] DEBUG [Timer-3] (SocketWrapper.java:127) - ClientSocketWrapper[Socket[addr=/myserver,port=4457,localport=4198].7f6b72] closing socket
[21 Sep 2009 15:24:02] DEBUG [Timer-3] (SocketWrapper.java:129) - ClientSocketWrapper[Socket[addr=/myserver,port=4457,localport=4198].7f6b72] closed socket
[21 Sep 2009 15:24:02] DEBUG [Timer-3] (SocketWrapper.java:127) - ClientSocketWrapper[Socket[addr=/myserver,port=4446,localport=4197].1673ef7] closing socket
[21 Sep 2009 15:24:02] DEBUG [Timer-3] (SocketWrapper.java:129) - ClientSocketWrapper[Socket[addr=/myserver,port=4446,localport=4197].1673ef7] closed socket
[21 Sep 2009 15:24:02] DEBUG [Timer-3] (SocketWrapper.java:127) - ClientSocketWrapper[Socket[addr=/myserver,port=4457,localport=4199].156cce6] closing socket
[21 Sep 2009 15:24:02] DEBUG [Timer-3] (SocketWrapper.java:129) - ClientSocketWrapper[Socket[addr=/myserver,port=4457,localport=4199].156cce6] closed socket
[21 Sep 2009 15:24:02] DEBUG [Timer-3] (ConnectionValidator.java:616) - ConnectionValidator[SocketClientInvoker[1017ca1, bisocket://myserver:4457], pingPeriod=2000 ms] stopped, returning true
[21 Sep 2009 15:24:02] DEBUG [Timer-3] (ConnectionValidator.java:680) - org.jboss.remoting.ConnectionValidator$WaitOnConnectionCheckTimerTask@1a62f80 detected connection failure: stopping LeasePinger
[21 Sep 2009 15:24:02] DEBUG [Timer-3] (LeasePinger.java:285) - LeasePinger[SocketClientInvoker[4bb369, bisocket://myserver:4457](4ss82w-n3gywx-fzvb4aaz-1-fzvb4cgo-c)] setting disconnect timeout to: -1
[21 Sep 2009 15:24:02] DEBUG [Timer-3] (ConnectionValidator.java:686) - ConnectionValidator[SocketClientInvoker[1017ca1, bisocket://myserver:4457], pingPeriod=2000 ms] shut down lease pinger
[21 Sep 2009 15:24:07] DEBUG [Thread-11] (ClientSocketWrapper.java:164) - reset timeout: 0

This kills my consumer which will no longer receive any messages from the server. How do I solve this problem?
1. How do I create a long live consumer in first place? I could not visit the examples sent by bodrin.
2. Should I listen for such disconnects and try to re-establish the connection on such disconnect? Where should I catch the disconnect exception?
3. What am I missing here?

Can somebody please help.
-Poonam.

25. Re: long live consumer stops working

simo.nikula1 Jan 26, 2010 9:56 AM (in response to poonamagarwal)

Hi

I've been studing quite similar issue and there are many things to consider.

If you have firewall this may be helpful

http://blog.akquinet.de/2009/09/30/using-jboss-messaging-in-a-firewalled-environment-the-toll-road/

I'm also facing network problems that cannot be fixed as temporary problems are typical nature of those networks.

In those cases few messages are left in queue every now and then. I'm still searching for proper solution but so far I've analyzed that those

problems come like this:

- client ping fails (also close fails with message cannot write CLOSING byte)

- server sends message without knowledge that client is no more alive

- after while server detects that client has not pinged it and logs error message and tries to close socket. These sockets can be detected by e.g. netstat and I run watchdog that restarts server after some amount of those CLOSE_WAIT (>5) sockets are found.

Message are delivered after server restart and FailoverCompleteTimeout.

Basically state is quite manageable but it is not nice to admit that we are restarting both our jboss servers for this cluster about 10 times per day.

Currently I'm testing socket.check_connection true in remoting-bisocket-service.

Having slow connection (512 kb) between client and servers makes testing easier than at redhat where this problem has not been able to be reproduced. client.FailoverCommandCenter can be usually activated by doing 2MB upload.

Simo

26. Re: long live consumer stops working

jselvin Mar 28, 2011 3:45 PM (in response to simo.nikula1)

Hi,

I am observing similar issue in my application. We are using Jboss 4.2.0.GA, Jboss Remoting 2.5.3.SP1

We have a firewall between our server and client and we followed the forum,

http://blog.akquinet.de/2009/09/30/using-jboss-messaging-in-a-firewalled-environment-the-toll-road/

to set our parameters like below,

<attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>

<attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>

<attribute name="dataType" isParam="true">jms</attribute>

<attribute name="socket.check_connection" isParam="true">true</attribute>

<attribute name="serverBindAddress">${jboss.bind.address}</attribute>

<attribute name="serverBindPort">4457</attribute>

<attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>

<attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>

<attribute name="numberOfCallRetries" isParam="true">5</attribute>

<attribute name="pingFrequency" isParam="true">5000</attribute>

<attribute name="pingWindowFactor" isParam="true">2</attribute>

<attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool</attribute>

<attribute name="stopLeaseOnFailure" isParam="true">true</attribute>

<attribute name="clientLeasePeriod" isParam="true">10000</attribute>

<attribute name="validatorPingPeriod" isParam="true">10000</attribute>

<attribute name="validatorPingTimeout" isParam="true">5000</attribute>

<attribute name="failureDisconnectTimeout" isParam="true">0</attribute>

<attribute name="callbackErrorsAllowed">1</attribute>

<attribute name="registerCallbackListener">false</attribute>

<attribute name="useClientConnectionIdentity" isParam="true">true</attribute>

<attribute name="timeout" isParam="true">1800000</attribute>

<attribute name="numberOfRetries" isParam="true">10</attribute>

<attribute name="JBM_clientMaxPoolSize" isParam="true">200</attribute>

<attribute name="callbackTimeout">10000</attribute>

<attribute name="secondaryBindPort">4481</attribute>

With this implementation, we have mulitple Connections in CLOSE_WAIT state most of them getting cleared and some left behind.

After several days, we loose the JMS communication. We need to restart the application again to get rid off.

Also we observed the below exception multiple times when the issue happens,

Exception:

2011-03-28 11:50:10,271 TRACE [org.jboss.remoting.transport.socket.ServerThread(638)](WorkerThread#4[10.255.254.134:42933]) WorkerThread#4[10.255.254.134:42933] EOFException received. This is likely due to client finishing communication.

java.io.EOFException

at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:740)

at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:586)

at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234)

Kindly share some light to resolve this.

Regards,

Joseph.

27. Re: long live consumer stops working

simo.nikula1 Mar 29, 2011 1:42 AM (in response to jselvin)

My similar problems disappeared after updating

components to versions: jboss-remoting-2.5.3.SP1, jboss-messaging-1.4.7.GA, jgroups-2.6.13.GA

If you are not using clustered JMS, jgroups is not relevant.

28. Re: long live consumer stops working

jselvin Mar 29, 2011 5:09 PM (in response to simo.nikula1)

Hi Simo Nikula,

Thank you so much for the response.

I have issues while using the above said versions.

I have to stick with Jboss 4.2 and Java 1.5 version in my application.

But jboss-messaging-1.4.7.GA depends on AOP and many other third party libraries.

1) Kindly let me know what all dependent jars you added to make them work.

2) What version of JBoss you are using.

3) Is there any readme file for the jboss messaging releases(also let me know the location of the repository you have downloaded).

Regards,

Joseph.

29. Re: long live consumer stops working

simo.nikula1 Apr 1, 2011 11:29 AM (in response to jselvin)

Hi

1-2) I'm using jboss-5.0.1.GA with above mentioned updates with java 1.6.0_13 but 1.5 should be as good or even better tested

3) http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_7_GA/

Simo