[
http://jira.nuxeo.org/browse/NXP-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62072#action_62072
]
Florent Guillaume commented on NXP-4251:
----------------------------------------
And:
http://hg.nuxeo.org/nuxeo/nuxeo-core/rev/4e89e92dada9
http://hg.nuxeo.org/nuxeo/nuxeo-core/rev/c17b1ba1a1cb
> UnrestrictedSessionRunner use in non-pooled/transactional setting can fail
> --------------------------------------------------------------------------
>
> Key: NXP-4251
> URL: http://jira.nuxeo.org/browse/NXP-4251
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Affects Versions: 5.2 GA
> Reporter: Florent Guillaume
> Assignee: Florent Guillaume
> Fix For: 5.3 GA
>
>
> When using UnrestrictedSessionRunner (or any secondary session) that does
> some work, if the main session expects to see the results immediately then at
> least one of this has to be true:
> 1. we're in a JCA pooled setting, in which cas all sessions in a thread
> actually share the same underlying state,
> 2. the secondary session has to send its invalidations through save(), and
> the main session has to process invalidations through save().
> The case 2. happens when not using JCA or a transaction manager, for instance
> with Jetty/Tomcat packaging.
> This is visible for instance when unlocking a document we don't own, or using
> workflows.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://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
