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

Andy Seaborne commented on JENA-250:
------------------------------------

The example program now works, as does the same JVM version.  The test suite 
now runs significant disk tests in both mapped and direct mode regardless of 
environment.

Old data, non-transactional, was being left in the non-transactional cache and 
later flushed (in StoreConnection.release) overwriting the later 
transactionally written data. In the test case, the old data was the initial 
creation of the B+Trees (a tree of zero entries), hence on first run the empty 
root block would be written and so all other data become inaccessible.

A new, complete of Jena 2.7.1 SNAPSHOT has been done - please test.

The TDB snapshot version is 20120608.115414-19 or later.

                
> StoreConnection.release will empty repository if last action is not a query
> ---------------------------------------------------------------------------
>
>                 Key: JENA-250
>                 URL: https://issues.apache.org/jira/browse/JENA-250
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: TDB
>    Affects Versions: TDB 0.9.0
>         Environment: Windows
>            Reporter: Simon Helsen
>             Fix For: TDB 0.9.1
>
>         Attachments: TestReleaseStore.jar, src.zip
>
>
> Whenever the last activity before releasing a store (with 
> StoreConnection.release) is a write transaction, the entire database is empty 
> the next time you create a dataset. I should note that this only happens when 
> you start with a new index store. If you release the store after a write 
> transaction on a store which was created the first time around where you did 
> not end with a write transaction, the problem will not occur.
> I attached a little test case which illustrates the problem. Just provide a 
> new index location as a java argument (or hard code it)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to