jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jorge Rodríguez Pedrianes (JIRA) <j...@apache.org>
Subject [jira] Commented: (JCR-449) inconsistency in internal version items during commits
Date Thu, 29 Jun 2006 17:21:32 GMT
    [ http://issues.apache.org/jira/browse/JCR-449?page=comments#action_12418500 ] 

Jorge Rodríguez Pedrianes commented on JCR-449:
-----------------------------------------------

Hello, i have been seen in your revision that in the class VersionManagerImpl you removed
in method InternalVersionItem the condition that comprubes not to instert  null values in
the attribute  "versionItems". Anywhere some times  InternalVersionHistory cache's doesn't
 have the find value and return null values and then when you try put in versionItem it throw
NullPointerException. Why did you remove this condition, it's really ok?

        Thanks a lot:
            Jorge Rodríguez Pedrianes

> inconsistency in internal version items during commits
> ------------------------------------------------------
>
>          Key: JCR-449
>          URL: http://issues.apache.org/jira/browse/JCR-449
>      Project: Jackrabbit
>         Type: Bug

>     Versions: 1.0, 1.0.1
>  Environment: r410655.
>     Reporter: Tobias Bocanegra
>     Assignee: Tobias Bocanegra

>
> since some of the versioing information is somehow cached in the 'IternalVersionItems',
it can happen that they are not updated fast enough after a commit that included versioning
operations. subsequent versioing operations could leed to errors.
> test case: create 2 threads, that concurrently do: begin -> checkout -> checkin
-> commit  on the same node.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message