On 17/11/2025 22:33, Азат Усманов wrote:
Hi Chris!, the Connector type was not specified on both computers. Mine just had the tomcat native dll so on my computer it is using apr.His connector was not specified, so it was using the default for tomcat in the absence of apr,i believe its NIO. I've provided him with the build instructions for apr on linux, since i do update tomcat native regularly on our production at test servers/He ended up building apr and tomcat native from latest tomcat native source 1.3.1. the issue remained the same. No SSL,NO h2.I might be able to convince him to do an update , although out test and production servers both running on 9.0.64. And those are unlikely to get updated that quickly. I probably wasn't clear in my initial message. the problematic file never fails to download, it just takes a 20 second delay(or however many ms you specify on the conectionTimeout) before downloading it .on his Mac, unless the maxKeepAliverequests is specified.I'm mostly asking because our prod and test servers have a similar setup in terms of MaxkeepAliveRequests not specified and the same connection timeout of 20s and apr,(but with https and linux) so I don't really know if we are gonna get a situation like his or like mine, when we are gonna deploy it to prod.Just trying to avoid stepping on a potential landmine
It sounds like there is an issue with detecting the end of the response. That normally means an incorrect content length is being sent. The response body is only shown once the next request times out and the connection is closed.
I'd suggest using Wireshark to look at the traffic and look very carefully at the HTTP headers that define the response body length and compare that to the actual response body length.
Comparing the working system and the non-working system should identify what is going wrong.
Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
