[
https://issues.apache.org/jira/browse/JENA-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796050#comment-16796050
]
Andy Seaborne commented on JENA-1683:
-------------------------------------
The image and the stacktrace look like different issues.
Do you have test cases and setup for each situation? As it stands from the
information provided, I don't see how to replicate the situations.
The "many threads" could simply be sending more requests than your
configuration can handle.
The"TDB ERROR Exception during journal replay" (which incidentally has improved
diagnostics from JENA-1676 when 3.11.0 is released - you can run the
development build now if you wish) are usually due to low level I/O problems
being signalled up.
> SPARQL Updates get stuck on high concurrency of updates
> -------------------------------------------------------
>
> Key: JENA-1683
> URL: https://issues.apache.org/jira/browse/JENA-1683
> Project: Apache Jena
> Issue Type: Bug
> Reporter: Abhranil Chatterjee
> Priority: Major
> Attachments: Screen Shot 2019-03-19 at 3.44.56 PM.png
>
>
> While doing performance test of Jena Fuseki (latest release 3.10.0, using
> jena-text for lucene index) with a mixed set of sparql-query and
> sparql-update requests, I found that SPARQL_Update becomes unserviceable.
> SPARQL_Query still functions normally. Sharing Screen shot of JMC JMX console
> where threads seem to be WAITING infinitely for acquiring writer lock.
> !Screen Shot 2019-03-19 at 3.44.56 PM.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
