Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
MessageContextAware leads to possible issues in a multithreaded environment
possible solutions:
#1 MessageContext#cloneContext uses a deep copy to get instances which aren't shared between threads
#2 synchronization based on the shared instances of MessageContextAware
#3 forward the current context as parameter instead of using MessageContextAware
#1 and #2 lead to possible performance issues -> #3 should be used to solve the issue