Skip to content

ARTEMIS-6066 deadlock with Core federation consumer#6452

Open
jbertram wants to merge 1 commit into
apache:mainfrom
jbertram:ARTEMIS-6066
Open

ARTEMIS-6066 deadlock with Core federation consumer#6452
jbertram wants to merge 1 commit into
apache:mainfrom
jbertram:ARTEMIS-6066

Conversation

@jbertram
Copy link
Copy Markdown
Contributor

I was unable to reproduce the deadlock with a test so static analysis will have to suffice here. The solution has the benefit of being alongside another bit of code that is explicitly identified as necessary to prevent deadlocks.

I was unable to reproduce the deadlock with a test so static analysis
will have to suffice here. The solution has the benefit of being
alongside another bit of code that is explicitly identified as necessary
to prevent deadlocks.
@@ -786,7 +786,6 @@ private void failoverOrReconnect(final Object connectionID,
sessionsToClose = new HashSet<>(sessions);
}
callFailoverListeners(FailoverEventType.FAILOVER_FAILED);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jbertram why this call wasn't moved with the other?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't move this call because it's not directly related to this deadlock. The thread dump on ARTEMIS-6066 shows that there's no problem with this call since it completes before the call to callSessionFailureListeners.

I suppose it's possible that this call should be moved as well, but I was trying to minimize the changes to only what was necessary to resolve this particular deadlock.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants