You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Dominique Pfister (JIRA)" <ji...@apache.org> on 2007/03/09 08:57:24 UTC

[jira] Created: (JCR-780) Simultaneous updates by multiple sessions might not appear in the journal

Simultaneous updates by multiple sessions might not appear in the journal
-------------------------------------------------------------------------

                 Key: JCR-780
                 URL: https://issues.apache.org/jira/browse/JCR-780
             Project: Jackrabbit
          Issue Type: Bug
          Components: core
    Affects Versions: 1.2.2
            Reporter: Dominique Pfister
         Assigned To: Dominique Pfister


In a clustering environment, simultaneous updates by multiple sessions in the same cluster node might not appear in the journal, because only record at a time can be handled by the cluster's workspace-specific callback method. When such a situtation arises, the following warnings can be found in the log:

*WARN * ClusterNode: No record created.
*WARN * ClusterNode: No record prepared.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (JCR-780) Simultaneous updates by multiple sessions might not appear in the journal

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-780:
------------------------------

        Fix Version/s: 1.3
    Affects Version/s: 1.2.1
                       1.2.3

> Simultaneous updates by multiple sessions might not appear in the journal
> -------------------------------------------------------------------------
>
>                 Key: JCR-780
>                 URL: https://issues.apache.org/jira/browse/JCR-780
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.2.1, 1.2.2, 1.2.3
>            Reporter: Dominique Pfister
>         Assigned To: Dominique Pfister
>             Fix For: 1.3
>
>
> In a clustering environment, simultaneous updates by multiple sessions in the same cluster node might not appear in the journal, because only record at a time can be handled by the cluster's workspace-specific callback method. When such a situtation arises, the following warnings can be found in the log:
> *WARN * ClusterNode: No record created.
> *WARN * ClusterNode: No record prepared.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (JCR-780) Simultaneous updates by multiple sessions might not appear in the journal

Posted by "Dominique Pfister (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominique Pfister resolved JCR-780.
-----------------------------------

    Resolution: Fixed

Fixed by passing along the current SharedItemStateManager's Update object along with the UpdateEventChannel notifications. This allows the Cluster's workspace-specific callback methods to remember the journal record being appended in the Update object itself.

Fixed in revision 516324.

> Simultaneous updates by multiple sessions might not appear in the journal
> -------------------------------------------------------------------------
>
>                 Key: JCR-780
>                 URL: https://issues.apache.org/jira/browse/JCR-780
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.2.2
>            Reporter: Dominique Pfister
>         Assigned To: Dominique Pfister
>
> In a clustering environment, simultaneous updates by multiple sessions in the same cluster node might not appear in the journal, because only record at a time can be handled by the cluster's workspace-specific callback method. When such a situtation arises, the following warnings can be found in the log:
> *WARN * ClusterNode: No record created.
> *WARN * ClusterNode: No record prepared.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.