Thanks so much. I'll try it today or tomorrow. Even though you didn't change it, could you please post your jk2.properties? Don't need the httpd.conf- it's pretty straightforward.
Thanks again, allen > -----Original Message----- > From: Phillip Qin [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 27, 2004 10:23 AM > To: 'Tomcat Users List' > Subject: RE: Apache, Tomcat and mod_jk2 - question about layout > > > This is my workers2.properties (not workers.properties). You don't need to > touch jk2.properties or httpd.conf. > > > # shared memory handling. > [shm] > file=C:\Program Files\Apache Group\Tomcat 4.1\work\jk2.shm > size=1048576 > > # Defines a load balancer named lb. Use even if you only have one machine. > #[lb:lb] > > # example socket channel, explicitly set port and host > [channel.socket:localhost:8009] > #tomcatId=localhost:8009 > port=8009 > host=127.0.0.1 > tomcatId=jvm1 > > # define the worker > [ajp13:localhost:8009] > channel=channel.socket:localhost:8009 > #group=lb > > # uri mapping > #[uri:/examples/*] > #group=lb > > [uri:investments.localhost/lciponline/*] > #group=lb > > [uri:test.localhost/onlinestore/*] > #group=lb > > #[uri:/investments/*] > #group=lb > > # ROOT > [uri:investments.localhost/*] > > [uri:test.localhost/*] > > [uri:investments.localhost/manager/*] > #group=lb > > [uri:test.localhost/manager/*] > > [uri:investments.localhost/admin/*] > > [uri:test.localhost/admin/*] > > [status:] > info=Status worker, displays runtime information > > [uri:investments.localhost/jkstatus/*] > #worker=status:status > group=status: > > [uri:test.localhost/jkstatus/*] > #worker=status:status > group=status: > > -----Original Message----- > From: Allen Williams [mailto:[EMAIL PROTECTED] > Sent: October 27, 2004 9:03 AM > To: Tomcat Users List > Subject: RE: Apache, Tomcat and mod_jk2 - question about layout > > > Second request: > > Would you post what you did to integrate the two? I've followed all the > "clues" on both apache and tomcat websites, which is exactly what > it says in > three books I've got, and I still get a "File Not Found" error from apache > when I go to the dynamic content. > > Is there some reference and description of the parameters and > values for the > workers.properties, jk2.properties, and httpd.conf files? Although the > Jakarta website has some of this, the examples showing the > parameters being > used are pretty sparse. What does JkMount do? I can't find this > documented > anywhere. > > I assure you, I've spent DAYS on the websites, in the books, and > looking for > documentation whereever I can find it. > > Thanks, > Allen > > > -----Original Message----- > > From: footh [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, October 26, 2004 10:08 PM > > To: Tomcat Users List > > Subject: Re: Apache, Tomcat and mod_jk2 - question about layout > > > > > > Thanks for the tips. I believe the site will be using > > SSL at some point so that may be a reason to use > > Apache. But for the time being, I suppose I might as > > well use Tomcat standalone knowing that I can just > > "flip a switch" (well, a couple switches) to get > > Apache back in there. > > > > > > --- Peter Johnson <[EMAIL PROTECTED]> wrote: > > > > > I am using Apache2, jk2 and Tomcat5 but I do so > > > because I want to > > > offload the SSL and compression onto a first tier > > > leaving the second > > > just to generate the content. I also use the first > > > tier for uri > > > rewriting using mod_rewrite. > > > > > > If you don't need uri rewriting I would consider > > > using Tomcat standalone > > > as the performance is likely to be comparable but > > > the reduced admin by > > > removing Apache and jk would be a big benefit. Why > > > have more steps that > > > can go wrong? More to debug when it does? > > > > > > To answer the questions from your first email. The > > > images will be being > > > returned from Apache, remember that an image is a > > > separate request. I > > > will qualify this by stating that any dynamically > > > generated images will > > > be returned by Tomcat. > > > > > > Regarding the directory setup ... it is whatever > > > works best for you. I > > > personally do the following: > > > Apache Content -> /sites/static/<site name>/....... > > > Tomcat Content -> /sites/webapps/<site name>/.... > > > > > > This means that all of the Tomcat content is outside > > > the realm of Apache > > > and thus security concerns are reduced. > > > > > > my 2c, > > > > > > PJ > > > > > > footh wrote: > > > > > > >I've read the FAQ on the topic of whether to go > > > >through Apache or just use Tomcat stand-alone and > > > >frankly, it seemed inconclusive. Then I did a > > > search > > > >and it seemed the general consensus was to use > > > Tomcat > > > >stand-alone for development enviroments and Apache > > > for > > > >production. > > > > > > > >Really, that's all I went by. I figured using > > > Apache, > > > >Tomcat and mod_jk was the more robust solution and > > > >better suited for the long haul. More and more > > > >features will likely be added to this site so I > > > need > > > >to be forward thinking. > > > > > > > >--- Parsons Technical Services <[EMAIL PROTECTED]> > > > >wrote: > > > > > > > > > > > > > > > >>Unless you have a reason, why not let Tomcat do it > > > >>all? > > > >> > > > >>Doug > > > >> > > > >>----- Original Message ----- > > > >>From: "footh" <[EMAIL PROTECTED]> > > > >>To: <[EMAIL PROTECTED]> > > > >>Sent: Tuesday, October 26, 2004 5:13 PM > > > >>Subject: Apache, Tomcat and mod_jk2 - question > > > about > > > >>layout > > > >> > > > >> > > > >> > > > >> > > > >>>After going through all the documentation, I have > > > >>>gotten mod_jk2 to forward jsp requests to Tomcat. > > > > > > >>>However, I have a question about the layout... > > > >>> > > > >>>Essentially, my site will be .html pages with > > > some > > > >>>occasional .jsp pages (it will likely change in > > > >>> > > > >>> > > > >>the > > > >> > > > >> > > > >>>future to all .jsp/servlets, but for now that's > > > >>> > > > >>> > > > >>the > > > >> > > > >> > > > >>>way it is). Right now, I have the Apache > > > >>> > > > >>> > > > >>DocumentRoot > > > >> > > > >> > > > >>>pointing to the directory containing the site and > > > >>> > > > >>> > > > >>also > > > >> > > > >> > > > >>>I have a Tomcat Context with a blank path > > > property > > > >>> > > > >>> > > > >>and > > > >> > > > >> > > > >>>docBase property pointing to the same site > > > >>> > > > >>> > > > >>directory. > > > >> > > > >> > > > >>>So, basically, I can browse the site by going to > > > >>>http://localhost:8080 using Tomcat in addition to > > > >>> > > > >>> > > > >>the > > > >> > > > >> > > > >>>standard http://localhost address (through > > > >>> > > > >>> > > > >>Apache). > > > >> > > > >> > > > >>>And, with mod_jk2 working, I can also hit > > > >>>http://localhost/xyz.jsp and have a .jsp page > > > >>> > > > >>> > > > >>execute > > > >> > > > >> > > > >>>correctly. > > > >>> > > > >>>So, my question is, is this the correct way to > > > >>>configure this kind of web site? When .jsp pages > > > >>> > > > >>> > > > >>are > > > >> > > > >> > > > >>>hit, are the images actually being loaded by > > > >>> > > > >>> > > > >>Apache or > > > >> > > > >> > > > >>>by Tomcat? > > > >>> > > > >>>A problem I've discovered is that if I need to > > > use > > > >>> > > > >>> > > > >>a > > > >> > > > >> > > > >>>web.xml file in the WEB-INF directory, I can > > > >>> > > > >>> > > > >>actually > > > >> > > > >> > > > >>>browse to the WEB-INF directory when hitting the > > > >>> > > > >>> > > > >>site > > > >> > > > >> > > > >>>through port 80 (Apache). Obviously, this is not > > > >>> > > > >>> > > > >>a > > > >> > > > >> > > > >>>good idea so I am thinking there is probably a > > > >>> > > > >>> > > > >>better > > > >> > > > >> > > > >>>way to set this site up. Any ideas? > > > >>> > > > >>>Thanks, > > > >>> > > > >>>JF > > > >>> > > > >>> > > > >>> > > > >>> > > > >>> > > > > > === message truncated === > > > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam protection around > > http://mail.yahoo.com > > > > --------------------------------------------------------------------- > > 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] > > > !DSPAM:417f9c45155311021598181! > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
