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

Andy Seaborne commented on JENA-244:
------------------------------------

Stephen - I recently (last weekend) came across this situation in the Jena Test 
Suite itself.  I believe I have a fix and would be grateful if you could test 
it.

There is a separate branch [1] of jena-core where I have been stripping out 
several unused features.  While these features don't directly affect the 
reasoner system, they do seem to have caused a timing change and a concurrency 
test started failing with a deadlock very like the one you have reported here.

There is a fix in the branch.  For I now, I have retrofitted the fit to 
jena-core trunk.

Would you be able to try the development build? [2]  Either copy the jar there, 
or the latest apache-jena build, or a dependency on jena-core-2.7.5-SNAPSHOT.

I ran your test example but wasn't getting failures with jena-core trunk before 
retrofitting the possible fix.  However, precise timing does affect the 
situation so different machines may act differently.

I plan to propose to the team that this branch becomes jena-core trunk but 
integration is not a simple replacement because it changes some internal APIs 
(in fairly trivial ways) so ARQ, TDB and SDB need updates at the same time.

[1] https://svn.apache.org/repos/asf/jena/branches/jena-core-simplified/

[2] 
https://repository.apache.org/content/groups/snapshots/org/apache/jena/jena-core/2.7.5-SNAPSHOT/
at least increment 46

                
> Deadlock during SPARQL execution on an inference model
> ------------------------------------------------------
>
>                 Key: JENA-244
>                 URL: https://issues.apache.org/jira/browse/JENA-244
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: Jena
>            Reporter: Stephen Owens
>         Attachments: JenaDeadLockTest.java, JenaDeadLockTest.java
>
>


--
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

Reply via email to