Sorry guys, I suspect I'm confusing the issue, but the last post was a clarification, not a solution. I'm still unable to get the root context to register.
Any thoughts? 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: Tref Gare Sent: Tuesday, 29 October 2002 2:42 PM To: Tomcat Users List Subject: RE: tc4.1.12 and Apache2.0.43 mod_jk Root Context not appearing in mod_jk.conf Whoops.. that was meant to read DocumentRoot "/WWW/MySite" For the apache httpd.conf bit Ta ------------------------------------------------------ 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: Tref Gare Sent: Tuesday, 29 October 2002 2:39 PM To: Tomcat Users List 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 To: Tomcat Users List 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>
