> On 2021-07-06, at 12:46:47, John Walker <[email protected]> wrote: > > Hi Andy > >> -----Original Message----- >> From: Andy Seaborne <[email protected]> >> Sent: Tuesday, July 6, 2021 12:04 PM >> To: [email protected] >> Subject: Re: Jena hangs while reading HTTP stream >> ... >>>> John - what's the requestURL? The logs say the request is 3072 bytes >>>> (including headers) which is possible but unusually large. >>> >>> As it is a GET request, the query text is passed as (url encoded) query >>> string >> parameter on the url. >>> I cannot share the query text as it is for a customer project, but have made >> similar GET request from curl and it came out at 3100 bytes. >> >> But what is it doing? I guess it is a CONSTRUCT query. > > Yes, it is a CONSTRUCT. > >> >> At what point did it show as 3100 bytes? From "curl -v" or from logs nearer. >> the server? (Intermediates may be adding "Transfer-*" headers) > > To get that I just copied the request headers from curl -v output into a text > file and check the size. > > The original 3072 bytes comes from what James observed for the request length > on the Dydra host.
the two length values are "$request_length/$body_bytes_sent" the first is described to be the length of the entire request. (http://nginx.org/en/docs/http/ngx_http_log_module.html) the requests include the sparql query text as a url parameter. one of the request lines was itself 2789 bytes. > >> >> Andy >> >>>> >>>> It is the unpredictability that is odd. >>>> >>>> Could you please breakpoint the process and see what code it is in? >>> >>> Will check on that. a stack trace could be very helpful. >>> >>>> >>>> Andy >>> >>> John
