-
Notifications
You must be signed in to change notification settings - Fork 319
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
Excluding Spring-JMS specific Runnable from the concurrent plugin #1496
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1496 +/- ##
============================================
+ Coverage 59.31% 69.02% +9.70%
- Complexity 92 2625 +2533
============================================
Files 392 268 -124
Lines 17632 11721 -5911
Branches 2445 1542 -903
============================================
- Hits 10458 8090 -2368
+ Misses 6458 3112 -3346
+ Partials 716 519 -197
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The overall approach LGTM, but tests are failing. Is it related to this PR?
It must be, but probably related to the concurrency plugin dependency. Checking... |
Apparently what happened is that since a transaction is created and activated before each test starts, then when registering a I split the Spring test into a separate module that has the dependencies on Spring JMS and on the concurrency plugin. |
And now the |
What does this PR do?
Yet another stab on fixing the issue reported in the forum, without losing context propagation for JMS-poll-transactions altogether and with minimal effect on anything else.
Supersedes #1483.
Checklist