Shannon
"Sean Scott" <sco...@zilliant.com> wrote in message
news:8cktkp$bka$1...@bayview.weblogic.com...
> On http request to weblogic I am getting a SocketException from
FileServlet.
>
> This just started with the upgrade from 5.1b2 to the final release of 5.1.
> Happens on both JSP pages and static html pages.
>
> Running jdk1.2.2, wl 5.1, NT 4 SP5
>
> Fri Apr 07 08:52:07 CDT 2000:<E> <ServletContext-General> Servlet failed
> with Exception
> java.net.SocketException: socket write error (code=10053)
> at java.net.SocketOutputStream.socketWrite(Native Method)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:87)
> at
> weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:88)
> at
>
weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamI
> mpl
> .java:121)
> at
>
weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(ServletOutputS
> tre
> amImpl.java:444)
> at weblogic.servlet.FileServlet.sendFile(FileServlet.java:199)
> at weblogic.servlet.FileServlet.service(FileServlet.java:56)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
> at
>
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :10
> 5)
> at
>
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
> l.j
> ava:742)
> at
>
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
> l.j
> ava:686)
> at
>
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
> Man
> ager.java:247)
> at
>
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
> at
> weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
>
>
They certainly are annoying. We paid big bucks to get Premium 24/7 service
from Weblogic so I will ask them about this tomorrow when I talk to them.
Til then...
Shannon Wheatley <swhe...@medibuy.com> wrote in message
news:8clkir$ik8$1...@bayview.weblogic.com...
I've included the exception I get (it has a second exception at the bottom which
lead me to the likely cause). As with the others this worked on Beta2 but not
on the release.
-Dominic
Fri Apr 07 08:08:06 GMT 2000:<I> <ServletContext-General> file: init
Fri Apr 07 08:08:07 GMT 2000:<E> <ServletContext-General> Servlet failed
with Exception
java.net.SocketException: socket write error (code=10053)
at java.net.SocketOutputStream.socketWrite(Native Method)
at java.net.SocketOutputStream.write(SocketOutputStream.java,
Compiled Code)
at
weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java,
Compiled Code)
at
weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:121)
at
weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(ServletOutputStreamImpl.java,
Co
mpiled Code)
at weblogic.servlet.FileServlet.sendFile(FileServlet.java:199)
at weblogic.servlet.FileServlet.service(FileServlet.java:56)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
Compiled Code)
Fri Apr 07 08:08:07 GMT 2000:<E> <HTTP> Servlet request terminated with
IOException:
java.net.ProtocolException: Didn't meet stated Content-Length, wrote:
'4096' bytes instead of stated: '11
5993' bytes.
at
weblogic.servlet.internal.ServletOutputStreamImpl.finish(ServletOutputStreamImpl.java:372)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:249)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
Compiled Code)
Event throws the exception on a simple html page with 2 urls (ie, no jsp,
real simple html).
I have had a problem report open since the 5th or 6th and have still not
heard back.
"Dominic Tulley" <dom...@qss.co.uk> wrote in message
news:38F18629...@qss.co.uk...
"Sean Scott" <sco...@zilliant.com> wrote in message
news:8ctmr4$m44$1...@bayview.weblogic.com...
Although I get the error message things seemed to work correctly and moving to
JDK 1.1 may prove upsetting at this stage in our development...
Cheers,
-Dominic
BEA Response:
I have reported the problem, the problem is under our developer's view, the
fix will go into our service pack 1 for weblogic server 5.1.0. but for now,
I do not have a date for service pack, I will let you know when I have
further information. and this problem does not happen when use netscape.
"Dominic Tulley" <dom...@qss.co.uk> wrote in message
news:38F5E768...@qss.co.uk...