]
Jay Balunas commented on RF-8135:
---------------------------------
The basic workaround for this is to increase the timeout for the transactions. If you are
uploading a file that takes 10 minutes your transaction timeout needs to be more than
that.
There may be some way to solve this between Seam and RichFaces and so we will not close
the issue. However we will not be able to get it into 3.3.3.
FileUpload: transaction timeout happens for long-running uploads
----------------------------------------------------------------
Key: RF-8135
URL:
https://jira.jboss.org/jira/browse/RF-8135
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-input, performance, regression
Affects Versions: 3.3.2.SR1
Reporter: Nick Belaevski
Assignee: Andrey Markhel
Priority: Critical
Fix For: Future
Details are at forum thread, basically this happens:
Nov-11 18:12:50,808 DEBUG [ajp-jbossdev5.namerica.idexxi.com%2F172.31.29.160-8309-9]
[org.ajax4jsf.event.AjaxPhaseListener] Process after phase UPDATE_MODEL_VALUES 4
Nov-11 18:12:50,808 DEBUG [ajp-jbossdev5.namerica.idexxi.com%2F172.31.29.160-8309-9]
[javax.enterprise.resource.webcontainer.jsf.timing] [TIMING] - [47ms] : Execution time for
phase (including any PhaseListeners) -> UPDATE_MODEL_VALUES 4
Nov-11 18:12:50,808 DEBUG [ajp-jbossdev5.namerica.idexxi.com%2F172.31.29.160-8309-9]
[org.ajax4jsf.event.AjaxPhaseListener] Process before phase INVOKE_APPLICATION 5
Nov-11 18:12:50,808 DEBUG [ajp-jbossdev5.namerica.idexxi.com%2F172.31.29.160-8309-9]
[javax.enterprise.resource.webcontainer.jsf.lifecycle] Entering InvokeApplicationsPhase
Nov-11 18:12:50,808 DEBUG [ajp-jbossdev5.namerica.idexxi.com%2F172.31.29.160-8309-9]
[javax.enterprise.resource.webcontainer.jsf.lifecycle] Exiting InvokeApplicationsPhase
Nov-11 18:12:50,808 DEBUG [ajp-jbossdev5.namerica.idexxi.com%2F172.31.29.160-8309-9]
[org.ajax4jsf.event.AjaxPhaseListener] Process after phase INVOKE_APPLICATION 5
Nov-11 18:12:50,810 WARN [ajp-jbossdev5.namerica.idexxi.com%2F172.31.29.160-8309-9]
[com.arjuna.ats.arjuna.logging.arjLoggerI18N]
[com.arjuna.ats.arjuna.coordinator.BasicAction_40] - Abort called on already aborted
atomic action -53e0e260:84df:4afb2c53:26cc
Nov-11 18:12:50,810 WARN [ajp-jbossdev5.namerica.idexxi.com%2F172.31.29.160-8309-9]
[org.jboss.seam.jsf.SeamPhaseListener] uncaught exception, passing to exception handler
java.lang.IllegalStateException: Could not commit transaction
at org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:626)
at org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:605)
at
org.jboss.seam.jsf.SeamPhaseListener.handleTransactionsAfterPhase(SeamPhaseListener.java:343)
at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:243)
at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:194)
at com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:175)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:114)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: