On 25/03/2020 14:36, Jean-Marc Vanel wrote:
Le mer. 25 mars 2020 à 13:07, Andy Seaborne a écrit :
What's the full stack trace?
(What's the blocking thread?)
See below.
I was looking for the other thread that is blocking this one at
being(write). Same JVM.
There is no across
Le mer. 25 mars 2020 à 13:07, Andy Seaborne a écrit :
> What's the full stack trace?
> (What's the blocking thread?)
>
See below.
> Yes, another unended W transaction in the same process might be the cause.
>
I thought rather, another unended W transaction in *another* process, since
the
What's the full stack trace?
(What's the blocking thread?)
Yes, another unended W transaction in the same process might be the cause.
Andy
On 25/03/2020 11:08, Jean-Marc Vanel wrote:
I investigated on that.
Now my test suite passes without Jena TDB trouble. I just added this in
Scala SBT
I investigated on that.
Now my test suite passes without Jena TDB trouble. I just added this in
Scala SBT :
parallelExecution in Test := false
I didn't know that parallel execution was the default.
So apparently this was an issue with 2 processes accessing the same TDB .
Normally this is detected
On 24/03/2020 15:11, Zhenya Antić wrote:
Hi Andy,
Did you load the data before attaching the text index?
How do I do it (or not do it, wasn't sure from your post)?
Set up the Fueski system, with the text index as the Fuskei service dataset:
fuseki:name "biology" ;
fuseki:dataset
