java.net.ProtocolException: Didn't meet stated Content-Length - Weblogic

This is a discussion on java.net.ProtocolException: Didn't meet stated Content-Length - Weblogic ; Hi, I am getting this error when starting the admin console. Any ideas what is causing this?? I had just configured my jdbc connection pool and datasource. I did not get any problem and I verified the connection using utils.dbping ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: java.net.ProtocolException: Didn't meet stated Content-Length

  1. java.net.ProtocolException: Didn't meet stated Content-Length


    Hi,

    I am getting this error when starting the admin console. Any ideas what is causing
    this??

    I had just configured my jdbc connection pool and datasource. I did not get any
    problem and I verified the connection using utils.dbping utility. It gave me success.

    Please advise.

    Thanks

    Peter Vennel.


    *** Start of Logs *******
    --------------------------

    E:\BEA\user_projects\ImagingBuildDomain>"E:\BEA\jdk131_10\bin\java" -hotspot -Xms32m
    -Xmx200m -Dweblogic.security.SSL.trustedCAKeyStore="E:\BEA\weblogic700\server\lib\cacerts"
    -Dweblogic.Name=ImagingBuildServer -Dbea.home="E:\BEA" -Dweblogic.management.username=admin
    -Dweblogic.management.password=abcd -Dweblogic
    ..ProductionModeEnabled= -Djava.security.policy="E:\BEA\weblogic700\server\lib\weblogic.policy"
    weblogic.Server
    Starting WebLogic Server...
    <140005> E:\BEA\user_projects\ImagingBuildDomain\.\config.x ml>
    <090082> using realm myrealm.>
    <000327> Admin Server "ImagingBuildServer" for domain "ImagingBuildDomain">
    <141052> started for development server.>
    <141030> of Managed Server... This feature is on by default, you may turn this off by passing
    -Dweblogic.management.discover=false>
    <000331> Admin Server "ImagingBuildServer" for domain "ImagingBuildDomain" running in Development
    Mode>
    <000354> listening on port 7002>
    <000354> listening on port 7001>
    <000365> to RUNNING>
    <000360> in RUNNING mode>
    <101083> Didn't meet stated Content-Length, wrote: '12216' bytes instead of stated: '34079'
    bytes.
    at weblogic.servlet.internal.ServletOutputStreamImpl. ensureContentLength(ServletOutputStreamImpl.java:4 69)
    at weblogic.servlet.internal.ServletResponseImpl.ensu reContentLength(ServletResponseImpl.java:1186)
    at weblogic.servlet.internal.ServletResponseImpl.send (ServletResponseImpl.java:1198)
    at weblogic.servlet.internal.ServletRequestImpl.execu te(ServletRequestImpl.java:2560)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThrea d.java:251)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.ja va:219)
    >

    <101104> context "ServletContext(id=6480502,name=console,context-path=/console)" failed,
    java.net.ProtocolException: Didn't meet stated Content-Length, wrote: '12216'
    bytes instead of stated: '34079' bytes.
    java.net.ProtocolException: Didn't meet stated Content-Length, wrote: '12216'
    bytes instead of stated: '34079' bytes.
    at weblogic.servlet.internal.ServletOutputStreamImpl. ensureContentLength
    (ServletOutputStreamImpl.java:469)
    at weblogic.servlet.internal.ServletResponseImpl.ensu reContentLength(ServletResponseImpl.java:1186)
    at weblogic.servlet.internal.ServletResponseImpl.send (ServletResponseImpl.java:1198)
    at weblogic.servlet.internal.ServletRequestImpl.execu te(ServletRequestImpl.java:2560)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThrea d.java:251)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.ja va:219)

  2. Re: java.net.ProtocolException: Didn't meet stated Content-Length


    I reinstalled WLS 7.0. I still get the same error.

    Everything is fine when I launch Weblogic server. The problem in when I log in
    to the Admin Console (browser), I noticed that while refreshing the left frame
    (containing the trees), It gives me this errors mentioned below...

    Please help.

    p.s. I am not getting this error on my build PC. So I gue, this must be something
    to do with the Test PC, when I am getting this error.

    "Peter Vennel" wrote:
    >
    >Hi,
    >
    >I am getting this error when starting the admin console. Any ideas what
    >is causing
    >this??
    >
    >I had just configured my jdbc connection pool and datasource. I did not
    >get any
    >problem and I verified the connection using utils.dbping utility. It
    >gave me success.
    >
    >Please advise.
    >
    >Thanks
    >
    >Peter Vennel.
    >
    >
    >*** Start of Logs *******
    >--------------------------
    >
    >E:\BEA\user_projects\ImagingBuildDomain>"E:\BEA\jdk131_10\bin\java" -hotspot
    >-Xms32m
    >-Xmx200m -Dweblogic.security.SSL.trustedCAKeyStore="E:\BEA\weblogic700\server\lib\cacerts"
    >-Dweblogic.Name=ImagingBuildServer -Dbea.home="E:\BEA" -Dweblogic.management.username=admin
    >-Dweblogic.management.password=abcd -Dweblogic
    >.ProductionModeEnabled= -Djava.security.policy="E:\BEA\weblogic700\server\lib\weblogic.policy"
    >weblogic.Server
    >Starting WebLogic Server...
    > <140005> >configuration
    >E:\BEA\user_projects\ImagingBuildDomain\.\config.x ml>
    > <090082> >initializing
    >using realm myrealm.>
    > <000327> >WebLogic
    >Admin Server "ImagingBuildServer" for domain "ImagingBuildDomain">
    > <141052> >Poller
    >started for development server.>
    > <141030> >discovery
    >of Managed Server... This feature is on by default, you may turn this
    >off by passing
    >-Dweblogic.management.discover=false>
    > <000331> >WebLogic
    >Admin Server "ImagingBuildServer" for domain "ImagingBuildDomain" running
    >in Development
    >Mode>
    > <000354> >"SSLListenThread.Default"
    >listening on port 7002>
    > <000354> >"ListenThread.Default"
    >listening on port 7001>
    > <000365> >statechanged
    >to RUNNING>
    > <000360> >started
    >in RUNNING mode>
    > <101083> >java.net.ProtocolException:
    >Didn't meet stated Content-Length, wrote: '12216' bytes instead of stated:
    >'34079'
    >bytes.
    > at weblogic.servlet.internal.ServletOutputStreamImpl. ensureContentLength(ServletOutputStreamImpl.java:4 69)
    > at weblogic.servlet.internal.ServletResponseImpl.ensu reContentLength(ServletResponseImpl.java:1186)
    > at weblogic.servlet.internal.ServletResponseImpl.send (ServletResponseImpl.java:1198)
    > at weblogic.servlet.internal.ServletRequestImpl.execu te(ServletRequestImpl.java:2560)
    > at weblogic.kernel.ExecuteThread.execute(ExecuteThrea d.java:251)
    > at weblogic.kernel.ExecuteThread.run(ExecuteThread.ja va:219)
    >>

    > <101104> >in servlet
    >context "ServletContext(id=6480502,name=console,context-path=/console)"
    >failed,
    >java.net.ProtocolException: Didn't meet stated Content-Length, wrote:
    >'12216'
    >bytes instead of stated: '34079' bytes.
    >java.net.ProtocolException: Didn't meet stated Content-Length, wrote:
    >'12216'
    >bytes instead of stated: '34079' bytes.
    > at weblogic.servlet.internal.ServletOutputStreamImpl. ensureContentLength
    >(ServletOutputStreamImpl.java:469)
    > at weblogic.servlet.internal.ServletResponseImpl.ensu reContentLength(ServletResponseImpl.java:1186)
    > at weblogic.servlet.internal.ServletResponseImpl.send (ServletResponseImpl.java:1198)
    > at weblogic.servlet.internal.ServletRequestImpl.execu te(ServletRequestImpl.java:2560)
    > at weblogic.kernel.ExecuteThread.execute(ExecuteThrea d.java:251)
    > at weblogic.kernel.ExecuteThread.run(ExecuteThread.ja va:219)



  3. Problem disappeared by itself


    Now when I tried it for one last time, for some strange reason, I did not get this
    error in server log. Looks like the problme has been resolved by itself.

    Thanks.

    Peter.

    "Peter Vennel" wrote:
    >
    >Hi,
    >
    >I am getting this error when starting the admin console. Any ideas what
    >is causing
    >this??
    >



+ Reply to Thread