Re: Eclipse, Tomcat and Sysdeo Plugin
That's interesting. I must admit, that i took the following road: 1.) set up a project with eclipse as described in my first email 2.) build the cocoon distrib with ant as described in the cocoon docs. 3.) use the so generated webapp to work in my tomcat 4.) link the classes directory of eclipse into cocoon/WEB-INF/classes 5.) enable remote debugging on my tomcat This worked for me. And i can modify cocoon, save the sources, get my modified class files generated from eclipse, restart the cocoon webapp and everything works as expected. sorry, i can;t tell you moree about why your classes cant be seen from tomcat ... maybe someone else has more knowledge ??? regards, hussayn Helmut Tammen wrote: Thank you Hussayn, I compiled my sources, got no compiler errors and mostly everything inside cocoon worked fine. But when I started the portal application which I wanted to debug I´ve got the error that org.appache.cocoon.webapps.authentication.components.AuthenticationManager could not be loaded in spite of being present under WEB-INF/classes. I then copied the cocoon*.jar files that were build with the ant script back to WEB-INF/lib and deleted WEB-INF/classes and everything worked fine again, even the portal application. Any ideas? Thanks Helmut On Tue, 25 Mar 2003 18:51:25 +0100, Hussayn Dabbous [EMAIL PROTECTED] wrote: ok, here is what i did (briefly): 1.) Set up an eclipse java-project named cocoon 2.) Import all cocoon-2.0.4 sources into the cocoon-project (i did this during project creation). 3.) Setup project environment to compile cocoon from within eclipse. You need to add all necessary libs by hand. I also had to discard some classes due to unavailable jars (i remeber about 5 classes only to be deleted from the cocon distrib). Otherwise the project would not compile ;-( 4.) create a launch config as already described on default port 8000 (in fact you can use anything else too) 5.) place breakpoints into any point of the cocoon sources I had no problems as you describe... 6.) Set the JAVA_OPTS as already described. 7.) Start tomcat with startup.sh 8.) Launch the launch config from 4.) 9.) Sit back and watch your appserver beeing fully under your control... no other tricks here ... One question: Why would you prefer to set the JAVA_OPTS by hand? And how are you starting the tomcat server, if you set the JAVA_OPTS by hand ??? I think it is much easier to simply cretae the JAVA_OPTS environment var possibly on a startup script and never think about this again... Ok, remember about this, when you go to production ;-) regards, hussayn ePost wrote: Hi Hussayn, I´m just coming back to the debug problem in eclipse (learning a lot of new stuff at the moment). I´ve set the startup option for tomcat as you adviced (but via command line not via JAVA_OPTS). In eclipse I start the remote debug session which successfully connects to port 8000. But I can´t set any breakpoints in the Cocoon Java Source. Do I have to adjust the source lookup path in eclipse? I´ve already tried some settings but nothing worked. Thanks for your answer. Helmut On Thu, 20 Mar 2003 09:34:06 +0100, SAXESS - Hussayn Dabbous [EMAIL PROTECTED] wrote: Hi, I can't tell you why you get this error, but i can tell you how we are debugging cocoon enabled web applications in a similar environment as yours: We are running eclipse, cocoon-2.0.4, tomcat-4.1.18 on solaris and linux. We run eclipse on a PC-frontend and we always start the tomcat server with the startup scripts. When debuging whichever webapp (including cocoon) we set the JAVA_OPTS as follows: -server -Xdebug -Xnoagent -Djava.compiler=NONE - Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000 Then we (re)start the tomcat server as usual with startup.sh or startup.bat. Please note, that we set the JAVA_OPTS, not the CATALINA_OPTS for this, although the docs at the tomcat site state something else (that does not work for us) On eclipse we set up a remote debugging session on port 8000. This works perfectly! It should also work, when the tomcat server is running locally. regards, hussayn Helmut Tammen wrote: Hi, I try to use the combination of Eclipse, Tomcat and the Sysdeo Plugin to debug the cocoon source in Eclipse. This doesn´t work (error message when trying to access any Cocoon resource at the end). When I start Tomcat via the startup.bat everything works fine. My environment: Windows 2000 Eclipse 2.1 (Beta) JDK 1.4.1_02 Tomcat 4.0.6 Sysdeo plugin for Eclipse 2.1 (Beta) Cocoon 2.1-dev I´ve also tried JDK 1.4.0, Tomcat 4.1.18 and Cocoon 2.0.4 in various combinations with no success. All the Xerces and Xalan libs are replaced with the ones from Cocoon in the directories [JAVA_HOME]/jre/lib/ endorsed, [CATALINA_HOME]/common/endorsed and in [ECLIPSE_HOME]/plugins/org.apache.xerces_4.0.7 (probably not necessary because not in the classpath of my webapp) Does anyone have an idea what´s going wrong here? Thanks in advance Helmut ERROR
Re: Eclipse, Tomcat and Sysdeo Plugin
Hi Hussayn, Im just coming back to the debug problem in eclipse (learning a lot of new stuff at the moment). Ive set the startup option for tomcat as you adviced (but via command line not via JAVA_OPTS). In eclipse I start the remote debug session which successfully connects to port 8000. But I cant set any breakpoints in the Cocoon Java Source. Do I have to adjust the source lookup path in eclipse? Ive already tried some settings but nothing worked. Thanks for your answer. Helmut On Thu, 20 Mar 2003 09:34:06 +0100, SAXESS - Hussayn Dabbous [EMAIL PROTECTED] wrote: Hi, I can't tell you why you get this error, but i can tell you how we are debugging cocoon enabled web applications in a similar environment as yours: We are running eclipse, cocoon-2.0.4, tomcat-4.1.18 on solaris and linux. We run eclipse on a PC-frontend and we always start the tomcat server with the startup scripts. When debuging whichever webapp (including cocoon) we set the JAVA_OPTS as follows: -server -Xdebug -Xnoagent -Djava.compiler=NONE - Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000 Then we (re)start the tomcat server as usual with startup.sh or startup.bat. Please note, that we set the JAVA_OPTS, not the CATALINA_OPTS for this, although the docs at the tomcat site state something else (that does not work for us) On eclipse we set up a remote debugging session on port 8000. This works perfectly! It should also work, when the tomcat server is running locally. regards, hussayn Helmut Tammen wrote: Hi, I try to use the combination of Eclipse, Tomcat and the Sysdeo Plugin to debug the cocoon source in Eclipse. This doesnt work (error message when trying to access any Cocoon resource at the end). When I start Tomcat via the startup.bat everything works fine. My environment: Windows 2000 Eclipse 2.1 (Beta) JDK 1.4.1_02 Tomcat 4.0.6 Sysdeo plugin for Eclipse 2.1 (Beta) Cocoon 2.1-dev Ive also tried JDK 1.4.0, Tomcat 4.1.18 and Cocoon 2.0.4 in various combinations with no success. All the Xerces and Xalan libs are replaced with the ones from Cocoon in the directories [JAVA_HOME]/jre/lib/ endorsed, [CATALINA_HOME]/common/endorsed and in [ECLIPSE_HOME]/plugins/org.apache.xerces_4.0.7 (probably not necessary because not in the classpath of my webapp) Does anyone have an idea whats going wrong here? Thanks in advance Helmut ERROR (2003-03-20) 08:33.54:103 [access] (Unknown-URI) Unknown- thread/CocoonServlet: Cocoon got an Exception while trying to close stream. java.io.IOException: The stream has been closed at org.apache.catalina.connector.ResponseStream.flush(ResponseStream.java:237) at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1145) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse, Tomcat and Sysdeo Plugin
ok, here is what i did (briefly): 1.) Set up an eclipse java-project named cocoon 2.) Import all cocoon-2.0.4 sources into the cocoon-project (i did this during project creation). 3.) Setup project environment to compile cocoon from within eclipse. You need to add all necessary libs by hand. I also had to discard some classes due to unavailable jars (i remeber about 5 classes only to be deleted from the cocon distrib). Otherwise the project would not compile ;-( 4.) create a launch config as already described on default port 8000 (in fact you can use anything else too) 5.) place breakpoints into any point of the cocoon sources I had no problems as you describe... 6.) Set the JAVA_OPTS as already described. 7.) Start tomcat with startup.sh 8.) Launch the launch config from 4.) 9.) Sit back and watch your appserver beeing fully under your control... no other tricks here ... One question: Why would you prefer to set the JAVA_OPTS by hand? And how are you starting the tomcat server, if you set the JAVA_OPTS by hand ??? I think it is much easier to simply cretae the JAVA_OPTS environment var possibly on a startup script and never think about this again... Ok, remember about this, when you go to production ;-) regards, hussayn ePost wrote: Hi Hussayn, Im just coming back to the debug problem in eclipse (learning a lot of new stuff at the moment). Ive set the startup option for tomcat as you adviced (but via command line not via JAVA_OPTS). In eclipse I start the remote debug session which successfully connects to port 8000. But I cant set any breakpoints in the Cocoon Java Source. Do I have to adjust the source lookup path in eclipse? Ive already tried some settings but nothing worked. Thanks for your answer. Helmut On Thu, 20 Mar 2003 09:34:06 +0100, SAXESS - Hussayn Dabbous [EMAIL PROTECTED] wrote: Hi, I can't tell you why you get this error, but i can tell you how we are debugging cocoon enabled web applications in a similar environment as yours: We are running eclipse, cocoon-2.0.4, tomcat-4.1.18 on solaris and linux. We run eclipse on a PC-frontend and we always start the tomcat server with the startup scripts. When debuging whichever webapp (including cocoon) we set the JAVA_OPTS as follows: -server -Xdebug -Xnoagent -Djava.compiler=NONE - Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000 Then we (re)start the tomcat server as usual with startup.sh or startup.bat. Please note, that we set the JAVA_OPTS, not the CATALINA_OPTS for this, although the docs at the tomcat site state something else (that does not work for us) On eclipse we set up a remote debugging session on port 8000. This works perfectly! It should also work, when the tomcat server is running locally. regards, hussayn Helmut Tammen wrote: Hi, I try to use the combination of Eclipse, Tomcat and the Sysdeo Plugin to debug the cocoon source in Eclipse. This doesnt work (error message when trying to access any Cocoon resource at the end). When I start Tomcat via the startup.bat everything works fine. My environment: Windows 2000 Eclipse 2.1 (Beta) JDK 1.4.1_02 Tomcat 4.0.6 Sysdeo plugin for Eclipse 2.1 (Beta) Cocoon 2.1-dev Ive also tried JDK 1.4.0, Tomcat 4.1.18 and Cocoon 2.0.4 in various combinations with no success. All the Xerces and Xalan libs are replaced with the ones from Cocoon in the directories [JAVA_HOME]/jre/lib/ endorsed, [CATALINA_HOME]/common/endorsed and in [ECLIPSE_HOME]/plugins/org.apache.xerces_4.0.7 (probably not necessary because not in the classpath of my webapp) Does anyone have an idea whats going wrong here? Thanks in advance Helmut ERROR (2003-03-20) 08:33.54:103 [access] (Unknown-URI) Unknown- thread/CocoonServlet: Cocoon got an Exception while trying to close stream. java.io.IOException: The stream has been closed at org.apache.catalina.connector.ResponseStream.flush(ResponseStream.java:237) at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1145) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse, Tomcat and Sysdeo Plugin
Thank you Hussayn, I compiled my sources, got no compiler errors and mostly everything inside cocoon worked fine. But when I started the portal application which I wanted to debug Ive got the error that org.appache.cocoon.webapps.authentication.components.AuthenticationManager could not be loaded in spite of being present under WEB-INF/classes. I then copied the cocoon*.jar files that were build with the ant script back to WEB-INF/lib and deleted WEB-INF/classes and everything worked fine again, even the portal application. Any ideas? Thanks Helmut On Tue, 25 Mar 2003 18:51:25 +0100, Hussayn Dabbous [EMAIL PROTECTED] wrote: ok, here is what i did (briefly): 1.) Set up an eclipse java-project named cocoon 2.) Import all cocoon-2.0.4 sources into the cocoon-project (i did this during project creation). 3.) Setup project environment to compile cocoon from within eclipse. You need to add all necessary libs by hand. I also had to discard some classes due to unavailable jars (i remeber about 5 classes only to be deleted from the cocon distrib). Otherwise the project would not compile ;-( 4.) create a launch config as already described on default port 8000 (in fact you can use anything else too) 5.) place breakpoints into any point of the cocoon sources I had no problems as you describe... 6.) Set the JAVA_OPTS as already described. 7.) Start tomcat with startup.sh 8.) Launch the launch config from 4.) 9.) Sit back and watch your appserver beeing fully under your control... no other tricks here ... One question: Why would you prefer to set the JAVA_OPTS by hand? And how are you starting the tomcat server, if you set the JAVA_OPTS by hand ??? I think it is much easier to simply cretae the JAVA_OPTS environment var possibly on a startup script and never think about this again... Ok, remember about this, when you go to production ;-) regards, hussayn ePost wrote: Hi Hussayn, Im just coming back to the debug problem in eclipse (learning a lot of new stuff at the moment). Ive set the startup option for tomcat as you adviced (but via command line not via JAVA_OPTS). In eclipse I start the remote debug session which successfully connects to port 8000. But I cant set any breakpoints in the Cocoon Java Source. Do I have to adjust the source lookup path in eclipse? Ive already tried some settings but nothing worked. Thanks for your answer. Helmut On Thu, 20 Mar 2003 09:34:06 +0100, SAXESS - Hussayn Dabbous [EMAIL PROTECTED] wrote: Hi, I can't tell you why you get this error, but i can tell you how we are debugging cocoon enabled web applications in a similar environment as yours: We are running eclipse, cocoon-2.0.4, tomcat-4.1.18 on solaris and linux. We run eclipse on a PC-frontend and we always start the tomcat server with the startup scripts. When debuging whichever webapp (including cocoon) we set the JAVA_OPTS as follows: -server -Xdebug -Xnoagent -Djava.compiler=NONE - Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000 Then we (re)start the tomcat server as usual with startup.sh or startup.bat. Please note, that we set the JAVA_OPTS, not the CATALINA_OPTS for this, although the docs at the tomcat site state something else (that does not work for us) On eclipse we set up a remote debugging session on port 8000. This works perfectly! It should also work, when the tomcat server is running locally. regards, hussayn Helmut Tammen wrote: Hi, I try to use the combination of Eclipse, Tomcat and the Sysdeo Plugin to debug the cocoon source in Eclipse. This doesnt work (error message when trying to access any Cocoon resource at the end). When I start Tomcat via the startup.bat everything works fine. My environment: Windows 2000 Eclipse 2.1 (Beta) JDK 1.4.1_02 Tomcat 4.0.6 Sysdeo plugin for Eclipse 2.1 (Beta) Cocoon 2.1-dev Ive also tried JDK 1.4.0, Tomcat 4.1.18 and Cocoon 2.0.4 in various combinations with no success. All the Xerces and Xalan libs are replaced with the ones from Cocoon in the directories [JAVA_HOME]/jre/lib/ endorsed, [CATALINA_HOME]/common/endorsed and in [ECLIPSE_HOME]/plugins/org.apache.xerces_4.0.7 (probably not necessary because not in the classpath of my webapp) Does anyone have an idea whats going wrong here? Thanks in advance Helmut ERROR (2003-03-20) 08:33.54:103 [access] (Unknown-URI) Unknown- thread/CocoonServlet: Cocoon got an Exception while trying to close stream. java.io.IOException: The stream has been closed at org.apache.catalina.connector.ResponseStream.flush(ResponseStream.java:237) at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1145) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2
Eclipse, Tomcat and Sysdeo Plugin
Hi, I try to use the combination of Eclipse, Tomcat and the Sysdeo Plugin to debug the cocoon source in Eclipse. This doesnt work (error message when trying to access any Cocoon resource at the end). When I start Tomcat via the startup.bat everything works fine. My environment: Windows 2000 Eclipse 2.1 (Beta) JDK 1.4.1_02 Tomcat 4.0.6 Sysdeo plugin for Eclipse 2.1 (Beta) Cocoon 2.1-dev Ive also tried JDK 1.4.0, Tomcat 4.1.18 and Cocoon 2.0.4 in various combinations with no success. All the Xerces and Xalan libs are replaced with the ones from Cocoon in the directories [JAVA_HOME]/jre/lib/endorsed, [CATALINA_HOME]/common/endorsed and in [ECLIPSE_HOME]/plugins/org.apache.xerces_4.0.7 (probably not necessary because not in the classpath of my webapp) Does anyone have an idea whats going wrong here? Thanks in advance Helmut ERROR (2003-03-20) 08:33.54:103 [access] (Unknown-URI) Unknown- thread/CocoonServlet: Cocoon got an Exception while trying to close stream. java.io.IOException: The stream has been closed at org.apache.catalina.connector.ResponseStream.flush(ResponseStream.java:237) at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1145) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125) at java.lang.Thread.run(Thread.java:536) FATAL_E (2003-03-20) 08:33.57:218 [access] (/cocoon21/samples/welcome) HttpProcessor[8080][4]/CocoonServlet: The Cocoon engine failed to process the request. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse, Tomcat and Sysdeo Plugin
Hi, I can't tell you why you get this error, but i can tell you how we are debugging cocoon enabled web applications in a similar environment as yours: We are running eclipse, cocoon-2.0.4, tomcat-4.1.18 on solaris and linux. We run eclipse on a PC-frontend and we always start the tomcat server with the startup scripts. When debuging whichever webapp (including cocoon) we set the JAVA_OPTS as follows: -server -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000 Then we (re)start the tomcat server as usual with startup.sh or startup.bat. Please note, that we set the JAVA_OPTS, not the CATALINA_OPTS for this, although the docs at the tomcat site state something else (that does not work for us) On eclipse we set up a remote debugging session on port 8000. This works perfectly! It should also work, when the tomcat server is running locally. regards, hussayn Helmut Tammen wrote: Hi, I try to use the combination of Eclipse, Tomcat and the Sysdeo Plugin to debug the cocoon source in Eclipse. This doesnt work (error message when trying to access any Cocoon resource at the end). When I start Tomcat via the startup.bat everything works fine. My environment: Windows 2000 Eclipse 2.1 (Beta) JDK 1.4.1_02 Tomcat 4.0.6 Sysdeo plugin for Eclipse 2.1 (Beta) Cocoon 2.1-dev Ive also tried JDK 1.4.0, Tomcat 4.1.18 and Cocoon 2.0.4 in various combinations with no success. All the Xerces and Xalan libs are replaced with the ones from Cocoon in the directories [JAVA_HOME]/jre/lib/endorsed, [CATALINA_HOME]/common/endorsed and in [ECLIPSE_HOME]/plugins/org.apache.xerces_4.0.7 (probably not necessary because not in the classpath of my webapp) Does anyone have an idea whats going wrong here? Thanks in advance Helmut ERROR (2003-03-20) 08:33.54:103 [access] (Unknown-URI) Unknown- thread/CocoonServlet: Cocoon got an Exception while trying to close stream. java.io.IOException: The stream has been closed at org.apache.catalina.connector.ResponseStream.flush(ResponseStream.java:237) at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1145) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125) at java.lang.Thread.run(Thread.java:536) FATAL_E (2003-03-20) 08:33.57:218 [access] (/cocoon21/samples/welcome) HttpProcessor[8080][4]/CocoonServlet: The Cocoon engine failed to process the request
Re: Eclipse, Tomcat and Sysdeo Plugin
On czw, mar 20, 2003 at 09:34:06 +0100, SAXESS - Hussayn Dabbous wrote: Hi, I can't tell you why you get this error, but i can tell you how we are debugging cocoon enabled web applications in a similar environment as yours: We are running eclipse, cocoon-2.0.4, tomcat-4.1.18 on solaris and linux. We run eclipse on a PC-frontend and we always start the tomcat server with the startup scripts. When debuging whichever webapp (including cocoon) we set the JAVA_OPTS as follows: -server -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000 Then we (re)start the tomcat server as usual with startup.sh or startup.bat. Please note, that we set the JAVA_OPTS, not the CATALINA_OPTS for this, although the docs at the tomcat site state something else (that does not work for us) On eclipse we set up a remote debugging session on port 8000. This works perfectly! It should also work, when the tomcat server is running locally. Yes it is - the only exception is debugging XPSs - couldn't make it work under eclipse. ouzo -- __ | / \ |Leszek Gawron// \\ \_\\ //_/ [EMAIL PROTECTED] _\\()//_ .'/()\'. Phone: +48(600)341118 / // \\ \ \\ // recursive: adj; see recursive | \__/ | - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Eclipse, Tomcat and Sysdeo Plugin
Hello, I'm using this plugin and it works fine but I have: Windows NT Eclipse 2.0 (release) JDK 1.3.1_03 Tomcat 4.1.12 Sysdeo plugin 2.0.1 Cocoon 2.1-dev I know that there was a problem with the plugin and Eclipse 2.1 RC1. The plugin version 2.1beta corrects this problem. But if you use Eclipse 2.1 RC2 I don't know. Have you checked the context in server.xml file? Regards Sylvain (T) -Message d'origine- De: Helmut Tammen [mailto:[EMAIL PROTECTED] Date: jeudi, 20. mars 2003 09:02 : [EMAIL PROTECTED] Objet: Eclipse, Tomcat and Sysdeo Plugin Hi, I try to use the combination of Eclipse, Tomcat and the Sysdeo Plugin to debug the cocoon source in Eclipse. This doesnt work (error message when trying to access any Cocoon resource at the end). When I start Tomcat via the startup.bat everything works fine. My environment: Windows 2000 Eclipse 2.1 (Beta) JDK 1.4.1_02 Tomcat 4.0.6 Sysdeo plugin for Eclipse 2.1 (Beta) Cocoon 2.1-dev Ive also tried JDK 1.4.0, Tomcat 4.1.18 and Cocoon 2.0.4 in various combinations with no success. All the Xerces and Xalan libs are replaced with the ones from Cocoon in the directories [JAVA_HOME]/jre/lib/endorsed, [CATALINA_HOME]/common/endorsed and in [ECLIPSE_HOME]/plugins/org.apache.xerces_4.0.7 (probably not necessary because not in the classpath of my webapp) Does anyone have an idea whats going wrong here? Thanks in advance Helmut ERROR (2003-03-20) 08:33.54:103 [access] (Unknown-URI) Unknown- thread/CocoonServlet: Cocoon got an Exception while trying to close stream. java.io.IOException: The stream has been closed at org.apache.catalina.connector.ResponseStream.flush(ResponseStream.java:237) at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1145) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125) at java.lang.Thread.run(Thread.java:536) FATAL_E (2003-03-20) 08:33.57:218 [access] (/cocoon21/samples/welcome) HttpProcessor[8080][4]/CocoonServlet: The Cocoon engine failed to process the request. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
