On Thu, 2017-10-26 at 09:42 -0400, Marc Boorshtein wrote: > Thanks Oleg. Could the root cause of this exception cause > performance > issues and more specifically connection retention? The symptoms we > were > seeing was a lock while trying to get a connection from the pool. We > got > around the issue by increasing the size of the pool but we're still > seeing > significant performance issues on this network and I suspect its > because > the response is hanging waiting for the final chunk. >
No, those issues should be completely unrelated in my opinion. Cheers Oleg > On Thu, Oct 26, 2017 at 7:31 AM, Oleg Kalnichevski <[email protected]> > wrote: > > > On Wed, 2017-10-25 at 11:12 -0400, Marc Boorshtein wrote: > > > All, > > > > > > I'm trying to connect to a resource over https and am getting the > > > following > > > errors on occasion: > > > > > > org.apache.http.ConnectionClosedException: Premature end of chunk > > > coded > > > message body: closing chunk expected > > > at > > > org.apache.http.impl.io.ChunkedInputStream.getChunkSize(ChunkedIn > > > putS > > > tream.java:268) > > > ~[httpcore-4.4.4.jar:4.4.4] > > > at > > > org.apache.http.impl.io.ChunkedInputStream.nextChunk(ChunkedInput > > > Stre > > > am.java:227) > > > ~[httpcore-4.4.4.jar:4.4.4] > > > at > > > org.apache.http.impl.io.ChunkedInputStream.read(ChunkedInputStrea > > > m.ja > > > va:186) > > > ~[httpcore-4.4.4.jar:4.4.4] > > > at > > > org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStre > > > am.j > > > ava:137) > > > ~[httpclient-4.5.2.jar:4.5.2] > > > > > > There isn't much on the web on this one. Whats interesting is > > > that > > > when > > > this code runs in the same subnet as the target, no issues but > > > when > > > it > > > crosses some complex networking I will get this error on > > > occasion. My > > > network team is saying there are no "issues" with the > > > connections. Are > > > there some tuning parameters I can adjust for this? > > > > > > > You should try to capture a wire log of the message exchange that > > exhibits the problem and see whether or not the closing chunk is > > indeed > > missing. > > > > Besides, it should be pretty safe to just > > ignore ConnectionClosedException if you do not care about 100% HTTP > > protocol compliance. HttpClient intentionally uses a specific > > exception > > type so it could be caught and ignored if desired. > > > > Hope this helps > > > > Oleg > > > > ----------------------------------------------------------------- > > ---- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > g > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
