[jboss-user] [JBoss Messaging] - Re: no exception callback for JBM clients when server detect

[bodrin]

I have one more scenario regarding missing onException callback:

1. Starting cluster node0.
2. Starting standalone consumer.
3. Starting standalone producer - consumer receives the messages
4. Starting cluster node1.
5. kill cluster node0
6. Starting standalone producer - consumer receives the messages
7. kill cluster node1 - no exception callback on the consumer
Again the consumer things it is connected, but it is not, because the whole cluster is shutdown.

the console log of cluster node1:

  | 10:53:11,569 INFO  [TreeCache] viewAccepted(): [10.58.100.162:32864|2] [10.58.100.162:32864]
  | 10:53:11,570 INFO  [SEPMessageCluster] New cluster view for partition SEPMessageCluster (id: 2, delta: -1) : [10.58.100.162:1299                             ]
  | 10:53:11,572 ERROR [SocketClientInvoker] Got marshalling exception, exiting
  | java.net.SocketException: end of file
  |         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:604)
  |         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:418)
  |         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
  |         at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
  |         at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
  |         at java.util.TimerThread.mainLoop(Timer.java:512)
  |         at java.util.TimerThread.run(Timer.java:462)
  | 10:53:11,581 INFO  [SEPMessageCluster] I am (10.58.100.162:1299) received membershipChanged event:
  | 10:53:11,581 INFO  [SEPMessageCluster] Dead members: 1 ([10.58.100.162:1199])
  | 10:53:11,581 INFO  [SEPMessageCluster] New Members : 0 ([])
  | 10:53:11,581 INFO  [SEPMessageCluster] All Members : 1 ([10.58.100.162:1299])
  | 10:53:11,586 INFO  [MessagingPostOffice] JBoss Messaging is failing over for failed node 0. If there are many messages to reload this may take some time...
  | 10:53:11,742 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://blade8.localdomain:4557/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
  | 10:53:11,743 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[1e42d5a, bisocket://blade8.localdomain:4557](a1m2s4i-vj7cpa-fdpndt5y-1-fdpnee9y-a)] failed sending disconnect for client lease for client with session ID a1m2s4i-vj7cpa-fdpndt5y-1-fdpnee9w-8
  | 10:53:11,744 ERROR [MicroRemoteClientInvoker] error shutting down lease pinger
  | 10:53:11,748 INFO  [MessagingPostOffice] JBoss Messaging failover completed
  | 10:53:30,089 WARN  [SimpleConnectionManager] ConnectionManager[f38b42] cannot look up remoting session ID a1m2s4i-k5q34x-fdpnbj60-1-fdpnef10-10
  | 10:53:30,089 WARN  [SimpleConnectionManager] A problem has been detected with the connection to remote client a1m2s4i-k5q34x-fdpnbj60-1-fdpnef10-10, jmsClientID=null. It is possible the client has exited without closing its connection(s) or the network has failed. All connection resources corresponding to that client process will now be removed.
  | 
  | [root at blade8 jboss-4.2.2.GA-JBM-1.4.0.SP3]#
  | 
  | 



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135848#4135848

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135848