[
https://jira.jboss.org/jira/browse/JBESB-2324?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2324:
-------------------------------------
Okay, there were actually two bugs involved with this.
- thread local context being cleared during the first post
- context *not* being removed from the original message
The sequence of events were, therefore
- SI invoked, setting context on message and removing thread context
- async invocation but original message still contains context
- back to action (context now in original message, shouldn't be)
- second SI invocation, no thread context to set *but* it already exists in the message
So, if a different message was used then the context would not be propagated.
I have added a unit test to cover these bugs and fixed the SI class. Currently running a
full test run to make sure this does not break assumptions elsewhere.
ServiceInvoker clears security thread local context during post
---------------------------------------------------------------
Key: JBESB-2324
URL:
https://jira.jboss.org/jira/browse/JBESB-2324
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta, Security
Affects Versions: 4.4 CP1, 4.5
Reporter: Kevin Conner
Assignee: Kevin Conner
Fix For: 4.4 CP2, 4.5
Attachments: jboss-esb.xml, jboss-esb.xml, ServiceInvokerAction.java
Subsequent invocations of ServiceInvoker will no longer have access to the context.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira