Attempt to force executions to be synchronized if JTA trans. is present #7004
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JiriOndrusek
force-pushed
the
CAMEL-1747_deadlock-WIP
branch
from
0fd8682 to
c62136f
Compare
Contributor
|
Thanks @JiriOndrusek and I made some progress to mark the exchange transacted in |
Contributor
|
@JiriOndrusek can you close this PR since we alreday have a fix for camel-jta. |
Contributor
|
closing PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue https://issues.apache.org/jira/browse/CAMEL-17474
Problem is caused by the fact, that JTA transactions requires synchronous execution (see comment)
There is a change (a few months ago), which changed default executions to be asynchronous and causes deadlocks.
I added a test created by @zhfeng
The whole code change is only POC whether this kind of change would help. (it seems to be working successfully)
Mainly I'm not sure about
JtaTransactionPolicy.beforeWrap. But it is essential to set flag to the route's error handler factory, to make this idea work.I would appreciate any kind of help/review//response to this PR. (as I'm not even sure whether this is the right idea to implement)