New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ClientReAuthOperation can not return response without call-id! #1816

pveentjer opened this Issue Feb 19, 2014 · 0 comments


None yet
2 participants

pveentjer commented Feb 19, 2014

When running a cluster that is accessed using a client, and keep on starting/stopping members in this cluster, I get the following exception. I think it is because the ClientReAuthOperation says it returns a response, but it isn't send in the system using the regular way (e..g invoke on target), but using the OperationService.send.

I think the fundamental problem is that the ClientReAuthOperation should not return a response.

20:14:40,139 FATAL [OperationService] - []:5705 [dev] [3.2-RC2-SNAPSHOT] Op: com.hazelcast.client.ClientReAuthOperation can not return response without call-id!
    com.hazelcast.core.HazelcastException: Op: com.hazelcast.client.ClientReAuthOperation can not return response without call-id!
at com.hazelcast.spi.impl.ResponseHandlerFactory.createRemoteResponseHandler(
at com.hazelcast.spi.impl.ResponseHandlerFactory.setRemoteResponseHandler(
at com.hazelcast.spi.impl.BasicOperationService.processPacket(
at com.hazelcast.spi.impl.BasicOperationService.access$900(
at com.hazelcast.spi.impl.BasicOperationService$BasicOperationProcessorImpl.process(
at com.hazelcast.spi.impl.BasicOperationScheduler$
at com.hazelcast.util.executor.ManagedExecutorService$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$
at com.hazelcast.util.executor.PoolExecutorThreadFactory$

@pveentjer pveentjer added this to the 3.2 milestone Feb 19, 2014

@pveentjer pveentjer self-assigned this Feb 19, 2014

@gurbuzali gurbuzali modified the milestones: 3.1.6, 3.2 Feb 19, 2014

@pveentjer pveentjer modified the milestones: 3.1.7, 3.1.6 Feb 19, 2014

@pveentjer pveentjer referenced this issue Feb 19, 2014


Fixes #1816 #1820

@pveentjer pveentjer closed this in 2eab516 Feb 19, 2014

pveentjer added a commit that referenced this issue Feb 20, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment