context XML file deleted on webapp redeploy
Hi, I am using TomCat 5.5.9 with SUN JDK 1.5.0._02 and I have a strange problem. I have a context file in $CATALINA_BASE/conf/Catalina/localhost/ directory, let's say it is named mywebapp.xml.When I first start TomCat, everything is fine. But when I redeploy the application by overwriting $CATALINA_BAASE/webapps/mywebapp.war with new version, the file $CATALINA_BASE/conf/Catalina/localhost/mywebapp.xml disappears. Is this a feature or a bug ? I never had a problem like this with TomCat 5.0 or 4.1, so I suppose that it is a bug, unless that is a new feature of TomCat 5.5. Martin -- ~~ Supercomputing Center Brno Martin Kuba Institute of Computer Scienceemail: [EMAIL PROTECTED] Masaryk University http://www.ics.muni.cz/~makub/ Botanicka 68a, 60200 Brno, CZ mobil: +420-603-533775 -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Integrating Apache + Tomcat 5 + jk2
Mike Nguyen wrote: Hi, I am trying to integrating Apache + Tomcat5+ jk2 on Solaris 9. Does anyone have an example of jk2.properties and workers2.properties file for this configuration? I appreciate it. Thanks. Mike This information is not sufficient, as you can connect mod_jk2 and Tomact in several ways: TCP sockets, unix sockets and JNI. A basic guide is available in JK documentation: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/confighowto.html I am using TCP sockets (easiest option). I have following in httpd.conf: LoadModule jk2_module libexec/mod_jk2.so IfModule mod_jk2.c JkSet config:file /etc/httpd/workers2.properties /IfModule and following in workers2.properties: [logger.file:] level=DEBUG file=/var/log/httpd/mod_jk2.log [shm:] file=/var/log/httpd/jk2.shm size=100 [channel.socket:localhost:8009] [uri:/mywebapp/*] info=maps mywebapp to default channel I hope this helps ... Martin -- ~~ Supercomputing Center Brno Martin Kuba Institute of Computer Scienceemail: [EMAIL PROTECTED] Masaryk University http://www.ics.muni.cz/~makub/ Botanicka 68a, 60200 Brno, CZ mobil: +420-603-533775 -- smime.p7s Description: S/MIME Cryptographic Signature
Re: Two Tomcats and One Apache Web Server
Walter do Valle wrote: Hello all Is it possible to install two Tomcats in the same linux server, put some web applications in one tomcat, put some web applications in other tomcat and both tomcats answer to the same Apache Web Server? Anyone has made this? Is there any tips and tricks about this matter? What is the best way to do this (if possible)? Sure. Set the TomCats to listen for AJP13 requests on two different ports, say 8009 and 8010 by changing the port number in their conf/server.xml. In the first tomcat, leave this section as it is: Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=0 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ and in the second tomcat, change 8009 to 8010. Then install mod_jk into Apache and define two workers in workers.properties: worker.list=t1,t2 worker.t1.type=ajp13 worker.t1.port=8009 worker.t1.host=localhost worker.t2.type=ajp13 worker.t2.port=8010 worker.t2.host=localhost then map them in httpd.conf: LoadModule jk_module libexec/mod_jk.so JkWorkersFile /etc/httpd/workers.properties JkLogFile /var/log/httpd/mod_jk.log JkLogLevel info JkMount /webapp1/* t1 JkMount /webapp2/* t2 It will route requests for /webapp1 to the first tomcat and requests for /webapp2 to the second tomcat. Martin -- ~~ Supercomputing Center Brno Martin Kuba Institute of Computer Scienceemail: [EMAIL PROTECTED] Masaryk University http://www.ics.muni.cz/~makub/ Botanicka 68a, 60200 Brno, CZ mobil: +420-603-533775 -- smime.p7s Description: S/MIME Cryptographic Signature
Re: Tomcat5.0.16 not reading request attributes from mod_jk
Remy Maucherat wrote: Martin Kuba wrote: Hi, I have a problem getting request attributes (like SSL information and additional CGI variables) in Tomcat5.0.16 connected to Apache using mod_jk/1.2.5 It seems to be some problem with the new Coyote/JK2 AJP 1.3 connector, because it works in Tomcat4.1.29. Please help. I don't know about your problem, but most of the connector code is identical with TC 4.1.29 (in particular, the JK implementation is the same). It cannot be identical, because it produces different results. I finally found what happens. The request attributes *are* available when I specificaly ask for them using request.getAttribute(javax.servlet.request.cipher_suite) request.getAttribute(javax.servlet.request.key_size) request.getAttribute(javax.servlet.request.X509Certificate) request.getAttribute(javax.servlet.request.ssl_session) request.getAttribute(SSL_PROTOCOL) but they are *not* reported by request.getAttributeNames() ! I suppose this is a bug. A side comment - I found that mod_jk is able to send additional CGI variables using JkEnvVar directive, but there is no simmilar setting for mod_jk2. Strange. Martin -- ~~ Supercomputing Center Brno Martin Kuba Institute of Computer Scienceemail: [EMAIL PROTECTED] Masaryk University http://www.ics.muni.cz/~makub/ Botanicka 68a, 60200 Brno, CZ mobil: +420-603-533775 -- smime.p7s Description: S/MIME Cryptographic Signature
Tomcat5.0.16 not reading request attributes from mod_jk
Hi, I have a problem getting request attributes (like SSL information and additional CGI variables) in Tomcat5.0.16 connected to Apache using mod_jk/1.2.5 It seems to be some problem with the new Coyote/JK2 AJP 1.3 connector, because it works in Tomcat4.1.29. Please help. Here are the details: I have it working with Tomcat4.1.29, after some experiments I figured out that in Apache's httpd.conf, I have to set JkMount /myapp/* myworker JkEnvVar SSL_CLIENT_S_DN none Location /myapp/* SSLOptions +ExportCertData +StdEnvVars /Location so that mod_jk extracts the SSL-related information from CGI variables, adds value of CGI variable specified by the JkEnvVar directive and sends the information to TomCat. In Tomcat4.1.29's server.xml I can use both prepared connectors !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=0 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8010 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ to get the information as request attributes, but the older Ajp13Connector is better, because it gets also the SSL_CLIENT_S_DN value, but JkCoyoteHandler does not, it gets only the SSL attributes. But in Tomcat5.0.16, with exactly the same Apache setup and the standard Coyote connector in server.xml: !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- Connector port=8009 enableLookups=false redirectPort=8443 debug=0 protocol=AJP/1.3 / it sets no request attributes at all ! Is it a bug in Tomcat5.0.16's Coyote connector or is something wrong with my configuration ? Martin -- ~~ Supercomputing Center Brno Martin Kuba Institute of Computer Scienceemail: [EMAIL PROTECTED] Masaryk University http://www.ics.muni.cz/~makub/ Botanicka 68a, 60200 Brno, CZ mobil: +420-603-533775 -- smime.p7s Description: S/MIME Cryptographic Signature
Re: FW: java platform
John de la Garza wrote: Does anyone here have experience running java under Solaris on a sparc and Linux on a x86? I am looking to set up a server to run servlets and was wondering which os runs java better. I would assume running Solaris on a sparc would be the best, but I just wanted some feedback. To my experience IBM JDK runs faster than SUN JDK on Linux and there is no IBM JDK for Solaris. See http://www.volano.com/report.html for detailed comparison. Also I have the feeling that my simple PC with Pentium III 500 runs a java application server faster than SUN E250, both with SUN JDK, but I did not any detailed tests to prove it. Martin
