| Author |
JSP EXCEPTION NUMBER 19002
|
|
| karen4 2004-01-19, 8:21 am |
| could some one let me know what is this error means.This are the errors throwing on Appserver
com.bo.wibean.WIException: WebIntelligence SDK / JSP Exception --- Number :19002 --- javaError : java.lang.IllegalStateException: Context has not been prepared for nex
t connection --- Description : General SYSTEM Exception
at com.bo.wibean.WIHelper.handleGeneralErrors(WIHelper.java(Compiled Code))
at com.bo.wibean.WIServerImpl.getSession(WIServerImpl.java(Compiled Code))
at com.busch.bo.framework.webi.isValidSession(webi.java(Compiled Code))
at com.busch.wms.wscui.common.controllers.WSCDispatcherServlet.processRequest(WSCDispatcherServlet.java(Compiled Code))
at com.busch.wms.wscui.common.controllers.WSCDispatcherServlet.doPost(WSCDispatcherServlet.java(Compiled Code))
at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
at com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java(Compiled Code))
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java(Compiled Code))
at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java(Compiled Code))
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java(Inlined Compiled Code))
at com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java(Compiled Code))
at com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java(Compiled Code))
at com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java(Inlined Compiled Code))
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher. handleWebAppDispatch(WebAppRequestDispat
cher.java(Compiled Code))
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java(Compiled Code))
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java(Compiled Code))
at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java(Compiled Code))
at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java(Compiled Code))
at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java(Compiled Code))
at com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java(Compiled Code))
at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java(Compiled Code))
at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java(Compiled Code))
at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java(Compiled Code))
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java(Compiled Code))
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java(Compiled Code))
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:138)
| |
| Ken Hygh 2004-01-19, 8:21 am |
| karen4 wrote:quote:
> could some one let me know what is this error means.This are the errors throwing on Appserver
>
>
> com.bo.wibean.WIException: WebIntelligence SDK / JSP Exception --- Number :19002 --- javaError : java.lang.IllegalStateException: Context has not been prepared for nex
> t connection --- Description : General SYSTEM Exception
> at com.bo.wibean.WIHelper.handleGeneralErrors(WIHelper.java(Compiled Code))
> at com.bo.wibean.WIServerImpl.getSession(WIServerImpl.java(Compiled Code))
> at com.busch.bo.framework.webi.isValidSession(webi.java(Compiled Code))
> at com.busch.wms.wscui.common.controllers.WSCDispatcherServlet.processRequest(WSCDispatcherServlet.java(Compiled Code))
> at com.busch.wms.wscui.common.controllers.WSCDispatcherServlet.doPost(WSCDispatcherServlet.java(Compiled Code))
> at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
> at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
> at com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java(Compiled Code))
> at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java(Compiled Code))
> at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java(Compiled Code))
> at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java(Inlined Compiled Code))
> at com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java(Compiled Code))
> at com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java(Compiled Code))
> at com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java(Inlined Compiled Code))
> at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher. handleWebAppDispatch(WebAppRequestDispat
cher.java(Compiled Code))
> at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java(Compiled Code))
> at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java(Compiled Code))
> at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java(Compiled Code))
> at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java(Compiled Code))
> at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java(Compiled Code))
> at com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java(Compiled Code))
> at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java(Compiled Code))
> at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java(Compiled Code))
> at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java(Compiled Code))
> at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java(Compiled Code))
> at com.ibm.ws.http.HttpConnection.run(HttpConnection.java(Compiled Code))
> at com.ibm.ws.util.CachedThread.run(ThreadPool.java:138)
>
There was some discussion of this recently on one of the websphere
newsgroups - where the problem was that the programmer had put the
request object into a member variable.
Ken
| |
| karen4 2004-01-19, 8:21 am |
| Ken can you explain to me in more detail.I appreciate your help.Thankyou
| |
| Ken Hygh 2004-01-19, 8:21 am |
| karen4 wrote:quote:
> Ken can you explain to me in more detail.I appreciate your help.Thankyou
Somewhere in your code, and I'm guessing it's in or near
com.busch.wms.wscdui.common.controllers.WSCDispatcherServlet, you're
using the wrong HttpServletRequest object. I suspect that you're not
pasing the request object to processRequest(), but instead are using an
instance variable. Instance variables cannot be used in servlets,
because they aren't threadsafe.
Look for the thread "java.lang.IllegalStateException: Context has not
been prepared for next connection" in
ibm.software.websphere.application-server.v4 - it discusses this
particular error message.
Ken
| |
| karen4 2004-01-19, 8:21 am |
| Thanks Ken.I appreciate your help
|
|
|
|