Skip to content
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

Warning level exception when shutting down the client #10291

Closed
alparslanavci opened this issue Apr 10, 2017 · 0 comments
Closed

Warning level exception when shutting down the client #10291

alparslanavci opened this issue Apr 10, 2017 · 0 comments

Comments

@alparslanavci
Copy link
Contributor

@alparslanavci alparslanavci commented Apr 10, 2017

When shutting down a client with a topic subscription, it logs a warning level excepiton which seems harmless. But it is not good to log a harmless exception as warning. See the stacktrace below:

2017-04-06 16:15:45,715 WARN [main] com.hazelcast.client.proxy.ClientReliableTopicProxy - hz.client_1 [dev] [3.8] Terminating MessageListener TopicMessageLostTest$MyClient@6075b2d3 on topic: my-topic. Reason: Unhandled exception, message: Internal executor rejected task: com.hazelcast.spi.impl.AbstractInvocationFuture$1@160396db, because client is shutting down... 
java.util.concurrent.RejectedExecutionException: Internal executor rejected task: com.hazelcast.spi.impl.AbstractInvocationFuture$1@160396db, because client is shutting down... 
at com.hazelcast.client.spi.impl.ClientExecutionServiceImpl$2.rejectedExecution(ClientExecutionServiceImpl.java:81) ~[hazelcast-all-3.8.jar:3.8] 
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823) ~[?:1.8.0_102] 
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369) ~[?:1.8.0_102] 
at com.hazelcast.client.spi.impl.ClientExecutionServiceImpl.execute(ClientExecutionServiceImpl.java:98) ~[hazelcast-all-3.8.jar:3.8] 
at com.hazelcast.spi.impl.AbstractInvocationFuture.unblock(AbstractInvocationFuture.java:239) [hazelcast-all-3.8.jar:3.8] 
at com.hazelcast.spi.impl.AbstractInvocationFuture.unblockAll(AbstractInvocationFuture.java:225) [hazelcast-all-3.8.jar:3.8] 
at com.hazelcast.spi.impl.AbstractInvocationFuture.complete(AbstractInvocationFuture.java:362) [hazelcast-all-3.8.jar:3.8] 
at com.hazelcast.client.spi.impl.ClientInvocation.notifyException(ClientInvocation.java:159) [hazelcast-all-3.8.jar:3.8] 
at com.hazelcast.client.spi.impl.ClientInvocationServiceSupport.shutdown(ClientInvocationServiceSupport.java:186) [hazelcast-all-3.8.jar:3.8] 
at com.hazelcast.client.spi.impl.ClientSmartInvocationServiceImpl.shutdown(ClientSmartInvocationServiceImpl.java:31) [hazelcast-all-3.8.jar:3.8] 
at com.hazelcast.client.impl.HazelcastClientInstanceImpl.doShutdown(HazelcastClientInstanceImpl.java:728) [hazelcast-all-3.8.jar:3.8] 
at com.hazelcast.client.impl.LifecycleServiceImpl.shutdown(LifecycleServiceImpl.java:141) [hazelcast-all-3.8.jar:3.8] 
at com.hazelcast.client.impl.HazelcastClientProxy.shutdown(HazelcastClientProxy.java:285) [hazelcast-all-3.8.jar:3.8] 
at TopicMessageLostTest$MyClient.stop(TopicMessageLostTest.java:104) [classes/:?] 
at TopicMessageLostTest.test(TopicMessageLostTest.java:53) [classes/:?] 
at TopicMessageLostTest.main(TopicMessageLostTest.java:29) [classes/:?]
@sancar sancar added this to the 3.8.2 milestone Apr 10, 2017
@sancar sancar self-assigned this Apr 13, 2017
sancar added a commit to sancar/hazelcast that referenced this issue Apr 13, 2017
sancar added a commit to sancar/hazelcast that referenced this issue Apr 14, 2017
Because of shutdown order of events, invocation was getting
RejectedExecutionException from EventService rather than
HazelcastClientNotActiveException.
Both the shutdown order fix and handling the Exception is added to pr.

fixes hazelcast#10291
sancar added a commit to sancar/hazelcast that referenced this issue Apr 14, 2017
Because of shutdown order of events, invocation was getting
RejectedExecutionException from EventService rather than
HazelcastClientNotActiveException.
Both the shutdown order fix and handling the Exception is added to pr.

fixes hazelcast#10291
sancar added a commit to sancar/hazelcast that referenced this issue Apr 14, 2017
Because of shutdown order of events, invocation was getting
RejectedExecutionException from EventService rather than
HazelcastClientNotActiveException.
Both the shutdown order fix and handling the Exception is added to pr.

fixes hazelcast#10291
sancar added a commit to sancar/hazelcast that referenced this issue Apr 14, 2017
Because of shutdown order of events, invocation was getting
RejectedExecutionException from EventService rather than
HazelcastClientNotActiveException.
Both the shutdown order fix and handling the Exception is added to pr.

fixes hazelcast#10291
sancar added a commit to sancar/hazelcast that referenced this issue Apr 17, 2017
Because of shutdown order of events, invocation was getting
RejectedExecutionException from EventService rather than
HazelcastClientNotActiveException.
Both the shutdown order fix and handling the Exception is added to pr.

fixes hazelcast#10291
sancar added a commit to sancar/hazelcast that referenced this issue Apr 17, 2017
Because of shutdown order of events, invocation was getting
RejectedExecutionException from EventService rather than
HazelcastClientNotActiveException.
Both the shutdown order fix and handling the Exception is added to pr.

fixes hazelcast#10291
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

3 participants
You can’t perform that action at this time.