Jk vs jk2. JK is dead STOP USING IT. JK2 all the way!! (sorry, jk2 is the prefered way to link apache2 to tomcat[45])
I would suggest using tomcat 4 for now if you are going immediately into a production environment where you have to abide by a server level agreement. Otherwise use tomcat 5. Tomcat 5 is listed as stable but seems a bit shakey right now with the bugs that keep popping up. There is no reason that I know of not to use Apache2. You will be using worker2.properties. Since I know nothing about JK I can't comment on the rest. > -----Original Message----- > From: C. Kukulies [mailto:[EMAIL PROTECTED] > Sent: Monday, April 19, 2004 5:33 PM > To: [EMAIL PROTECTED] > Subject: the pain of choice > > > Can someone give me an advice which way to go WRT to using a > tomcat/apache combo on a Unix (not Linux) system? > > There are so many options, jk, jk2, tomcat 3-4-5, apache 1.3, apache2. > worker.properties worker2.properties, jk2.properties in tomcat/conf, > mod_jk.conf in etc/apache, mod_jk, mod_jk2. > > Then I see constructs in brackets [] in worker.properties and > without these. > What is workers.host=jsp-hostname? Is it an IP host? Or is it > some placeholder > which must be in workers.list? > > > -- > 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]
