Hi, Finally, it was a false alarm. See the discussion on the jira : https://issues.apache.org/jira/browse/TAP5-1660
Thanks to Martin, I realized that my sample was not relevant and that the conditioned lock around the holder, in PerthreadManagerImpl, is not a problem and maybe, "in the worst case", only redundant. My original issue is probably related to a side effect from our code since the tapestry 5.2 migration (the issue does not occur when the page pool is enabled). By the way, it's really a pleasure to read the tapestry source code and discuss with the community. Nourredine. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-5-2-Per-thread-scope-services-not-thread-safe-tp4825735p4829505.html Sent from the Tapestry - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
