Github user ajs6f commented on the pull request:
https://github.com/apache/jena/commit/8601cd3028c0e57dbc805efc5d54d7b9ee272c3f#commitcomment-20399785
In
jena-arq/src/test/java/org/apache/jena/sparql/core/pergraph/MultithreadingTest.java:
In
jena-arq/src/test/java/org/apache/jena/sparql/core/pergraph/MultithreadingTest.java
on line 45:
Okay, looking carefully at `ThreadAction` I don't see how it explicitly
synchronizes amongst overlapping `Runnable`s. So the way I can see to use it
for this test is a 3-phase `ThreadAction` with these three phases:
1. Open a tx on graph1
2. Launch a separate thread that opens a tx on graph2, writes into it, then
commits
3. Close the tx on graph1, open a tx on graph2 (or just use implicit-tx
calls) to check to see that the probe triple appeared in graph2
Is that kind of what you were thinking? Use ordering instead of
synchronization?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
