[jira] [Commented] (MARMOTTA-236) triple-leak with concurrent connections in facading

["Sebastian Schaffert (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MARMOTTA-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13763009#comment-13763009 ] 

Sebastian Schaffert commented on MARMOTTA-236:
----------------------------------------------

The problem cannot really be solved by us because it depends on how the database system handles concurrent transactions- The temporary solution is fail-fast: we now throw a ConcurrentModificationException in case this situation occors on H2 database. On PostgreSQL and MySQL the problem should not occur because they handle transactions differently.
                
> triple-leak with concurrent connections in facading
> ---------------------------------------------------
>
>                 Key: MARMOTTA-236
>                 URL: https://issues.apache.org/jira/browse/MARMOTTA-236
>             Project: Marmotta
>          Issue Type: Bug
>          Components: Sesame Tools
>    Affects Versions: 3.0-incubating
>            Reporter: Jakob Frank
>            Assignee: Sebastian Schaffert
>             Fix For: 3.1-incubating
>
>   Original Estimate: 8h
>          Time Spent: 1.5h
>  Remaining Estimate: 6.5h
>
> When using facading on the *same* subject in different connections, the transaction-isolation seems to be not completely working.
> When creating a typed facade (Facade with RDFType-Annotation):
> - in the first connection (c1), the type is correctly added
> - before commit in c1, creating a facade on a parallel connection c2 - the type is NOT added.
> - after commit in c1: the type is added as should be.
> see UnitTest: ConcurrentFacadingTest#testParallelFacadingType

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira