On 06/07/2021 12:40, John Walker wrote:
Hi James
-----Original Message-----
From: James Anderson <[email protected]>
Sent: Tuesday, July 6, 2021 1:00 PM
To: [email protected]
Subject: Re: Jena hangs while reading HTTP stream
a stack trace could be very helpful.
There is no stack trace captured at the time of the incident and we are unable
to reproduce.
Given this sanitized extract from the application logs directly prior to it
hanging:
c.semaku.es.core.service.UpdateService : Executing : query.rq
com.semaku.es.core.util.Utils : Send request to:
https://example.com/foo/bar/sparql?query=query.rq
com.semaku.es.core.util.Utils : Received response in 1397ms for
https://example.com/foo/bar/sparql?query=query.rq
c.semaku.es.core.service.UpdateService : Loading NTriples to Jena model
The "received response in ..." line is logged after the HttpOp.execHttpGet()
method has been called (which returns the TypedOutputStream).
I am not familiar enough with how these streams work in Jena and Java.
It is unclear if this indicates Dydra has started to return results after
1397ms, or if the complete response had already been received by the client.
Started.
execHttpGet opens the stream; it does not read the body (it reads the
headers).
The body is the TypedInputStream - there is a normal java InputStream.
Andy
