I think the necessary fix, which involves (somehow) serializing some operations across threads that share an HttpSession, is out of scope for a drop in bug fix release, don't you think? The solution I've been thinking of will have some pretty wild performance effects, as requests that share sessions will need to be routed through a single lock object, stored in the session.
On Tue, Jun 21, 2011 at 2:54 PM, David Rees <dree...@gmail.com> wrote: > On Tue, Jun 21, 2011 at 2:33 PM, Howard Lewis Ship <hls...@gmail.com> wrote: >> I'm backporting some fixes for a client to 5.2. I expect to have a >> 5.2.6 release ready very soon. Anything critical that needs to go >> into it beyond the Prototype/JS stuff I've been doing? > > I've been seeing more and more of those > "ConcurrentModificationException"s when parallel requests come in from > clients, but I suspect the proper fix for that may be a bit involved. > What about the hack I proposed in that thread? > > http://tapestry.1045711.n5.nabble.com/Rather-worrying-exception-with-5-2-4-java-util-ConcurrentModificationException-tp3370588p3370588.html > > Thanks, BTW for working on a 5.2.6 release - it's good to see bugfix > releases on the stable branch for people using it in production. > > -Dave > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
