You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (Commented) (JIRA)" <ji...@apache.org> on 2012/01/29 21:49:10 UTC
[jira] [Commented] (JENA-202) Creating datasets, then using them in
a transaction, repeatedly, can cause OOM.
[ https://issues.apache.org/jira/browse/JENA-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195840#comment-13195840 ]
Andy Seaborne commented on JENA-202:
------------------------------------
A specific cause for this report has not been found, nor has it be reproduced outside the original report test framework. Code analysis shows a possible cause: the TDBMaker cache isn't thread safe. Used with the usual locking policy, this was acceptable so it is possible that the change to transactions also is a change in usage patterns.
It was also reported that using the alternative way to make datasets, directly using the transactional dataset factory (StoreConnection) works. There is not reason not to use the direct code so this is now the normal API code to make datasets in TDBFactory. StoreConnection has a cache and the datasets behave like old style datasets until used by for a transaction when they switch to being transactional only.
(There is no equivalent of autocommit because of the severe performance problems and the fact that SPARQL query and update are not safe if done one-trrssnaction per interaction with the storage - many interactions are involved.)
Status: awaiting feedback as to whether the changes remove the problem.
> Creating datasets, then using them in a transaction, repeatedly, can cause OOM.
> -------------------------------------------------------------------------------
>
> Key: JENA-202
> URL: https://issues.apache.org/jira/browse/JENA-202
> Project: Jena
> Issue Type: Bug
> Components: TDB
> Affects Versions: TDB 0.9.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Blocker
> Fix For: TDB 0.9.0
>
>
--
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