GZIP IOException When Enable Debug Option weblogic.debug.DebugHttp

(Doc ID 2332398.1)

Last updated on DECEMBER 03, 2017

Applies to:

Oracle WebLogic Server - Version 12.2.1.0.0 and later
Information in this document applies to any platform.

Symptoms

Below error happens when setting -Dweblogic.debug.DebugHttp=true and the gzip compression is enabled. Refer to Configure GZIP compression for Web applications

The server log shows IOException as below sample.

<2017/11/24, 2:00:49,299 JST> <Debug> <Http> <HOSTNAME> <AdminServer>

<[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <d5d05292-76d2-4d18-9f92-2ff7438d0655-00000060> <1511499649299><[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] ><BEA-000000> <IOException occurs while finishing the output

java.io.IOException: write beyond end of stream

at java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:201)

at java.util.zip.GZIPOutputStream.write(GZIPOutputStream.java:145)

at weblogic.servlet.utils.ChunkedGzipOutputStream.write(ChunkedGzipOutputStream.java:40)

at weblogic.servlet.utils.StatOutputStream.write(StatOutputStream.java:38)

at weblogic.servlet.internal.ChunkOutput.writeChunkNoTransfer(ChunkOutput.java:649)

at weblogic.servlet.internal.ChunkOutput.writeChunks(ChunkOutput.java:588)

at weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:471)

at weblogic.servlet.internal.CharsetChunkOutput.flush(CharsetChunkOutput.java:318)

at weblogic.servlet.internal.ChunkOutputWrapper.flush(ChunkOutputWrapper.java:207)

at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:153)

at weblogic.servlet.internal.ServletOutputStreamImpl.commit(ServletOutputStreamImpl.java:561)

at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1709)

at weblogic.servlet.internal.ServletRequestImpl.runInternal(ServletRequestImpl.java:1701)

at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1651)

at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:270)

at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)

at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)

at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)

at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)

at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:640)

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:406)

at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)

>

Meanwhile you can observe "<net::ERR_CONTENT_LENGTH_MISMATCH>" with Google Chrome Browser if you open the developer tool inside Chrome.

 

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms