-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Client disconnect leads to stucked clusterExecutor shutdown (3.6.2) #8721
Comments
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Dec 21, 2016
Launch a new thread when client needs to be closed from cluster thread. fixes hazelcast#8721
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Dec 21, 2016
Launch a new thread when client needs to be closed from cluster thread. fixes hazelcast#8721
This was referenced Dec 21, 2016
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Dec 21, 2016
Launch a new thread when client needs to be closed from cluster thread. fixes hazelcast#8721
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Dec 21, 2016
Launch a new thread when client needs to be closed from cluster thread. fixes hazelcast#8721
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Dec 23, 2016
Launch a new thread when client needs to be closed from cluster thread. fixes hazelcast#8721
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Dec 23, 2016
Launch a new thread when client needs to be closed from cluster thread. fixes hazelcast#8721
sancar
pushed a commit
to sancar/hazelcast
that referenced
this issue
Dec 23, 2016
Launch a new thread when client needs to be closed from cluster thread. fixes hazelcast#8721
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have two apps deployed on different VM's. First app connects to another as Hazelcast Client.
As soon second app goes down, client starts reconnection as expeced. Finally the client says
and goes to
ClusterListenerSupport:233
to shutdown LifecycleService.After some components shutdowns, called
ClusterListenerSupport.shutdown
And the component tries to shutdown clusterExecutor and stucked for
TERMINATE_TIMEOUT_SECONDS
because the task is launched inside this clusterExecutor.Here is screen from debug view
![b2008d0b19](https://cloud.githubusercontent.com/assets/1476017/17664601/f59af734-62fd-11e6-9279-64f2a158ef30.jpg)
Log says:
This issue reproduces permanently and only after target instance goes down.
The text was updated successfully, but these errors were encountered: