[
https://jira.nuxeo.org/browse/NXP-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=84788#action_84788
]
Benoit Delbosc commented on NXP-5998:
-------------------------------------
The first visible thing in the log is:
2010-11-22 12:48:23,166 WARN [org.jboss.seam.jsf.SeamPhaseListener]
uncaught exception, passing to exception handler
org.jboss.seam.ConcurrentRequestTimeoutException: Concurrent call to
conversation
at
org.jboss.seam.core.Manager.restoreAndLockConversation(Manager.java:545)
at
org.jboss.seam.core.Manager.restoreConversation(Manager.java:507)
at
org.jboss.seam.jsf.SeamPhaseListener.afterRestoreView(SeamPhaseListener.java:390)
at
org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:228)
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.RestoreViewPhase.doPhase(RestoreViewPhase.java:103)
at
com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at
org.nuxeo.ecm.platform.ui.web.lifecycle.NuxeoLifeCycleImpl.execute(NuxeoLifeCycleImpl.java:83)
...
after the conversation is lost and the user receive an error with a trace:
@In attribute requires non-null value:
userServicesContext.navigationContext
...
This happens with a single user,
note that funkload test pass if the vcs backend is postgresql but the bug can
be reproduce with a browser (as explain in the bug description);
ConcurrentRequestTimeoutException may be due to a pending lock after an error
page (404).
like https://jira.jboss.org/browse/JBSEAM-3680 but this one should be fixed in
2.1.0-SP1
http://seamframework.org/Community/ConcurrentRequestTimeoutExceptionWithOnlyOneConversation
> Fix random errors due to previous errors managed by the error handler
> ---------------------------------------------------------------------
>
> Key: NXP-5998
> URL: https://jira.nuxeo.org/browse/NXP-5998
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Affects Versions: 5.4.1-SNAPSHOT
> Reporter: Anahide Tchertchian
> Priority: Major
> Fix For: 5.4.1
>
>
> Funkload tests show that when an error occurs (trying to access to a document
> that does not exist for instance), following valid calls will end up with an
> error.
> Symptoms show that the conversation is lost.
> Problem can also be reproduced by hand even if it's not so straight-forward
> (does not happen all the time).
> Steps to reproduce:
> - type a non-existing url => error page
> - use the 'back' button of browser and click on a document link
> => error (and url has lost document context)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
