If people are having problems getting mod_jk to work there are probably reasons. It may be true that mod_jk works but not always as expected. I have a system that works fine until mod_jk gets involved then java starts barfing up 'exceptions' on a couple of jsp's. Naturally the developers claim, if the code works in 'standalone' but not with mod_jk and virtual domains, the problem is with mod_jk.
On Tuesday 24 June 2003 05:42 am, John Turner wrote: > Donwgrading and using mod_webapp is the WORST thing you could do, for all > sorts of reasons. Security, for one. Performance, for another. Future > extensibility and growth, for another. > > Mod_jk and mod_jk2 work. This is a fact. There's nothing anyone can do if > you want to give up learning how they work and use something else instead, > but the truth is they work, and not just on someone's desktop. Many, many > people are using Tomcat and a connector under heavy load in production on a > daily basis (I'm one of them and there are many more). Load balancing, > multiple instances, all sorts of advanced configurations. If you want to > take the time to learn how things work, and why they work that way (Tomcat > MUST obey the servlet spec, there is no alternative), then you can get your > answers and have a robust, stable system. Its a personal choice. Good > luck. > > John > > On 24 Jun 2003 07:56:47 +0200, Tony Grant <[EMAIL PROTECTED]> wrote: > > >> From my work of yesterday it seems that the easiest way to get a servlet > > to run is to downgrade to Tomcat 4.0.x and use mod_webapp... > > > > This isn't a very encouraging experience. > > > > Cheers > > Tony Grant -- Stephen Carville <[EMAIL PROTECTED]> UNIX and Network Administrator DPSI 6033 W. Century Blvd, Ste 1075 Los Angeles, CA 90045 310-342-3602 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
