cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geoff Howard <ghow...@crosswalk.com>
Subject RE:
Date Sat, 22 Jun 2002 03:15:28 GMT
Looks like you're using WebSphere?  I wonder if there is a bug/conflict with
the error handling process when run on WebSphere.  Are you testing the error
handling, or are there two problems here - one that your pipeline is
throwing an error and the other that the error handling isn't working?

Is it possible to run the same setup on Tomcat for a test?  Can you provide
the relevant sitemap portions, including the error handling pipeline?

Geoff Howard

-----Original Message-----
From: Adam_Waldal@eFunds.com [mailto:Adam_Waldal@eFunds.com]
Sent: Tuesday, June 18, 2002 11:43 AM
To: cocoon-users@xml.apache.org
Subject: Re: 



Can anyone enlighten me as to how I can fix the following Exception?

We are trying to run and duplicate some of the examples and are recieving
this.

Thanks,
Adam
----- Forwarded by Adam Waldal/SHV/eFunds on 06/18/02 10:37 AM -----
 

                      K Ramesh@INEFUNDS

                                               To:      Adam
Waldal/SHV/eFunds@EFUNDS                                                 
                      06/18/02 10:43 AM        cc:

                                               Fax to:

                                               Subject: Re: (Document link:
Adam Waldal)                                              
 




Here it is

Error page exception
The server cannot use the error page specified for your application to
handle the Original Exception printed below. Please see the Error Page
Exception below for a description of the problem with the specified error
page.

Original Exception:
Error Message: [Cocoon2] reported an error
Error Code: 404
Target Servlet: Cocoon2
Error Stack:
com.ibm.servlet.engine.webapp.WebAppErrorReport: [Cocoon2] reported an
error
     at
com.ibm.servlet.engine.webapp.WebAppDispatcherResponse.sendError(WebAppDispa
tcherResponse.java:85)


     at
com.ibm.servlet.engine.webapp.WebAppDispatcherResponse.sendError(WebAppDispa
tcherResponse.java:68)


     at
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1024)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager
.java:827)


     at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.
_service(StrictLifecycleServlet.java:167)
     at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServle
t.java:297)


     at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycle
Servlet.java:110)


     at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:47
2)


     at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletMan
ager.java:1012)


     at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManag
er.java:913)


     at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebAppRequestDispatcher.java:523)


     at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequest
Dispatcher.java:282)


     at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestD
ispatcher.java:112)


     at
com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:91)
     at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.
java:184)


     at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedIn
vocation.java:67)


     at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequ
estProcessor.java:122)


     at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener
.java:315)


     at
com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.ja
va:60)


     at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:323)


     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:252)
     at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122)



Error Page Exception:
Error Message: OutputStream already obtained
Error Code: 0
Target Servlet: null
Error Stack:
java.lang.IllegalStateException: OutputStream already obtained
     at
com.ibm.servlet.engine.srt.SRTServletResponse.getWriter(SRTServletResponse.j
ava:316)


     at
com.ibm.servlet.engine.webapp.HttpServletResponseProxy.getWriter(HttpServlet
ResponseProxy.java:101)


     at com.ibm.servlet.engine.webapp.WebApp.sendError(WebApp.java:617)
     at
com.ibm.servlet.engine.webapp.WebAppDispatcherResponse.sendError(WebAppDispa
tcherResponse.java:91)


     at
com.ibm.servlet.engine.webapp.WebAppDispatcherResponse.sendError(WebAppDispa
tcherResponse.java:68)


     at
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1024)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager
.java:827)


     at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.
_service(StrictLifecycleServlet.java:167)
     at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServle
t.java:297)


     at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycle
Servlet.java:110)


     at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:47
2)


     at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletMan
ager.java:1012)


     at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManag
er.java:913)


     at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebAppRequestDispatcher.java:523)


     at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequest
Dispatcher.java:282)


     at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestD
ispatcher.java:112)


     at
com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:91)
     at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.
java:184)


     at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedIn
vocation.java:67)


     at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequ
estProcessor.java:122)


     at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener
.java:315)


     at
com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.ja
va:60)


     at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:323)


     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:252)
     at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122)

Error 500: ERROR: Cannot set header. Response already committed.




 

                      Adam

                      Waldal@EFUNDS            To:      K
Ramesh/CHE/INeFunds@INEFUNDS                                                
                                               cc:

                      06/18/02 09:03 PM        Subject: Re: (Document link:
K Ramesh)                                                 
 

 




Ramesh,
      The attachment seems empty.  Could you check it and send it again.
-Adam


 

                      K Ramesh@INEFUNDS

                                               To:       Adam
Waldal/SHV/eFunds@eFunds                                                 
                      06/18/02 10:33 AM        cc:

                                               Fax to:

                                               Subject:

 




(See attached file: samples.htm)
This is the error i get when i run any of the cocoon samples from websphere
environment.







---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <cocoon-users-unsubscribe@xml.apache.org>
For additional commands, e-mail:   <cocoon-users-help@xml.apache.org>


Mime
View raw message