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

Mysterious Exception: java.net.SocketException: Socket closed

97 views
Skip to first unread message

Gabi

unread,
Dec 31, 2001, 9:46:55 AM12/31/01
to

Hi,

Every (non-deterministic) once and a while I get the next exception on the server
when calling a servlet. The line "Cannot parse POST parameters of request ..."
is very unclear to me. Did you see it before?

Here is the whole snippet:

<Dec 31, 2001 10:41:10 AM IST> <Error> <Kernel> <ExecuteRequest failed
java.net.SocketException: Socket closed
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:86)
at weblogic.servlet.internal.PostInputStream.read(PostInputStream.java:124)
at weblogic.servlet.internal.ServletInputStreamImpl$1.read(ServletInputStreamImpl.java:60)
at weblogic.servlet.internal.ServletInputStreamImpl.read(ServletInputStreamImpl.java:97)
at weblogic.servlet.internal.ServletRequestImpl.mergePostParams(ServletRequestImpl.java:891)
at weblogic.servlet.internal.ServletRequestImpl.parseQueryParams(ServletRequestImpl.java:779)
at weblogic.servlet.internal.ServletRequestImpl.getParameter(ServletRequestImpl.java:953)
at weblogic.servlet.internal.ServletRequestImpl.initSessionInfo(ServletRequestImpl.java:1824)
at weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1684)
at weblogic.servlet.internal.ServletRequestImpl.getRemoteUser(ServletRequestImpl.java:1022)
at weblogic.servlet.logging.CLFLogger.log(CLFLogger.java:60)
at weblogic.servlet.logging.LogManagerHttp.log(LogManagerHttp.java:292)
at weblogic.servlet.internal.HttpServer.log(HttpServer.java:783)
at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:987)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1964)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.utils.NestedRuntimeException: Cannot parse POST parameters of request:
'/collectors' - with nested exception:
[java.net.SocketException: Socket closed]
at weblogic.servlet.internal.ServletRequestImpl.mergePostParams(ServletRequestImpl.java:911)
at weblogic.servlet.internal.ServletRequestImpl.parseQueryParams(ServletRequestImpl.java:779)
at weblogic.servlet.internal.ServletRequestImpl.getParameter(ServletRequestImpl.java:953)
at weblogic.servlet.internal.ServletRequestImpl.initSessionInfo(ServletRequestImpl.java:1824)
at weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1684)
at weblogic.servlet.internal.ServletRequestImpl.getRemoteUser(ServletRequestImpl.java:1022)
at weblogic.servlet.logging.CLFLogger.log(CLFLogger.java:60)
at weblogic.servlet.logging.LogManagerHttp.log(LogManagerHttp.java:292)
at weblogic.servlet.internal.HttpServer.log(HttpServer.java:783)
at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:987)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1964)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>


cheers,

Gabi,

Gabi

unread,
Jan 3, 2002, 9:36:28 AM1/3/02
to

hi,

I use W2K, WLS6.1 with JDK131.
I can not reproduce the exception, it just happens ...

thanks,
Gabu,

"Jame" <ja...@bluesoft.com.cn> wrote:
>Are you using WLS6.1sp1?Which platform?I'd seen it,just a little
>difference,not"socket closed" ,but "Read timed out".
>and the version is WLS6.1 sp1 ,platform is HP-UX
>But someone said that the same program did not match such exception on
>WLS6.1.
>I don't know,but you could try WLS6.1 with JDK130 not JDK131 .
>"Gabi" <ga...@negev.net> wrote in message
>news:3c307a5f$1...@newsgroups.bea.com...


>>
>> Hi,
>>
>> Every (non-deterministic) once and a while I get the next exception
>on the
>server
>> when calling a servlet. The line "Cannot parse POST parameters of request

>...."


>> is very unclear to me. Did you see it before?
>>
>> Here is the whole snippet:
>>
>> <Dec 31, 2001 10:41:10 AM IST> <Error> <Kernel> <ExecuteRequest failed
>> java.net.SocketException: Socket closed
>> at java.net.SocketInputStream.socketRead(Native Method)
>> at java.net.SocketInputStream.read(SocketInputStream.java:86)
>> at
>weblogic.servlet.internal.PostInputStream.read(PostInputStream.java:124)
>> at
>weblogic.servlet.internal.ServletInputStreamImpl$1.read(ServletInputStreamIm
>pl.java:60)
>> at
>weblogic.servlet.internal.ServletInputStreamImpl.read(ServletInputStreamImpl

>..java:97)
>> at
>weblogic.servlet.internal.ServletRequestImpl.mergePostParams(ServletRequestI
>mpl.java:891)
>> at
>weblogic.servlet.internal.ServletRequestImpl.parseQueryParams(ServletRequest
>Impl.java:779)
>> at
>weblogic.servlet.internal.ServletRequestImpl.getParameter(ServletRequestImpl
>..java:953)
>> at
>weblogic.servlet.internal.ServletRequestImpl.initSessionInfo(ServletRequestI
>mpl.java:1824)
>> at
>weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
>ava:1684)
>> at
>weblogic.servlet.internal.ServletRequestImpl.getRemoteUser(ServletRequestImp

>..java:953)
>> at
>weblogic.servlet.internal.ServletRequestImpl.initSessionInfo(ServletRequestI
>mpl.java:1824)
>> at
>weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
>ava:1684)
>> at
>weblogic.servlet.internal.ServletRequestImpl.getRemoteUser(ServletRequestImp

Narinder Gaheer

unread,
Jan 3, 2002, 6:15:45 PM1/3/02
to
Are you running weblogic with Rolling Patch 2. We had a similar problem with
weblogic on Win2k
and RP2 resolved it.

Here is the link :-

http://commerce.bea.com/downloads/wls_patches.jsp

Hope that helps.

Narinder


"Gabi" <ga...@negev.net> wrote in message

news:3c346c6c$2...@newsgroups.bea.com...

Gabi

unread,
Jan 9, 2002, 8:07:52 AM1/9/02
to

hi,

I use WLS6.1 under W2K with no sp's

cheers,

Gabi,

Steve Schaber

unread,
Jan 10, 2002, 11:47:44 AM1/10/02
to

Has anyone solved this issue???

I am noticing that there are many people reporting this issue but it seems that
nobody has fixed it. Is this true?

0 new messages