Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

java.net.ProtocolException

28 views
Skip to first unread message

Rajib

unread,
Mar 10, 2004, 1:30:37 AM3/10/04
to

Hi,

I am getting this error while my application is running.

####<Mar 7, 2004 11:18:14 AM PST> <Error> <HTTP> <websrv24> <myserver> <ExecuteThread:
'22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-101104> <Servlet
execution in servlet context "ServletContext(id=7143557,name=testDummyExpressWebApp,context-path=)"
failed, java.net.ProtocolException: Didn't meet stated Content-Length, wrote:
'134376' bytes instead of stated: '1570782' bytes..
java.net.ProtocolException: Didn't meet stated Content-Length, wrote: '134376'
bytes instead of stated: '1570782' bytes.
at weblogic.servlet.internal.ServletOutputStreamImpl.ensureContentLength(ServletOutputStreamImpl.java:470)
at weblogic.servlet.internal.ServletResponseImpl.ensureContentLength(ServletResponseImpl.java:1176)
at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1188)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2590)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

Can somebody give a brief idea why i am getting this error?

Thanks in advance,
Raj

Robert Greig

unread,
Mar 10, 2004, 5:02:04 AM3/10/04
to
Rajib wrote:

The error means that at some point your application has set the
"Content-Length" http header but when the response has been committed
you haven't actually written the number of bytes you specified in the
header.

You can set the Content-Length header when you are streaming back binary
data (e.g. a Word doc). Doing so allows the client to display as %-age
complete dialog (for example).

Robert

0 new messages