On 23/08/15 16:23, Adrian Gschwend wrote:
On 09.07.15 11:03, Andy Seaborne wrote:
Hi Andy,
Could this be JENA-918?
Andy
https://issues.apache.org/jira/browse/JENA-918
oh I didn't see there is a tdb-config as well. I just changed it there
to 5000ms and I still get the error.
Can I somehow see what is set at runtime?
Not really though it would a good idea to annotate the log at the start
of the query with the timeout set.
that would definitely help for debugging. I can't see that in 2.3.0
release, right?
Right.
The snapshot development version is 2.3.0-SNAPHOT
If you could try that, it would be very helpful.
The "3 second" timeout is the marker for JENA-918 but if every setting
is different to 3000 then I can't explain the situation. If you could
send me all the configuration files you use, I will try to recreate this
when I'm back online (I'm "away" this week)
I still have that on 2.3.0. Do you want just the configuration or also
the data which triggers it? It's gonna be open data so it's not a problem.
Would it be enough to tar the "run" directory or is this not portable?
Adrian - That would be perfect. I don't think I need the data, just the
setup. It would also be useful to know exactly how you are making the
call. A per-query timeout is possible with the header "Timeout:" or
parameter &timeout=.
Andy
regards
Adrian
