RE: invoker servlet, tomcat 4.1.29, apache 2.0.48 and connector jk2
for that app) is : Context path= docBase=/home/httpd/html/intranet debug=0 reloadable=true crossContext=true Resources className=org.apache.naming.resources.FileDirContext allowLinking=true/ /Context Any idea ? Thanks Max -Original Message- From: Justin Ruthenbeck [mailto:[EMAIL PROTECTED] Sent: January 6, 2004 3:22 PM To: Tomcat Users List Subject: Re: invoker servlet, tomcat 4.1.29, apache 2.0.48 and connector jk2 Since you're able to hit your servlets through the invoker when pointing to Tomcat directly, this sounds like a connector problem. Check your workers[2].properties to make sure you're passing requests for /servlet through to Apache. justin At 11:47 AM 1/6/2004, you wrote: http://jakarta.apache.org/tomcat/faq/misc.html#invoker -Tim Maxime Pelletier wrote: Hi, We upgraded our tomcat to 4.1.29 and apache to 2.0.48 recently and we have lost access to all servlet invoked in the following form http://address/servlet/MyServlet the apache does no longer pass the request to the tomcat and result in a 404 error (processed by apache). When I use the tomcat only port the servlets are accessibles : http://address:tomcatport/servlet/MyServlet Does anyone have a solution to this ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Justin Ruthenbeck Software Engineer, NextEngine Inc. justinr - AT - nextengine DOT com Confidential. See: http://www.nextengine.com/confidentiality.php __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Justin Ruthenbeck Software Engineer, NextEngine Inc. justinr - AT - nextengine DOT com Confidential. See: http://www.nextengine.com/confidentiality.php __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Justin Ruthenbeck Software Engineer, NextEngine Inc. justinr - AT - nextengine DOT com Confidential. See: http://www.nextengine.com/confidentiality.php __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
invoker servlet, tomcat 4.1.29, apache 2.0.48 and connector jk2
Hi, We upgraded our tomcat to 4.1.29 and apache to 2.0.48 recently and we have lost access to all servlet invoked in the following form http://address/servlet/MyServlet the apache does no longer pass the request to the tomcat and result in a 404 error (processed by apache). When I use the tomcat only port the servlets are accessibles : http://address:tomcatport/servlet/MyServlet Does anyone have a solution to this ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: invoker servlet, tomcat 4.1.29, apache 2.0.48 and connector jk2
Hi, My workers2.properties file have the following entries : [uri:/*.jsp] info=Map to Tomcat All *.jsp In Default Context # context=/ # group=channel.un:/var/log/tomcat/intranet/intranet_jk2.socket group=ajp13:/var/log/tomcat/intranet/intranet_jk2.socket debug=0 disable=0 [uri:/*/.jsp] info=Map to Tomcat All *.jsp In All Contexts # context=/examples # group=channel.un:/var/log/tomcat/intranet/intranet_jk2.socket group=ajp13:/var/log/tomcat/intranet/intranet_jk2.socket debug=0 disable=0 [uri:/servlet/*] info=Map to Tomcat All Files in /servlet In Default Context context=/servlet # group=channel.un:/var/log/tomcat/intranet/intranet_jk2.socket group=ajp13:/var/log/tomcat/intranet/intranet_jk2.socket debug=0 disable=0 [uri:/*/servlet/*] info=Map to Tomcat All Files in /servlet of All Contexts # context=/servlet # group=channel.un:/var/log/tomcat/intranet/intranet_jk2.socket group=ajp13:/var/log/tomcat/intranet/intranet_jk2.socket debug=0 disable=0 My server.xml context (context for that app) is : Context path= docBase=/home/httpd/html/intranet debug=0 reloadable=true crossContext=true Resources className=org.apache.naming.resources.FileDirContext allowLinking=true/ /Context Any idea ? Thanks Max -Original Message- From: Justin Ruthenbeck [mailto:[EMAIL PROTECTED] Sent: January 6, 2004 3:22 PM To: Tomcat Users List Subject: Re: invoker servlet, tomcat 4.1.29, apache 2.0.48 and connector jk2 Since you're able to hit your servlets through the invoker when pointing to Tomcat directly, this sounds like a connector problem. Check your workers[2].properties to make sure you're passing requests for /servlet through to Apache. justin At 11:47 AM 1/6/2004, you wrote: http://jakarta.apache.org/tomcat/faq/misc.html#invoker -Tim Maxime Pelletier wrote: Hi, We upgraded our tomcat to 4.1.29 and apache to 2.0.48 recently and we have lost access to all servlet invoked in the following form http://address/servlet/MyServlet the apache does no longer pass the request to the tomcat and result in a 404 error (processed by apache). When I use the tomcat only port the servlets are accessibles : http://address:tomcatport/servlet/MyServlet Does anyone have a solution to this ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Justin Ruthenbeck Software Engineer, NextEngine Inc. justinr - AT - nextengine DOT com Confidential. See: http://www.nextengine.com/confidentiality.php __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: invoker servlet, tomcat 4.1.29, apache 2.0.48 and connector jk2
I can definitly access the servlets with the tomcat port. Using the following addresses : Tomcat url work http://XX.X.X.XX:8081/servlet/com.wanted.cobrandpropertyeditor.servlet.TextE ditServlet Apache/jk2/tomcat does not work http://XX.X.X.XX/servlet/com.wanted.cobrandpropertyeditor.servlet.TextEditSe rvlet Same thing if I use a servlet-mapping : Tomcat url work http://XX.X.X.XX:8081/servlet/CPE_TextEditServlet Apache/jk2/tomcat does not work http://XX.X.X.XX:8081/servlet/CPE_TextEditServlet Old Tomcat ver. 4.1.24 upgraded to 4.1.29 Old Apache ver. 2.0.45 upgraded to 2.0.48 The conf/web.xml part you are talking about is the following (not commented) : !-- The mapping for the default servlet -- servlet-mapping servlet-namedefault/servlet-name url-pattern//url-pattern /servlet-mapping !-- The mapping for the invoker servlet -- !-- -- servlet-mapping servlet-nameinvoker/servlet-name url-pattern/servlet/*/url-pattern /servlet-mapping !-- -- !-- The mapping for the JSP servlet -- servlet-mapping servlet-namejsp/servlet-name url-pattern*.jsp/url-pattern /servlet-mapping Here is a section of my WEB-INF/web.xml file. It should by ok anyway because it is working with the 8081 port ... servlet servlet-nameCPE_TextEditServlet/servlet-name servlet-classcom.wanted.cobrandpropertyeditor.servlet.TextEditServlet/ser vlet-class !--init-param-- !--param-nameparam1/param-name-- !--param-valuevalue1/param-value-- !--/init-param-- load-on-startup3/load-on-startup /servlet servlet-mapping servlet-nameinvoker/servlet-name url-pattern/servlet/*/url-pattern /servlet-mapping servlet-mapping servlet-nameCPE_TextEditServlet/servlet-name url-pattern/servlet/CPE_TextEditServlet/url-pattern /servlet-mapping Thanks again, Max -Original Message- From: Justin Ruthenbeck [mailto:[EMAIL PROTECTED] Sent: January 6, 2004 4:05 PM To: Tomcat Users List Subject: RE: invoker servlet, tomcat 4.1.29, apache 2.0.48 and connector jk2 This looks correct. What version of Tomcat and Apache did you upgrade from? Are you *sure* you can hit your /servlet/* URLs going directly to Tomcat? Just to be sure: you're aware of the invoker servlet changes that Tim sent a URL to, right (that the invoker is disabled by default)? justin At 12:35 PM 1/6/2004, you wrote: Hi, My workers2.properties file have the following entries : [uri:/*.jsp] info=Map to Tomcat All *.jsp In Default Context # context=/ # group=channel.un:/var/log/tomcat/intranet/intranet_jk2.socket group=ajp13:/var/log/tomcat/intranet/intranet_jk2.socket debug=0 disable=0 [uri:/*/.jsp] info=Map to Tomcat All *.jsp In All Contexts # context=/examples # group=channel.un:/var/log/tomcat/intranet/intranet_jk2.socket group=ajp13:/var/log/tomcat/intranet/intranet_jk2.socket debug=0 disable=0 [uri:/servlet/*] info=Map to Tomcat All Files in /servlet In Default Context context=/servlet # group=channel.un:/var/log/tomcat/intranet/intranet_jk2.socket group=ajp13:/var/log/tomcat/intranet/intranet_jk2.socket debug=0 disable=0 [uri:/*/servlet/*] info=Map to Tomcat All Files in /servlet of All Contexts # context=/servlet # group=channel.un:/var/log/tomcat/intranet/intranet_jk2.socket group=ajp13:/var/log/tomcat/intranet/intranet_jk2.socket debug=0 disable=0 My server.xml context (context for that app) is : Context path= docBase=/home/httpd/html/intranet debug=0 reloadable=true crossContext=true Resources className=org.apache.naming.resources.FileDirContext allowLinking=true/ /Context Any idea ? Thanks Max -Original Message- From: Justin Ruthenbeck [mailto:[EMAIL PROTECTED] Sent: January 6, 2004 3:22 PM To: Tomcat Users List Subject: Re: invoker servlet, tomcat 4.1.29, apache 2.0.48 and connector jk2 Since you're able to hit your servlets through the invoker when pointing to Tomcat directly, this sounds like a connector problem. Check your workers[2].properties to make sure you're passing requests for /servlet through to Apache. justin At 11:47 AM 1/6/2004, you wrote: http://jakarta.apache.org/tomcat/faq/misc.html#invoker -Tim Maxime Pelletier wrote: Hi, We upgraded our tomcat to 4.1.29 and apache to 2.0.48 recently and we have lost access to all servlet invoked in the following form http://address/servlet/MyServlet the apache does no longer pass the request to the tomcat and result in a 404 error (processed by apache). When I use the tomcat only port the servlets are accessibles : http://address:tomcatport/servlet/MyServlet Does anyone have a solution to this ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Justin Ruthenbeck Software Engineer, NextEngine
