You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2016/05/21 11:58:12 UTC

[jira] [Commented] (WICKET-6167) Random ConcurrentModificationException since upgrade to 7.3.0

    [ https://issues.apache.org/jira/browse/WICKET-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15294971#comment-15294971 ] 

Martin Grigorov commented on WICKET-6167:
-----------------------------------------

This ticket is related to WICKET-6107.
But all it does is to broadcast a Wicket event whenever a WebSocket connection is closed.
After the broadcast Wicket detaches the request cycle and here it seems you have a component with custom Java serialization (custom writeObject()?!) that modifies it children during the serialization.

> Random ConcurrentModificationException since upgrade to 7.3.0
> -------------------------------------------------------------
>
>                 Key: WICKET-6167
>                 URL: https://issues.apache.org/jira/browse/WICKET-6167
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-native-websocket
>    Affects Versions: 7.3.0
>         Environment: Apache Syncope 2.0.0-SNAPSHOT
>            Reporter: Francesco Chicchiriccò
>            Assignee: Martin Grigorov
>
> As [reported in mailing list|https://lists.apache.org/thread.html/Zqmev2wqdxnjxya] we randomly see exceptions (see [an example|https://paste.apache.org/Q7Jy]) in Apache Syncope admin console logs after upgrading from Wicket 7.2.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)