Thanks for the explanations. We had a situation where a Resource was inadvertently wired in using Spring's default "singleton" scope. Fortunately under high load we did see concurrency conflicts show up when setting Status. The easy fix was using the static thread-local accessor, but the true fix was creating the Resource per request. I wanted to make sure I fully understood getResponse() before putting it back in our code.
- 1.1m4 release notes --- Added a static “current” property... Patrick Logan
- Re: 1.1m4 release notes --- Added a static “curren t”... Stephan Koops
- RE: 1.1m4 release notes --- Adde d a static “curr... Jerome Louvel
- Re: 1.1m4 release notes --- Added a static “c... Tim Peierls
- Re: 1.1m4 release notes --- Added a stati... Rob Heittman
- Re: 1.1m4 release notes --- Added a static “... Patrick Logan
- RE: 1.1m4 release notes --- Added a stati... Jerome Louvel
- Re: 1.1m4 release notes --- Added a ... Tim Peierls
- Re: 1.1m4 release notes --- Added ... Patrick Logan
- RE: 1.1m4 release notes --- Ad... Jerome Louvel
- Re: 1.1m4 release notes --- Ad... Tim Peierls
- RE: 1.1m4 release notes --- Ad... Jerome Louvel
- Re: 1.1m4 release notes --- Ad... Tim Peierls
- RE: 1.1m4 release notes --- Ad... Jerome Louvel
- Re: 1.1m4 release notes --- Ad... Tim Peierls
- RE: 1.1m4 release notes --- Ad... Jerome Louvel