求解：java.net.ProtocolException: Didn't meet stated Content-Length, wrote: '0' byt

在开发环境不出现上面的错误。但是在正式环境报这个错误。并在在出现这个错误之前，weblogic服务占用的CPU会变的很高，导致访问速度变的很慢。

下面是异常信息：
第一个异常：
<2011-6-10 下午03时06分52秒 CST> <Error> <HTTP> <BEA-101083> <Connection failure
.
java.net.ProtocolException: Didn't meet stated Content-Length, wrote: '0' bytes
instead of stated: '39936' bytes.
        at weblogic.servlet.internal.ServletOutputStreamImpl.ensureContentLength
()V(Optimized Method)
        at weblogic.servlet.internal.ServletResponseImpl.ensureContentLength()V(
Optimized Method)
        at weblogic.servlet.internal.ServletResponseImpl.send()V(Optimized Metho
d)
        at weblogic.servlet.internal.ServletRequestImpl.execute(Lweblogic.kernel
.ExecuteThread;)V(Optimized Method)
        at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest
;)V(Optimized Method)
        at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
        at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Sourc
e)
>
第二个异常：(/AAA/servlet/DownAdjunct下载附件的)
<2011-6-10 下午03时46分01秒 CST> <Error> <WebLogicServer> <BEA-000337> <ExecuteT
hread: '2' for queue: 'weblogic.kernel.Default' has been busy for "855" seconds
working on the request "Http Request: /AAA/servlet/DownAdjunct", which is m
ore than the configured time (StuckThreadMaxTime) of "600" seconds.>

评论

2 楼 cfree 2012-09-22  

一般是用了response 写数据回去，设置下response.setContextLength(xxx) 就好了

1 楼 htl0834 2012-05-21  

请问，问题现在解决了么