JBoss EAP 6.1 to 6.3 Migration Issue

Latest response

We have a working web application using JBoss 6.1 and Primefaces 4. When we deploy our code on JBoss 6.3 we are getting
actions that fire "twice".
To hopefully better understand how/why an action callback would be called twice, I turned on massive debug and, I rebuilt exactly the SAME code using the 6.1 pom.xmls and ran EXACTLY the same test under both JBoss 6.1 and JBoss 6.3. The code ran fine under 6.1, and tanked in 6.3, as expected (see attached log files).
I then took the “full” log files and ripped out all but the faces stuff, which you will find in the “short” log files. I then made sure that the logged actions “lined up”. Everything is in sync up to line 449, which is where 6.3 calls the Edit button’s action function a second time, causing all Hell to break loose.

The Edit button can be found by looking for: /Jaguar/ToolCategoryList.xhtml @43,108
in the log files.

Of particular interest to me, at the moment, are lines 245-309 which seem to be setting up the Faces and Primefaces parsers. Note that in 6.1 http-/ is tied to ln=primefaces&v=4.0 (line 264), but in 6.3 http-/ is tied to ln=primefaces-aristo (line 248). If we look at lines 348, it appears that the wrong thread is doing the final round of processing on the Primefaces components in 6.3 and that is resulting in two actions being associated with the Edit button.

6.1 – Line 348
FINE [javax.enterprise.resource.webcontainer.jsf.facelets.tag.component] (http-/ /Jaguar/ToolCategoryList.xhtml @43,108
Component[90427187_563ce76] Found, marking children for cleanup

6.3 – Line 348
FINE [javax.enterprise.resource.webcontainer.jsf.facelets.tag.component] (http-/ /Jaguar/ToolCategoryList.xhtml @43,108
Component[90427187_563ce76] Created: org.primefaces.component.commandbutton.CommandButton
FINE [javax.enterprise.resource.webcontainer.jsf.application] (http-/ Created component with component type of 'org.primefaces.component.CommandButton'

Any help as to why JBoss EAP 6.3 and Primefaces 4 are not behaving correctly would be greatly appreciated.




This sort of question (where we have logs and possibly a reproducer) would be best dealt with on a Support Case [1]. Please open a support case and one of our Web Framework engineers can take a look a closer look at this issue for you.


Roger that...will do.