|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Steve Ebersole, Scott Marlow and I were discussing solutions for this. Although we don't like it, it seems a route may be for afterCompletionAction to set a "clear the session" synchronized flag, rather than doing it on its own, to prevent reaper threads from using the session unsafely. But then the question is where all does the flag get checked?
Thoughts? Alternatives?