carbon-business-messaging icon indicating copy to clipboard operation
carbon-business-messaging copied to clipboard

Error on failover : Cannot send response: [com.hazelcast.topic.impl.reliable.ReliableTopicMessage@20d79721] to Address[192.168.1.22]:4000

Open Subasinghe opened this issue 7 years ago • 0 comments

  1. Have 3 nodes as mb1, mb2, mb3.
  2. Publish queue messages with a roundrobin sequence of mb1, mb2 and then mb3.
  3. Kill mb1. Wait sometime.
  4. Kill mb2.
  5. The following log is printed twice on the mb3 node's console.
[2015-09-17 18:22:03,127] INFO
{org.wso2.andes.thrift.MBThriftClient}

- Reconnecting to Slot Coordinator 192.168.1.22:7611
[2015-09-17 18:23:00,941] INFO
{org.wso2.andes.kernel.AndesChannel} - Channel created (ID: 2)
[2015-09-17 18:23:00,941] INFO {org.wso2.andes.kernel.AndesChannel}

- Channel created (ID: 3)
[2015-09-17 18:23:01,005] INFO
{org.wso2.andes.subscription.SubscriptionStore}

- Local subscription ADDED [MyQueue]ID=0@node55/T=1442494380976/D=true/X=false/O=null/E=amq.direct/ET=org.wso2.andes.server.exchange.DirectExchange$1@7a5fd768/EUD=0/S=true
Sep 17, 2015 6:23:01 PM com.hazelcast.ringbuffer.impl.operations.ReadManyOperation
SEVERE: [192.168.1.55]:4000 [wso2.carbon.domain] [3.5] Cannot send response: [com.hazelcast.topic.impl.reliable.ReliableTopicMessage@20d79721] to Address[192.168.1.22]:4000
com.hazelcast.core.HazelcastException: Cannot send response: [com.hazelcast.topic.impl.reliable.ReliableTopicMessage@20d79721] to Address[192.168.1.22]:4000
at com.hazelcast.spi.impl.ResponseHandlerFactory$RemoteInvocationResponseHandler.sendResponse(ResponseHandlerFactory.java:131)
at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.handleResponse(OperationRunnerImpl.java:204)
at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:138)
at com.hazelcast.spi.impl.operationexecutor.classic.ClassicOperationExecutor.runOnCallingThread(ClassicOperationExecutor.java:380)
at com.hazelcast.spi.impl.operationservice.impl.OperationServiceImpl.runOperationOnCallingThread(OperationServiceImpl.java:252)
at com.hazelcast.spi.impl.waitnotifyservice.impl.WaitNotifyServiceImpl.notify(WaitNotifyServiceImpl.java:128)
at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.afterRun(OperationRunnerImpl.java:213)
at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:139)
at com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.processOperation(OperationThread.java:154)
at com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.process(OperationThread.java:110)
at com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.doRun(OperationThread.java:101)
at com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.run(OperationThread.java:76)

[2015-09-17 18:23:01,331] INFO
{org.wso2.andes.server.cluster.coordination.hazelcast.AndesMembershipListener}

- Handling cluster gossip: A member left the cluster. Member Socket Address:/192.168.1.22:4000 UUID:0d465034-d186-4bc9-83bb-cc8dc24f9041

with reference to : https://wso2.org/jira/browse/MB-1317

Subasinghe avatar Jun 12 '17 11:06 Subasinghe