ASSERTION FAILED - servicepack 10

Per Lovdinger

unread,

Aug 20, 2001, 9:03:34 AM8/20/01

to

Hi,
I've just upgraded to servicepack 10 and I get the following problem.
The problem does not occur all the time.
Any help greatly appreciated...

..Per
============================================================================
====
Enviroment:AIX version 4.3 weblogic 5.10 sp10 clustered environment
============================================================================
====
=========================================================

** Time to process jsp servlet = 31 msecs
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Attempt to
invoke 0
e request ]
at weblogic.utils.Debug.assert(Debug.java(Compiled Code))
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
8)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
Mon Aug 20 12:54:47 GMT+00:00 2001:<E> <HTTP> Connection failure
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Attempt to
invoke 0
e request ]
at weblogic.utils.Debug.assert(Debug.java(Compiled Code))
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
8)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)

weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Attempt to
invoke 0
e request ]
at weblogic.utils.Debug.assert(Debug.java(Compiled Code))
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
8)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
Mon Aug 20 12:54:47 GMT+00:00 2001:<E> <HTTP> Connection failure
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Attempt to
invoke 0
e request ]
at weblogic.utils.Debug.assert(Debug.java(Compiled Code))
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
8)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)

weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Attempt to
invoke 0
e request ]
at weblogic.utils.Debug.assert(Debug.java(Compiled Code))
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
8)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
Mon Aug 20 12:54:54 GMT+00:00 2001:<E> <HTTP> Connection failure
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Attempt to
invoke 0
e request ]
at weblogic.utils.Debug.assert(Debug.java(Compiled Code))
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
8)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)

weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Attempt to
invoke 0
e request ]
at weblogic.utils.Debug.assert(Debug.java(Compiled Code))
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
8)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
Mon Aug 20 12:54:55 GMT+00:00 2001:<E> <HTTP> Connection failure
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Attempt to
invoke 0
e request ]
at weblogic.utils.Debug.assert(Debug.java(Compiled Code))
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
8)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)

anna-maija.vesterinen

unread,

Sep 24, 2001, 11:55:29 AM9/24/01

to

Hi,

I have a similar problem in out production environment. Have you/any one had any luck in finding out any solution?

rgds,
Ansku

Tim Jowers

unread,

Oct 11, 2001, 1:30:50 PM10/11/01

to

Same problem for us. SP10 worked fine in development and test but has this problem
on the production servers. Part of the message is about a "0 byte request" so
perhaps this has to do with an ISP issue as this does not occur on other test
clients.

Ideas?
Tim