Secondary OAM Cluster Member Fails to Start With BEA-290065, java.net.ProtocolException: Exceeded Stated Content-Length (Doc ID 2071029.1)

Last updated on JUNE 06, 2017

Applies to:

Oracle Access Manager - Version 11.1.2.3.0 and later
Information in this document applies to any platform.

Symptoms

When attempting to start an OAM Managed Server that is a member of a cluster, the following error appears in the system output for the OAM Managed Server

<Oct 15, 2015 7:51:39 PM UTC> <Warning> <DeploymentService> <BEA-290065> <Deployment service servlet encountered an Exception while handling the deployment datatransfer message for request id "1,444,938,657,509" from server "oam_server2". Exception is: "java.net.ProtocolException: Exceeded stated content-length of: '-1496535563' bytes
       at weblogic.servlet.internal.ServletOutputStreamImpl.checkCL(ServletOutputStreamImpl.java:200)
       at weblogic.servlet.internal.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:146)
       at weblogic.deploy.service.datatransferhandlers.MultipartResponse.writeDataStream(MultipartResponse.java:91)
       at weblogic.deploy.service.datatransferhandlers.MultipartResponse.write(MultipartResponse.java:78)
       at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.handleDataTransferRequest(DeploymentServiceServlet.java:901)
(...)


And the server fails to start.

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