Hi, Since Tapestry 5.2, it seems that per-thread scope services are not thread-safe (some of our integration tests executed in parallel fail since Tapestry 5.2).
We do not obtain a new instance of the service for each request/thread as expected. That leads to strange behaviour when you use the Environmental services as data's container for example. I also noticed that the synchronization of some resources (used by per-thread scope services) is effective only for jdk 1.5 (see PerthreadmanagerImpl's constructor and JDUtils.JDK_1_5). But this aspect does not explain everything : the pb occurs with JDK 1.5 too. Has someone already experimented that pb? should I raise a JIRA? (I can provide a sample that reproduces the issue) Nourredine. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-5-2-Per-thread-scope-services-not-thread-safe-tp4825735p4825735.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]
