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.
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
Fix session affinity management (stickiness) in wildfly-http-client #108
base: main
Are you sure you want to change the base?
Fix session affinity management (stickiness) in wildfly-http-client #108
Changes from 1 commit
6c2c255
75162be
782f815
fddb756
75b0292
a359156
c0b9a42
5c637e4
9e059aa
c4d7336
6252596
88560f4
2fdb50f
d2383e7
891ea3a
a4b8e61
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Is this the best way to add this here? I think that having a blocking invocation at the HttpEJBReceiver will just cause the receiver thread to hold while the other end is responding and this could lead to numerous blocking thread issues.
Ideally, we need a way of having this information available before createSession kicks in, or at least an analysis (maybe you already did that analysis and already know the answer to this question) of why this won't cause thread issues.
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.
If that's the case, then someone else needs to have a look at this particular issue and do an analysis. It would need to be you or Richard or Paul. The problem is that the code for initializing a transaction and marshaling the transactional state into the invocation (in HttpTargetContext.writeTransaction()) is extremely tightly coupled, and didn't easily allow initializing the transaction (on a backend server chosen by the load balancer) and then using the resulting URI as a target for the invocation.