Websphere message "WebApp is not alive"

Anony

未読、

2002/08/19 22:54:412002/08/19

To:

I am using IBM Websphere 3.5.x on HP-UX

What does this error mean?

Error 500
An error has occured while processing
request:http://web.foobar.com/blah/index.html
Message: WebApp is not alive

Target Servlet: null
StackTrace:
----------------------------------------------------------------------------
----
Root Error-1: WebApp is not alive

javax.servlet.ServletException: WebApp is not alive
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebAppRequestDispatcher.java:312)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequest
Dispatcher.java:234)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestD
ispatcher.java:138)
at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.
java:77)
at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedIn
vocation.java:67)
at
com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(Cacheabl
eInvocationContext.java:106)
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequ
estProcessor.java:160)
at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener
.java:300)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp$ServiceRunnable.run(SQ
EventListenerImp.java:230)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp.notifySQEvent(SQEventL
istenerImp.java:104)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQEventSource.notifyEvent(SQE
ventSource.java:212)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.notifyService(SQWrapperEventSource.java:353)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.run(SQWrapperEventSource.java:220)
at
com.ibm.servlet.engine.oselistener.outofproc.OutOfProcThread$CtlRunnable.run
(OutOfProcThread.java:248)
at java.lang.Thread.run(Thread.java:479)

----------------------------------------------------------------------------
----
Wrapped Error-2: WebApp is not alive

com.ibm.servlet.engine.webapp.WebAppErrorReport: WebApp is not alive
at com.ibm.servlet.engine.webapp.WebApp.sendError(WebApp.java:524)
at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.
java:92)
at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedIn
vocation.java:67)
at
com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(Cacheabl
eInvocationContext.java:106)
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequ
estProcessor.java:160)
at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener
.java:300)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp$ServiceRunnable.run(SQ
EventListenerImp.java:230)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp.notifySQEvent(SQEventL
istenerImp.java:104)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQEventSource.notifyEvent(SQE
ventSource.java:212)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.notifyService(SQWrapperEventSource.java:353)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.run(SQWrapperEventSource.java:220)
at
com.ibm.servlet.engine.oselistener.outofproc.OutOfProcThread$CtlRunnable.run
(OutOfProcThread.java:248)
at java.lang.Thread.run(Thread.java:479)

Ken Hygh

未読、

2002/08/20 5:39:052002/08/20

To:

It could mean that the application server is not started (note that's
application server, not admin server), that the web application had a
startup problem (like one of its servlets' init() methods failed), or a
mismatch between the plugin config files and the websphere configuration.
Ken

> ..java:300)

Anony

未読、

2002/08/26 0:48:462002/08/26

To:

I resolved this problem.

Here's how I fixed it:

Our web application was allocating a bunch of JDBC connections.
The connections were never getting closed.

At one point, I found that our system had 125 JDBC connections open.

The number of JDBC connections was increasing at a rapid rate.

On HP-UX, you can view the open socket connections using this command:

netstat -a

The netstat command helped me realize that far too many connections
were open.

>
> I am using IBM Websphere 3.5.x on HP-UX
>
> What does this error mean?
>
> Error 500
> An error has occured while processing
> request:http://web.foobar.com/blah/index.html
> Message: WebApp is not alive
>
> Target Servlet: null
> StackTrace:
> --------------------------------------------------------------------------
--

> Root Error-1: WebApp is not alive
>

> [...]
>