Skip to content

Conversation

@ihsandemir
Copy link
Collaborator

@ihsandemir ihsandemir commented Jun 19, 2017

Prevented ConnectionManager::shutdown to throw any exception.

Reverted the order of InvocationService shutdown and ConnectionManager shutdown in order to eliminate any unnecessary retries happening during client shutdown, and prevent these retries causing any exceptions. Note that InvocationService::shutdown is only setting a boolean flag.

At Java client, there is a CleanResourcesTask which periodically performs the cleanup of invocations. We really need such a task implemented in the future.

fixes #258

Reverted the order of InvocationService shutdown and ConnectionManager shutdown in order to eliminate any unnecessary retries happening during client shutdown, and prevent these retries causing any exceptions. Note that InvocationService::shutdown is only setting a boolean flag.

At Java client, there is a CleanResourcesTask which periodically performs the cleanup of invocations. We really need such a task implemented in the future.
@ihsandemir ihsandemir added this to the 3.8.2 milestone Jun 19, 2017
@ihsandemir ihsandemir self-assigned this Jun 19, 2017
@ihsandemir ihsandemir requested a review from sancar June 19, 2017 13:50
@devOpsHazelcast
Copy link
Contributor

Test FAILed.

@ihsandemir
Copy link
Collaborator Author

verify

@devOpsHazelcast
Copy link
Contributor

Test PASSed.

…ethod.

Fix: Set the handler registration id correctly, previously we left it as unset (empty) which indirectly caused the removals of the registration to fail.
@devOpsHazelcast
Copy link
Contributor

Test FAILed.

@ihsandemir
Copy link
Collaborator Author

verify

@devOpsHazelcast
Copy link
Contributor

Test PASSed.

…ycleService::isOpen instead. Also, suppressed some logs printed during shutdown. Updated the start sequence to start the InvocationService start before ConnectionManager start (currently InvocationService::start is no-op). Updated shutdown sequence to shutdown PartitionService before ConnectionManager.
@devOpsHazelcast
Copy link
Contributor

Test PASSed.

@ihsandemir ihsandemir changed the title ConnectionManager::shutdown should not throw any exception ConnectionManager::shutdown should not throw any exception and ClusterTest.testListenersWhenClusterDown fails Jun 20, 2017
@ihsandemir ihsandemir merged commit 8e3e18f into hazelcast:master Jun 20, 2017
@ihsandemir ihsandemir deleted the connMgrShutdownNoException branch June 20, 2017 12:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ClusterTest.testListenersWhenClusterDown failed at nightly tests cpp-centos7-nightly-32-STATIC-Release

3 participants