On Mon, May 16, 2016 at 11:29 PM, Martijn Dashorst < [email protected]> wrote:
> My guess is there's something changed with the websocket support? > > at > org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:297) > ~[wicket-core-7.3.0.jar:7.3.0] > at > org.apache.wicket.protocol.ws.api.AbstractWebSocketProcessor.broadcastMessage(AbstractWebSocketProcessor.java:257) > ~[wicket-native-websocket-core-7.3.0.jar:7.3.0] > at > org.apache.wicket.protocol.ws.api.AbstractWebSocketProcessor.onClose(AbstractWebSocketProcessor.java:182) > ~[wicket-native-websocket-core-7.3.0.jar:7.3.0] > at > org.apache.wicket.protocol.ws.javax.WicketEndpoint.onClose(WicketEndpoint.java:71) > ~[wicket-native-websocket-javax-7.3.0.jar:7.3.0] > > The exception happens while traversing the component tree for > serialization. Wouldn't the LinkedMap be modified when something > happens on the page during the serialization phase? > Yes, this looks like a good candidate! I'll have to take a deeper look. > > Martijn > > > On Mon, May 16, 2016 at 11:26 PM, Martijn Dashorst > <[email protected]> wrote: > > > https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/MarkupContainer.java#L28 > > > > On Mon, May 16, 2016 at 10:26 PM, Sven Meier <[email protected]> wrote: > >> Ah, yes. > >> > >> But no usage of LinkedMap from Wicket as far as my IDE tells me. > >> > >> Sven > >> > >> > >> On 16.05.2016 22:09, Martijn Dashorst wrote: > >>> > >>> Since Wicket 7.1 we introduced a dependency on commons-collections for > >>> the O(1) adding of components. > >>> > >>> Martijn > >>> > >>> On Mon, May 16, 2016 at 10:08 PM, Sven Meier <[email protected]> wrote: > >>>> > >>>> Hi, > >>>> > >>>>> org.apache.commons.collections4.map.LinkedMap.writeObject > >>>> > >>>> Wicket does not use commons-collections, so please check where this > >>>> instance > >>>> is coming from. > >>>> > >>>> It seems another thread is working on the map while Wicket tries to > >>>> serialize the page. > >>>> > >>>> Hope this helps > >>>> Sven > >>>> > >>>> > >>>> On 16.05.2016 14:21, Francesco Chicchiriccò wrote: > >>>>> > >>>>> Hi all, > >>>>> I am sometimes seeing exceptions like [1] in Syncope console logs, > since > >>>>> upgrade to Wicket 7.3.0 - I am sure enough that this was not > happening > >>>>> with > >>>>> Wicket 7.2.0. > >>>>> > >>>>> Any hint? > >>>>> TIA > >>>>> > >>>>> Regards. > >>>>> > >>>>> [1] https://paste.apache.org/Q7Jy > >>>>> > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: [email protected] > >>>> For additional commands, e-mail: [email protected] > >>>> > >>> > >>> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > > > > > > > > -- > > Become a Wicket expert, learn from the best: http://wicketinaction.com > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
