RE: cannot get servlet mapping working under 3.3
You might try adding the JservConfig ... element to your server.xml, documented here: http://jakarta.apache.org/tomcat/tomcat-3.3-doc/serverxml.html#JservConfig You will likely need a current version of the mod_jserv connector. The Windows binary can be found here: http://archive.apache.org/dist/jakarta/tomcat-3/bin/win32/i386/ For a different OS, you will have to build it. The bulk of the information for mod_jserv may be found here: http://jakarta.apache.org/tomcat/tomcat-3.3-doc/tomcat-apache-howto.html It has been a long time since I did much with mod_jserv, and then, only on Windows. HTH. Cheers, Larry -Original Message- From: Christoph P. Kukulies [mailto:[EMAIL PROTECTED] Sent: Monday, April 05, 2004 11:19 AM To: Tomcat Users List Subject: Re: cannot get servlet mapping working under 3.3 On Mon, Apr 05, 2004 at 11:41:56AM +0200, Christoph P. Kukulies wrote: Investigating further I come to the conclusion that my problem may be related to the invoker servlet. Doesn't tomcat 3.3 have a central web.xml any longer? Sorry, I know that talking about tomcat 5.x is more interesting than talking about yesterdays. :-) Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de Could it be that I need mod_jserv.so from the tomcat native directory? How does one build that? Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de - 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: cannot get servlet mapping working under 3.3
On Sun, Apr 04, 2004 at 10:04:12PM +0200, Schalk wrote: I would suggest you upgrade to Tomcat 5.0+ and mod_jk Yes, I could but then I have another Servlet API and other headaches with my classes possibly not working any longer or having deprecated APIs. Nobody here who can tell what the problem is with 3.3 and apache in my case? I'm very close to have them both running. Just a little piece seems to be missing. How can I verify the apache tomcat connector is working? Were there problems with aliasing/mapping? Can only believe that I'm missing something in server.xml or httpd.conf/jserv.conf. Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de :: Subject: cannot get servlet mapping working under 3.3 :: :: I'm reconvalescing from a disc crash where lots of my existing :: tomcat 3.1/apache 1.3.26 installation had crashed and I :: reinstalled tomcat 3.3 with apache-1.3.27 now such that :: the examples work when I connect to the server at port 8080. :: But this is tomcat. Trying to connect to apache via the jserv :: modules doesn't seem to work. :: :: logs/stderr.log looks ok. :: :: I have included apache/jserv/jserv.conf at the end of httpd.conf :: :: :: jserv.conf: :: :: ### :: :: :: ### :: :: # Note: this file should be appended or included into your httpd.conf :: :: # Tell Apache on win32 to load the Apache JServ communication module :: #LoadModule jserv_module modules/ApacheModuleJServ.dll :: :: # Tell Apache on Unix to load the Apache JServ communication module :: # For shared object builds only!!! :: LoadModule jserv_module /usr/local/libexec/apache/mod_jserv.so :: :: IfModule mod_jserv.c :: :: # Whether Apache must start Apache JServ or not (On=Manual Off=Autostart) :: # Syntax: ApJServManual [on/off] :: # Default: Off :: ApJServManual Off :: :: # Properties filename for Apache JServ in Automatic Mode. :: # In manual mode this directive is ignored :: # Syntax: ApJServProperties [filename] :: # Default: ./conf/jserv.properties :: ApJServProperties /usr/local/etc/apache/jserv/jserv.properties :: :: # Log file for this module operation relative to Apache root directory. :: # Set the name of the trace/log file. To avoid possible confusion about :: # the location of this file, an absolute pathname is recommended. :: # :: # This log file is different than the log file that is in the :: # jserv.properties file. This is the log file for the C portion of Apache :: # JServ. :: # :: # On Unix, this file must have write permissions by the owner of the JVM :: # process. In other words, if you are running Apache JServ in manual mode :: # and Apache is running as user nobody, then the file must have its :: # permissions set so that that user can write to it. :: # Syntax: ApJServLogFile [filename] :: # Default: ./logs/mod_jserv.log :: # Note: when set to DISABLED, the log will be redirected to Apache error log :: ApJServLogFile /var/log/mod_jserv.log :: :: # Log Level for this module :: # Syntax: ApJServLogLevel [debug|info|notice|warn|error|crit|alert|emerg] :: # Default: info(unless compiled w/ JSERV_DEBUG, in which case it's debug) :: ApJServLogLevel debug :: :: # Protocol used by this host to connect to Apache JServ :: # (see documentation for more details on available protocols) :: # Syntax: ApJServDefaultProtocol [name] :: # Default: ajpv12 :: ApJServDefaultProtocol ajpv12 :: :: # Default host on which Apache JServ is running :: # Syntax: ApJServDefaultHost [hostname] :: # Default: localhost :: #ApJServDefaultHost java.apache.org :: :: # Default port that Apache JServ is listening to :: # Syntax: ApJServDefaultPort [number] :: # Default: protocol-dependant (for ajpv12 protocol this is 8007) :: ApJServDefaultPort 8007 :: :: # The amount of time to give to the JVM to start up as well :: # as the amount of time to wait to ping the JVM to see if it :: # is alive. Slow or heavily loaded machines might want to :: # increase this value. :: # Default: 10 seconds :: # ApJServVMTimeout 10 :: :: # Passes parameter and value to specified protocol. :: # Syntax: ApJServProtocolParameter [name] [parameter] [value] :: # Default: NONE :: # Note: Currently no protocols handle this. Introduced for future protocols. :: :: # Apache JServ secret key file relative to Apache root directory. :: # Syntax: ApJServSecretKey [filename] :: # Default: ./conf/jserv.secret.key :: # Warning: if authentication is DISABLED, everyone on this machine (not just :: # this module) may connect to your servlet engine and execute servlet :: # bypassing web server restrictions. See the documentation for more information :: #ApJServSecretKey /usr/local/etc/apache/jserv/jserv.secret.key :: ApJServSecretKey DISABLED :: :: # Mount point for Servlet zones
Re: cannot get servlet mapping working under 3.3
I found the following in tomcat.conf in the 3.3 distribution: ## Context mapping - you need to deploy # ( copy or ln -s ) the context into htdocs ## # ApJservMount /CONTEXT/servlet /root # Location /CONTEXT/WEB-INF/ # AllowOverride None # deny from all # /Location What would that mean? Do I have to ln -s /usr/local/jakarta-tomcat3.3/webapps/servlets /usr/local/www/data (or whatever the document root is)? I found a /usr/local/www/servlets in the directory of my crshaed disk but cannot determin any longer whether this is a soft link, a directory or whatever or if this is only a relict of some experimenting. -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cannot get servlet mapping working under 3.3
Investigating further I come to the conclusion that my problem may be related to the invoker servlet. Doesn't tomcat 3.3 have a central web.xml any longer? Sorry, I know that talking about tomcat 5.x is more interesting than talking about yesterdays. :-) Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de On Mon, Apr 05, 2004 at 10:28:28AM +0200, Christoph P. Kukulies wrote: I found the following in tomcat.conf in the 3.3 distribution: ## Context mapping - you need to deploy # ( copy or ln -s ) the context into htdocs ## # ApJservMount /CONTEXT/servlet /root # Location /CONTEXT/WEB-INF/ # AllowOverride None # deny from all # /Location What would that mean? Do I have to ln -s /usr/local/jakarta-tomcat3.3/webapps/servlets /usr/local/www/data (or whatever the document root is)? I found a /usr/local/www/servlets in the directory of my crshaed disk but cannot determin any longer whether this is a soft link, a directory or whatever or if this is only a relict of some experimenting. -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cannot get servlet mapping working under 3.3
On Mon, Apr 05, 2004 at 11:41:56AM +0200, Christoph P. Kukulies wrote: Investigating further I come to the conclusion that my problem may be related to the invoker servlet. Doesn't tomcat 3.3 have a central web.xml any longer? Sorry, I know that talking about tomcat 5.x is more interesting than talking about yesterdays. :-) Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de Could it be that I need mod_jserv.so from the tomcat native directory? How does one build that? Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cannot get servlet mapping working under 3.3
I'm reconvalescing from a disc crash where lots of my existing tomcat 3.1/apache 1.3.26 installation had crashed and I reinstalled tomcat 3.3 with apache-1.3.27 now such that the examples work when I connect to the server at port 8080. But this is tomcat. Trying to connect to apache via the jserv modules doesn't seem to work. logs/stderr.log looks ok. I have included apache/jserv/jserv.conf at the end of httpd.conf jserv.conf: ### ### # Note: this file should be appended or included into your httpd.conf # Tell Apache on win32 to load the Apache JServ communication module #LoadModule jserv_module modules/ApacheModuleJServ.dll # Tell Apache on Unix to load the Apache JServ communication module # For shared object builds only!!! LoadModule jserv_module /usr/local/libexec/apache/mod_jserv.so IfModule mod_jserv.c # Whether Apache must start Apache JServ or not (On=Manual Off=Autostart) # Syntax: ApJServManual [on/off] # Default: Off ApJServManual Off # Properties filename for Apache JServ in Automatic Mode. # In manual mode this directive is ignored # Syntax: ApJServProperties [filename] # Default: ./conf/jserv.properties ApJServProperties /usr/local/etc/apache/jserv/jserv.properties # Log file for this module operation relative to Apache root directory. # Set the name of the trace/log file. To avoid possible confusion about # the location of this file, an absolute pathname is recommended. # # This log file is different than the log file that is in the # jserv.properties file. This is the log file for the C portion of Apache # JServ. # # On Unix, this file must have write permissions by the owner of the JVM # process. In other words, if you are running Apache JServ in manual mode # and Apache is running as user nobody, then the file must have its # permissions set so that that user can write to it. # Syntax: ApJServLogFile [filename] # Default: ./logs/mod_jserv.log # Note: when set to DISABLED, the log will be redirected to Apache error log ApJServLogFile /var/log/mod_jserv.log # Log Level for this module # Syntax: ApJServLogLevel [debug|info|notice|warn|error|crit|alert|emerg] # Default: info(unless compiled w/ JSERV_DEBUG, in which case it's debug) ApJServLogLevel debug # Protocol used by this host to connect to Apache JServ # (see documentation for more details on available protocols) # Syntax: ApJServDefaultProtocol [name] # Default: ajpv12 ApJServDefaultProtocol ajpv12 # Default host on which Apache JServ is running # Syntax: ApJServDefaultHost [hostname] # Default: localhost #ApJServDefaultHost java.apache.org # Default port that Apache JServ is listening to # Syntax: ApJServDefaultPort [number] # Default: protocol-dependant (for ajpv12 protocol this is 8007) ApJServDefaultPort 8007 # The amount of time to give to the JVM to start up as well # as the amount of time to wait to ping the JVM to see if it # is alive. Slow or heavily loaded machines might want to # increase this value. # Default: 10 seconds # ApJServVMTimeout 10 # Passes parameter and value to specified protocol. # Syntax: ApJServProtocolParameter [name] [parameter] [value] # Default: NONE # Note: Currently no protocols handle this. Introduced for future protocols. # Apache JServ secret key file relative to Apache root directory. # Syntax: ApJServSecretKey [filename] # Default: ./conf/jserv.secret.key # Warning: if authentication is DISABLED, everyone on this machine (not just # this module) may connect to your servlet engine and execute servlet # bypassing web server restrictions. See the documentation for more information #ApJServSecretKey /usr/local/etc/apache/jserv/jserv.secret.key ApJServSecretKey DISABLED # Mount point for Servlet zones # (see documentation for more information on servlet zones) # Syntax: ApJServMount [name] [jserv-url] # Default: NONE # Note: [name] is the name of the Apache URI path to mount jserv-url on # [jserv-url] is something like protocol://host:port/zone # If protocol, host or port are not specified, the values from # ApJServDefaultProtocol, ApJServDefaultHost or ApJServDefaultPort # will be used. # If zone is not specified, the zone name will be the first subdirectory of # the called servlet. # Example: ApJServMount /servlets /myServlets # if user requests http://host/servlets/TestServlet; # the servlet TestServlet in zone myServlets on default host # thru default protocol on defaul port will be requested # Example: ApJServMount /servlets ajpv12://localhost:8007 # if user requests http://host/servlets/myServlets/TestServlet; # the servlet TestServlet in zone myServlets will be requested # Example: ApJServMount /servlets ajpv12://jserv.mydomain.com:15643/myServlets # if user requests http://host/servlets/TestServlet; the servlet # TestServlet in zone myServlets on host jserv.mydomain.com using # ajpv12
RE: cannot get servlet mapping working under 3.3
I would suggest you upgrade to Tomcat 5.0+ and mod_jk Kind Regards Schalk Neethling Web Developer.Designer.Programmer.President Volume4.Development.Multimedia.Branding emotionalize.conceptualize.visualize.realize Tel: +27125468436 Fax: +27125468436 email:[EMAIL PROTECTED] web: www.volume4.com This message contains information that is considered to be sensitive or confidential and may not be forwarded or disclosed to any other party without the permission of the sender. If you received this message in error, please notify me immediately so that I can correct and delete the original email. Thank you. :: -Original Message- :: From: C. Kukulies [mailto:[EMAIL PROTECTED] :: Sent: Sunday, April 04, 2004 9:55 PM :: To: [EMAIL PROTECTED] :: Subject: cannot get servlet mapping working under 3.3 :: :: I'm reconvalescing from a disc crash where lots of my existing :: tomcat 3.1/apache 1.3.26 installation had crashed and I :: reinstalled tomcat 3.3 with apache-1.3.27 now such that :: the examples work when I connect to the server at port 8080. :: But this is tomcat. Trying to connect to apache via the jserv :: modules doesn't seem to work. :: :: logs/stderr.log looks ok. :: :: I have included apache/jserv/jserv.conf at the end of httpd.conf :: :: :: jserv.conf: :: :: ### :: :: :: ### :: :: # Note: this file should be appended or included into your httpd.conf :: :: # Tell Apache on win32 to load the Apache JServ communication module :: #LoadModule jserv_module modules/ApacheModuleJServ.dll :: :: # Tell Apache on Unix to load the Apache JServ communication module :: # For shared object builds only!!! :: LoadModule jserv_module /usr/local/libexec/apache/mod_jserv.so :: :: IfModule mod_jserv.c :: :: # Whether Apache must start Apache JServ or not (On=Manual Off=Autostart) :: # Syntax: ApJServManual [on/off] :: # Default: Off :: ApJServManual Off :: :: # Properties filename for Apache JServ in Automatic Mode. :: # In manual mode this directive is ignored :: # Syntax: ApJServProperties [filename] :: # Default: ./conf/jserv.properties :: ApJServProperties /usr/local/etc/apache/jserv/jserv.properties :: :: # Log file for this module operation relative to Apache root directory. :: # Set the name of the trace/log file. To avoid possible confusion about :: # the location of this file, an absolute pathname is recommended. :: # :: # This log file is different than the log file that is in the :: # jserv.properties file. This is the log file for the C portion of Apache :: # JServ. :: # :: # On Unix, this file must have write permissions by the owner of the JVM :: # process. In other words, if you are running Apache JServ in manual mode :: # and Apache is running as user nobody, then the file must have its :: # permissions set so that that user can write to it. :: # Syntax: ApJServLogFile [filename] :: # Default: ./logs/mod_jserv.log :: # Note: when set to DISABLED, the log will be redirected to Apache error log :: ApJServLogFile /var/log/mod_jserv.log :: :: # Log Level for this module :: # Syntax: ApJServLogLevel [debug|info|notice|warn|error|crit|alert|emerg] :: # Default: info(unless compiled w/ JSERV_DEBUG, in which case it's debug) :: ApJServLogLevel debug :: :: # Protocol used by this host to connect to Apache JServ :: # (see documentation for more details on available protocols) :: # Syntax: ApJServDefaultProtocol [name] :: # Default: ajpv12 :: ApJServDefaultProtocol ajpv12 :: :: # Default host on which Apache JServ is running :: # Syntax: ApJServDefaultHost [hostname] :: # Default: localhost :: #ApJServDefaultHost java.apache.org :: :: # Default port that Apache JServ is listening to :: # Syntax: ApJServDefaultPort [number] :: # Default: protocol-dependant (for ajpv12 protocol this is 8007) :: ApJServDefaultPort 8007 :: :: # The amount of time to give to the JVM to start up as well :: # as the amount of time to wait to ping the JVM to see if it :: # is alive. Slow or heavily loaded machines might want to :: # increase this value. :: # Default: 10 seconds :: # ApJServVMTimeout 10 :: :: # Passes parameter and value to specified protocol. :: # Syntax: ApJServProtocolParameter [name] [parameter] [value] :: # Default: NONE :: # Note: Currently no protocols handle this. Introduced for future protocols. :: :: # Apache JServ secret key file relative to Apache root directory. :: # Syntax: ApJServSecretKey [filename] :: # Default: ./conf/jserv.secret.key :: # Warning: if authentication is DISABLED, everyone on this machine (not just :: # this module) may connect to your servlet engine and execute servlet :: # bypassing web server restrictions. See the documentation for more information :: #ApJServSecretKey /usr/local/etc/apache/jserv/jserv.secret.key :: ApJServSecretKey DISABLED :: :: # Mount point for Servlet zones :: # (see documentation
RE: cannot get servlet mapping working under 3.3
As far as I know Jserv has been deprecated or is no longer in development and has migrated over to mod_jk, open to correction though. Kind Regards Schalk Neethling Web Developer.Designer.Programmer.President Volume4.Development.Multimedia.Branding emotionalize.conceptualize.visualize.realize Tel: +27125468436 Fax: +27125468436 email:[EMAIL PROTECTED] web: www.volume4.com This message contains information that is considered to be sensitive or confidential and may not be forwarded or disclosed to any other party without the permission of the sender. If you received this message in error, please notify me immediately so that I can correct and delete the original email. Thank you. :: -Original Message- :: From: Schalk [mailto:[EMAIL PROTECTED] :: Sent: Sunday, April 04, 2004 10:04 PM :: To: 'Tomcat Users List' :: Subject: RE: cannot get servlet mapping working under 3.3 :: :: I would suggest you upgrade to Tomcat 5.0+ and mod_jk :: :: Kind Regards :: Schalk Neethling :: Web Developer.Designer.Programmer.President :: Volume4.Development.Multimedia.Branding :: emotionalize.conceptualize.visualize.realize :: Tel: +27125468436 :: Fax: +27125468436 :: email:[EMAIL PROTECTED] :: web: www.volume4.com :: :: This message contains information that is considered to be sensitive or :: confidential and may not be forwarded or disclosed to any other party :: without the permission of the sender. If you received this message in error, :: please notify me immediately so that I can correct and delete the original :: email. Thank you. :: :: :: -Original Message- :: :: From: C. Kukulies [mailto:[EMAIL PROTECTED] :: :: Sent: Sunday, April 04, 2004 9:55 PM :: :: To: [EMAIL PROTECTED] :: :: Subject: cannot get servlet mapping working under 3.3 :: :: :: :: I'm reconvalescing from a disc crash where lots of my existing :: :: tomcat 3.1/apache 1.3.26 installation had crashed and I :: :: reinstalled tomcat 3.3 with apache-1.3.27 now such that :: :: the examples work when I connect to the server at port 8080. :: :: But this is tomcat. Trying to connect to apache via the jserv :: :: modules doesn't seem to work. :: :: :: :: logs/stderr.log looks ok. :: :: :: :: I have included apache/jserv/jserv.conf at the end of httpd.conf :: :: :: :: :: :: jserv.conf: :: :: :: :: :: ### :: :: :: :: :: :: :: ### :: :: :: :: # Note: this file should be appended or included into your httpd.conf :: :: :: :: # Tell Apache on win32 to load the Apache JServ communication module :: :: #LoadModule jserv_module modules/ApacheModuleJServ.dll :: :: :: :: # Tell Apache on Unix to load the Apache JServ communication module :: :: # For shared object builds only!!! :: :: LoadModule jserv_module /usr/local/libexec/apache/mod_jserv.so :: :: :: :: IfModule mod_jserv.c :: :: :: :: # Whether Apache must start Apache JServ or not (On=Manual Off=Autostart) :: :: # Syntax: ApJServManual [on/off] :: :: # Default: Off :: :: ApJServManual Off :: :: :: :: # Properties filename for Apache JServ in Automatic Mode. :: :: # In manual mode this directive is ignored :: :: # Syntax: ApJServProperties [filename] :: :: # Default: ./conf/jserv.properties :: :: ApJServProperties /usr/local/etc/apache/jserv/jserv.properties :: :: :: :: # Log file for this module operation relative to Apache root directory. :: :: # Set the name of the trace/log file. To avoid possible confusion about :: :: # the location of this file, an absolute pathname is recommended. :: :: # :: :: # This log file is different than the log file that is in the :: :: # jserv.properties file. This is the log file for the C portion of Apache :: :: # JServ. :: :: # :: :: # On Unix, this file must have write permissions by the owner of the JVM :: :: # process. In other words, if you are running Apache JServ in manual mode :: :: # and Apache is running as user nobody, then the file must have its :: :: # permissions set so that that user can write to it. :: :: # Syntax: ApJServLogFile [filename] :: :: # Default: ./logs/mod_jserv.log :: :: # Note: when set to DISABLED, the log will be redirected to Apache :: error log :: :: ApJServLogFile /var/log/mod_jserv.log :: :: :: :: # Log Level for this module :: :: # Syntax: ApJServLogLevel [debug|info|notice|warn|error|crit|alert|emerg] :: :: # Default: info(unless compiled w/ JSERV_DEBUG, in which case it's :: debug) :: :: ApJServLogLevel debug :: :: :: :: # Protocol used by this host to connect to Apache JServ :: :: # (see documentation for more details on available protocols) :: :: # Syntax: ApJServDefaultProtocol [name] :: :: # Default: ajpv12 :: :: ApJServDefaultProtocol ajpv12 :: :: :: :: # Default host on which Apache JServ is running :: :: # Syntax: ApJServDefaultHost [hostname] :: :: # Default: localhost :: :: #ApJServDefaultHost java.apache.org :: :: :: :: # Default port that Apache JServ
