Deregistration of listener with id failed

56 views
Skip to first unread message

Prashant choudhary

unread,
Jan 24, 2017, 8:17:24 AM1/24/17
to Hazelcast
Hi,

I have three member node running on the same or different machine.  I have java client which is adding a listener to a map.

getRequestCache().addEntryListener(new MyTestRequestEntryListener(), true);


Order of start 
Node1
Client
Node2
Node3


My java client is able to receive all the events on the particular map. If I forcefully stop Node1 then I get the exception below and java client not able to receive the events. But it works fine if I stop Node2 or Node3.  It looks like if a client is connected to particular cluster member then and not able to failover to another member.

Jan 24, 2017 6:29:15 PM com.hazelcast.client.spi.ClientListenerService
WARNING: hz.client_0 [dev1] [3.7.4] Deregistration of listener with id 4146cebc-0821-47a9-88e3-026ee0aad004 has failed to member Member [192.168.0.116]:5701 - 2e813fc6-ad8e-4cf3-a9f6-a9fdb06e9295
java.util.concurrent.TimeoutException
at com.hazelcast.client.spi.impl.ClientInvocationFuture.newTimeoutException(ClientInvocationFuture.java:55)
at com.hazelcast.spi.impl.AbstractInvocationFuture.get(AbstractInvocationFuture.java:197)
at com.hazelcast.client.spi.impl.listener.ClientSmartListenerService.deregister(ClientSmartListenerService.java:186)
at com.hazelcast.client.spi.impl.listener.ClientSmartListenerService.reRegisterAll(ClientSmartListenerService.java:377)
at com.hazelcast.client.spi.impl.listener.ClientSmartListenerService.access$300(ClientSmartListenerService.java:52)
at com.hazelcast.client.spi.impl.listener.ClientSmartListenerService$2.run(ClientSmartListenerService.java:122)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:76)
at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:92)


Is someone also faced this issue? Any solution to overcome this?

I am using the latest version 3.7.4.

ih...@hazelcast.com

unread,
Apr 6, 2017, 8:23:27 AM4/6/17
to Hazelcast
Hello,

The listener registration mechanism changed at the latest releases, so I strongly recommend using the latest releases.

Regarding this log at 3.7.4, this log may be OK which is an information that during reregistration, the listener could not be deregistered from the member (is this 2e813fc6-ad8e-4cf3-a9f6-a9fdb06e9295 Node 1 uuid?) But following this, the reregister should continue and register to the existing members. You should be receiving the events unless those registers also failed. Do you have any additional log to suggest that the register also failed?

It needs more investigation but lets also check if you get the problem when you use the latest release jar.

Regards,
ihsan
Reply all
Reply to author
Forward
0 new messages