PAYARA-1585 Async servlet access is not correctly logged #1571
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
|
Jenkins test please |
|
All tests have passed |
lprimak
approved these changes
May 3, 2017
lprimak
pushed a commit
to flowlogix/Payara
that referenced
this pull request
Jul 5, 2017
* Fixed issue payara#1585 * Async start check added to fetch AsyncContext
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.
Issue : Response information is not correctly logged in the HTTP Access log when the web container deals with Asynchronous servlet requests.
Fix : Logging invocation is now done at the completion notification of Asynchronous Context using AsyncListener.
Issue Ref : #1401