PAYARA-179 implement request tracing for inbound JMS messages on an MDB #1068
Conversation
This file contains 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
Also add additional apis for request tracing to view and set the conversation ID
|
Can one of the admins verify this patch? |
|
jenkins test please |
|
All tests have passed |
lprimak
pushed a commit
to flowlogix/Payara
that referenced
this pull request
Jul 5, 2017
…DB (payara#1068) Also add additional apis for request tracing to view and set the conversation ID
|
@smillidge Does Payara support OpenTracing over JMS? |
|
How does Tracing for outbound jms messages work? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Also add additional apis for request tracing to view and set the conversation ID