Thanks Robert and Bill, I've got the system working now using direct additions to httdp.conf (basically a cut and paste of the auto generated file mod_jk.conf with additions). I haven't yet had a chance to experiment with the noRoot="false" though that sounds very much like the sort of attribute that might have been tripping us up. The thing that was refusing to work for me was the Aliasing of the root context. Now that I've stopped trying to alias it and instead am just referring JkMounts to ajp13 and pointing Apache at the same root as tomcat all seems to be well.
I can appreciate the convenience of configuring things from one location and as such, perhaps what I should be doing is using the Include directive in the httpd.conf and configuring a static copy of mod_jk.conf (ie: one that doesn't get overwritten with each startup of Tomcat) for the aliases etc. Either way I'm still editing two files, either server.xml and mod_jk.conf and or httpd.conf and server.xml Many thanks for your various assistances thus far. You're champions. Tref ------------------------------------------------------ Tref Gare Development Consultant Areeba Level 19/114 William St, Melbourne VIC 3000 email: [EMAIL PROTECTED] phone: +61 3 9642 5553 fax: +61 3 9642 1335 website: http://www.areeba.com.au ------------------------------------------------------ "This email is intended only for the use of the individual or entity named above and contains information that is confidential. No confidentiality is waived or lost by any mis-transmission. If you received this correspondence in error, please notify the sender and immediately delete it from your system. You must not disclose, copy or rely on any part of this correspondence if you are not the intended recipient. Any communication directed to clients via this message is subject to our Agreement and relevant Project Schedule. Any information that is transmitted via email which may offend may have been sent without knowledge or the consent of Areeba." ------------------------------------------------------ -----Original Message----- From: Robert L Sowders [mailto:rsowders@;usgs.gov] Sent: Wednesday, 30 October 2002 8:03 PM To: Tomcat Users List Subject: Re: tc4.1.12 and Apache2.0.43 mod_jk Root Context not appearing in mod_jk.conf Oops, cat short_term_memory | /dev/null I'm glad I could help you at least once then, It's been awhile since I've been down with JK mind you, been tracking JK2 while others here have maintained JK systems. If you know the correct syntax for your jkmounts and such and make your own edits to server.xml, there really is no reason to use the generated mod_jk.conf. A judicious use of Apache DocumentRoot and webapp co-mingling, together with JkAutoAlias, sprinkled with a dash of auto generated mod_jk.conf can lead to allot less configuration for admins. Especially on sites with a lot of virtual hosts. I guess the difference is the same as cmd line unix and windows gui. I've often wondered why windows users put up with having to click thru 15 different windows to get to a button that changes one line in a file they just as easily could have directly edited. For single user installations, it's not really needed, but it's cool none-the-less. I believe if you make your own contexts in server.xml outside of the ROOT then your auto generated mod_jk.conf will contain the new Jkmounts. I'll send you a txt file off list that details a web hosting setup that makes it easy without auto generated mod_jk.conf. rls "Bill Barker" <[EMAIL PROTECTED]> Sent by: news <[EMAIL PROTECTED]> 10/29/2002 11:07 PM Please respond to "Tomcat Users List" To: [EMAIL PROTECTED] cc: Subject: Re: tc4.1.12 and Apache2.0.43 mod_jk Root Context not appearing in mod_jk.conf You also need to set the noRoot="false" attribute in the Listener. It defaults to "true", since otherwise (if the default forwardAll="true"), all requests get sent to Tomcat. "Tref Gare" <[EMAIL PROTECTED]> wrote in message news:D9E0834F4E6DA84C8F8F421EDA28E84106A63F@;proxy.areeba.com.au... Thanks Robert, You actually helped me out last week with the same howto.. however in this case we're a step past that. I've got the listeners set up as per the howto and they're doing fine when it comes to setting up the examples context, however they don't seem to want to have anything to do with the root context. I was wondering briefly if this has something to do with the invoker servlet (disabled by default in tomcat 4.1.12) but I'm only trying to reach .jsp's at the moment not /servlet/MyServlet etc. On the topic can you enlighten me at all as to what's the advantage (aside from ease of use) of using the auto generated files as compared to manually created ones (ie: taking the params in mod_jk.conf and copying/tweaking them in httpd.conf direct). I'm going to have some non vanilla mappings (*.form for example) that I imagine might not be able to be configured via the auto generated file. Tref ------------------------------------------------------ Tref Gare Development Consultant Areeba Level 19/114 William St, Melbourne VIC 3000 email: [EMAIL PROTECTED] phone: +61 3 9642 5553 fax: +61 3 9642 1335 website: http://www.areeba.com.au ------------------------------------------------------ "This email is intended only for the use of the individual or entity named above and contains information that is confidential. No confidentiality is waived or lost by any mis-transmission. If you received this correspondence in error, please notify the sender and immediately delete it from your system. You must not disclose, copy or rely on any part of this correspondence if you are not the intended recipient. Any communication directed to clients via this message is subject to our Agreement and relevant Project Schedule. Any information that is transmitted via email which may offend may have been sent without knowledge or the consent of Areeba." ------------------------------------------------------ -----Original Message----- From: Robert L Sowders [mailto:rsowders@;usgs.gov] Sent: Tuesday, 29 October 2002 7:52 PM Subject: Re: tc4.1.12 and Apache2.0.43 mod_jk Root Context not appearing in mod_jk.conf You will need to setup a listener in server.xml and then the Include in your httpd.conf will be something like "Include /usr/local/tomcat/conf/auto/mod_jk.conf" Here is a How To that I refer to from time to time. http://www.johnturner.com/howto/apache2-tomcat4110-jk-howto.html The part you want is at step 3. rls "Tref Gare" <[EMAIL PROTECTED]> 10/28/2002 07:39 PM Please respond to "Tomcat Users List" To: "Tomcat Users List" <[EMAIL PROTECTED]> cc: Subject: tc4.1.12 and Apache2.0.43 mod_jk Root Context not appearing in mod_jk.conf Hi All, Any help much appreciated. We've got a tomcat 4.1.12 and Apache 2.0.43 connected up using mod_jk and I'm having grief getting the root context to register in mod_jk.conf. I had thought that any contexts defined in Tomcat would be automatically setup in mod_jk.conf, is there a secret I'm unaware of? I've got both docBase and appBase settings set to the same location which is also the root context. Eg: Tomcat thinks it's docBase is /WWW/MySite Apache thinks it's DocumentRoot is /WWW/MySite Tomcat has currently only two contexts setup /examples which has been moved to /WWW/MySite/examples <Context path="/examples" docBase="examples" debug="0" reloadable="true" crossContext="true"> This one works fine in both Tomcat standalone and via Apache However the root context is setup as follows <Context path="" docBase="/WWW/MySite" debug="0"/> and just refuses to register in mod_jk.conf, leaving all jsps displaying as pure source and WEB-INF etc wide open to the world. I'm swimming here.. any suggestions? Thanks ------------------------------------------------------ Tref Gare Development Consultant Areeba Level 19/114 William St, Melbourne VIC 3000 email: [EMAIL PROTECTED] phone: +61 3 9642 5553 fax: +61 3 9642 1335 website: http://www.areeba.com.au ------------------------------------------------------ "This email is intended only for the use of the individual or entity named above and contains information that is confidential. No confidentiality is waived or lost by any mis-transmission. If you received this correspondence in error, please notify the sender and immediately delete it from your system. You must not disclose, copy or rely on any part of this correspondence if you are not the intended recipient. Any communication directed to clients via this message is subject to our Agreement and relevant Project Schedule. Any information that is transmitted via email which may offend may have been sent without knowledge or the consent of Areeba." ------------------------------------------------------ -----Original Message----- From: William Lee [mailto:wlee@;sendmail.com] Sent: Tuesday, 29 October 2002 1:25 PM Subject: Re: Tomcat 4.1.12 hanging under stress? Ben Ricker wrote: > On Mon, 2002-10-28 at 14:38, William Lee wrote: > >>I'm running a Tomcat 4.1.12 (with the coyote connectors running SSL) on >>RH Linux with a 2.4.9 kernel and IBM JRE 1.3.1 build cxia32131-20020622. > > > I am wondering about the kernel version here; you have rather old > kernel, a version which is considered unstable. I would suggest > upgrading the kernel, especially since you have SMP. > > This is just a small suggestion.....anything in the logs? > > Ben Ricker > Wellin.com Hmm, it may have something to do with the kernel, I'll try later to see whether this is the case. I don't think the log gives me much though. Anyhow, I've made a weird discovery that I found interesting. It seems like there's a "barrier" when the JVM consume around 90MB of RAM. Once the JVM got over that barrier, then things will keep working. The strange thing is, under not-so-heavy load (< 30 concurrent users), somehow it failed to break that barrier and the socket hung when it reaches that point. If I drive the load up ( 50, 100, or even 200 concurrent connections), somehow it breaks that barrier and things will work without any problem. Does anyone know why this is the case? -- William Lee (Will) | Sendmail Inc. Email: [EMAIL PROTECTED] | http://www.sendmail.com Tel: (510) 594-5505 | -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
