That is worrying, but I'd appreciate if you can get the more complete stack track from the console. It looks like the failure was inside page.attached() ... and that could be just about anything. It is likely a 3rd party library that is not fully compatible with 5.2.4, and it would be good for everyone to figure out which one.
On Fri, Feb 4, 2011 at 12:10 AM, antalk <[email protected]> wrote: > > Hi, > > Last month i've upgraded our internally used website from Tap 5.1 to 5.2.4, > all went well until i found this disturbing exception in the error log: > > > ERROR 2011-02-03 17:42:56,303 [TP-Processor7][] > org.apache.tapestry5.services.TapestryModule.RequestExceptionHandler - > Processing of > request failed with uncaught exception: Unable to attach page > documents/Received (en): java.util.ConcurrentModificationException > java.lang.RuntimeException: Unable to attach page documents/Received (en): > java.util.ConcurrentModificationException > at > org.apache.tapestry5.internal.services.NonPoolingRequestPageCacheImpl.get(NonPoolingRequestPageCacheImpl.java:82) > at > $RequestPageCache_12dec607e45.get($RequestPageCache_12dec607e45.java) > at > $RequestPageCache_12dec607e3f.get($RequestPageCache_12dec607e3f.java) > at > org.apache.tapestry5.internal.services.AjaxComponentEventRequestHandler.handle(AjaxComponentEventRequestHandler.java:70) > at > org.apache.tapestry5.internal.services.ajax.AjaxFormUpdateFilter.handle(AjaxFormUpdateFilter.java:56) > at > $ComponentEventRequestHandler_12dec608113.handle($ComponentEventRequestHandler_12dec608113.java) > at > $ComponentEventRequestHandler_12dec60810e.handle($ComponentEventRequestHandler_12dec60810e.java) > at > org.apache.tapestry5.internal.services.AjaxFilter.handle(AjaxFilter.java:42) > at > $ComponentEventRequestHandler_12dec60810f.handle($ComponentEventRequestHandler_12dec60810f.java) > at > org.apache.tapestry5.services.TapestryModule$39.handle(TapestryModule.java:2583) > at > $ComponentEventRequestHandler_12dec60810f.handle($ComponentEventRequestHandler_12dec60810f.java) > at > $ComponentEventRequestHandler_12dec607e3c.handle($ComponentEventRequestHandler_12dec607e3c.java) > at > org.apache.tapestry5.internal.services.ComponentRequestHandlerTerminator.handleComponentEvent(ComponentRequestHandlerTerminator.java:43) > > > I have however no clue as who clicked what and where but this seems like > some sort of bug in the new none-pooling page implementation ? > > Best regards, > Antal > > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Rather-worrying-exception-with-5-2-4-java-util-ConcurrentModificationException-tp3370588p3370588.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] > > -- 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: [email protected] For additional commands, e-mail: [email protected]
