UITree.visitNode generates ConcurrentModificationException

[icemaker]

Hi,

I have a problem with UITree.visitNode generating a ConcurrentModificationException.
The log has been sent to me by a client and unfortunately I cannot reproduce it on my environment and cannot test it on the client environment at the moment (but I can send him some code modifications).

What could lead to this kind of exception ?

Is there a way to know at least which page and which component has generated this error ?
The current exception stacktrace does not give me enough informations. All I get is :

Code: Select all

Caused by: java.util.ConcurrentModificationException
	at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:819) [rt.jar:1.7.0_25]
	at java.util.ArrayList$Itr.next(ArrayList.java:791) [rt.jar:1.7.0_25]
	at org.primefaces.component.api.UITree.visitNode(UITree.java:633) [primefaces-4.0.jar:4.0]
	at org.primefaces.component.api.UITree.visitNodes(UITree.java:612) [primefaces-4.0.jar:4.0]
	at org.primefaces.component.api.UITree.visitTree(UITree.java:561) [primefaces-4.0.jar:4.0]
	at javax.faces.component.UIComponent.visitTree(UIComponent.java:1700) [jsf-api-2.2.0-m12.jar:2.2]
	at javax.faces.component.UIComponent.visitTree(UIComponent.java:1700) [jsf-api-2.2.0-m12.jar:2.2]
	at javax.faces.component.UIComponent.visitTree(UIComponent.java:1700) [jsf-api-2.2.0-m12.jar:2.2]
	at javax.faces.component.UIComponent.visitTree(UIComponent.java:1700) [jsf-api-2.2.0-m12.jar:2.2]
	at javax.faces.component.UIComponent.visitTree(UIComponent.java:1700) [jsf-api-2.2.0-m12.jar:2.2]
	at javax.faces.component.UIComponent.visitTree(UIComponent.java:1700) [jsf-api-2.2.0-m12.jar:2.2]
	at javax.faces.component.UIComponent.visitTree(UIComponent.java:1700) [jsf-api-2.2.0-m12.jar:2.2]
	at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreView(FaceletPartialStateManagementStrategy.java:367) [jsf-impl-2.2.0-m12.jar:2.2.0-m12-SNAPSHOT]
	at com.sun.faces.application.StateManagerImpl.restoreView(StateManagerImpl.java:138) [jsf-impl-2.2.0-m12.jar:2.2.0-m12-SNAPSHOT]
	at com.sun.faces.application.view.ViewHandlingStrategy.restoreView(ViewHandlingStrategy.java:123) [jsf-impl-2.2.0-m12.jar:2.2.0-m12-SNAPSHOT]
	at com.sun.faces.application.view.FaceletViewHandlingStrategy.restoreView(FaceletViewHandlingStrategy.java:572) [jsf-impl-2.2.0-m12.jar:2.2.0-m12-SNAPSHOT]
	at com.sun.faces.application.view.MultiViewHandler.restoreView(MultiViewHandler.java:148) [jsf-impl-2.2.0-m12.jar:2.2.0-m12-SNAPSHOT]
	at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:353) [jsf-api-2.2.0-m12.jar:2.2]
	at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:353) [jsf-api-2.2.0-m12.jar:2.2]
	at org.omnifaces.viewhandler.RestorableViewHandler.restoreView(RestorableViewHandler.java:66) [omnifaces-1.5.jar:1.5]
	at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:197) [jsf-impl-2.2.0-m12.jar:2.2.0-m12-SNAPSHOT]

Primefaces version: 4.0 / Mojarra 2.2.0-m12 / Jboss 7.1.1 Final

Thanks a lot for any help

[jeffsui]

Did you ever find out what this was?

[chrishj]

One cause could be if the client is using for-each

Code: Select all

 for(Class c: list){.. 

and is modifying the list that is being looped over.

[kukeltje]

Might also be the combination of JSF 2.2 and PF 4.0. Might very wel be that PF 4 is not forward compatible!!!