Memory Leak In WebLogic Server 10.3.4+ when Work Manager Capacity Constraint is Violated (Doc ID 1412803.1)

Last updated on JULY 29, 2013

Applies to:

Oracle Weblogic Server - Version 10.3.4 and later
Information in this document applies to any platform.


Customers on WLS 10.3.4+ reported that under heavy load with a Work Manager capacity constraint in place, a memory leak occurred. After WLS responded to the client with a HTTP 503 status code, servlet-relevant objects such as weblogic.servlet.internal.ServletRequestImpl, weblogic.servlet.internal.ServletResponseImpl, weblogic.servlet.internal.ServletInputStreamImpl, weblogic.servlet.internal.ServletOutputStreamImpl, weblogic.servlet.internal.RequestHeaders, weblogic.servlet.internal.ResponseHeaders, etc. remain forever on the JVM heap.


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