Which direction: mod_jk or mod_proxy_ajp? (was: why use mod_jk?)
I suppose this question deserved its own thread. Before I spend any more time trying to get this configured, I would like to know what is the best way to proceed: mod_jk or mod_proxy_ajp? Thanks, Brad On Feb 24, 2006, at 7:49 AM, Brad O'Hearne wrote: Jess, Thanks for the reply. Responses below: On Feb 24, 2006, at 6:51 AM, Jess Holle wrote: If you're using Apache 1.3.x or 2.0.x, mod_jk is pretty simple overall. No, you don't want to even try in-process stuff and, yes, if you have a firewall in between Apache and Tomcat that drops idle connections you should read carefully (this is covered by the docs). The only big complaint I have is that the mod_jk docs don't make it terribly clear (or didn't last I checked) exactly how to set jvmRoute in Tomcat and how extraordinarily critical this is when doing load balancing. The Tomcat docs don't make this terribly clear either -- apart from a comment in server.xml. Most everyone I know who tries mod_jk load balancing gets hung up on this one point unless/until I give them a detailed explanation. Apart from the lack of clear/obvious information on this in the mod_jk docs (which should include it considering most folk won't think to check both mod_jk and Tomcat docs), this is actually very simple as well, though. None of the configuration steps in and of itself are difficult. Building mod_jk is not difficult. Editing configuration files is not difficult. Its after you've put it all together, exactly as noted on a hodge-podge of Googled URLs, and it doesn't work, and one cryptic line in a log file, and the right connections not being made between apache and tomcat, which send you into hours of trial and error. With regards to your comments above, I didn't tangle with load balancing at all, and apache and tomcat reside on the same box, no firewall between them. Yes, you'd think this would be simple. I am looking forward to mod_proxy_ajp as it is supposed be a tiny bit faster. You say you are "looking forward to mod_proxy_ajp" -- does this mean its not available yet, or you just aren't using it yet? While I am glad to learn now of mod_proxy_ajp, I guess this kind of adds to my frustration a bit -- what is the way to go now and why: mod_proxy_ajp or mod_jk? Thanks for your help. Brad -- Jess Holle Brad O'Hearne wrote: mod_proxy_ajp? Yet another twist. Its just hard for me to believe that "how do I integrate tomcat and apache httpd?" is such a mystery / unknown. This seems like it would be question #1 on any Tomcat FAQ. So where can I found out more about mod_proxy_ajp. Is there a Tomcat resource which explains the configuration of it? Brad Bill Barker wrote: "Brad O'Hearne" <[EMAIL PROTECTED]> wrote in message news: [EMAIL PROTECTED] After wasting time trying to configure mod_jk, I thought I'd just wipe my mind free and just play dumb for a moment. If Apache can proxy requests using mod_proxy, what is the benefit of using mod_jk as an integration technique between httpd and tomcat, if integration is *not* in-process, which I understand is not recommended for Tomcat 5.5? Actually, in-process with mod_jk is only supported (and, I use the term lightly :) for TC 3.3.x. For any higher versions it doesn't work at all. You've managed to grasp the deep, dark plan of the Tomcat developers: It is expected that people will migrate to mod_proxy_ajp with Httpd 2.2+, and mod_jk is expected to move to supporting IIS/SunOne only (and, the later only if somebody steps up with interest :). Brad --- -- 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Which direction: mod_jk or mod_proxy_ajp? (was: why use mod_jk?)
That depends if you want to use Apache 2.0.x, Apache 2.2.x, or some other web server (i.e. IIS). If you're planning on using Apache 2.2.x, mod_proxy_ajp is the way to go. For anything else, mod_jk is the way to go. , Josh. > -Original Message- > From: Brad O'Hearne [mailto:[EMAIL PROTECTED] > Sent: Friday, February 24, 2006 9:02 AM > To: Tomcat Users List > Subject: Which direction: mod_jk or mod_proxy_ajp? (was: why > use mod_jk?) > > > I suppose this question deserved its own thread. Before I spend any > more time trying to get this configured, I would like to know > what is > the best way to proceed: mod_jk or mod_proxy_ajp? > > Thanks, > > Brad > > On Feb 24, 2006, at 7:49 AM, Brad O'Hearne wrote: > > > Jess, > > > > Thanks for the reply. Responses below: > > > > On Feb 24, 2006, at 6:51 AM, Jess Holle wrote: > > > >> If you're using Apache 1.3.x or 2.0.x, mod_jk is pretty simple > >> overall. > >> > >> No, you don't want to even try in-process stuff and, yes, if you > >> have a firewall in between Apache and Tomcat that drops idle > >> connections you should read carefully (this is covered by > the docs). > >> > >> The only big complaint I have is that the mod_jk docs don't make > >> it terribly clear (or didn't last I checked) exactly how to set > >> jvmRoute in Tomcat and how extraordinarily critical this is when > >> doing load balancing. The Tomcat docs don't make this terribly > >> clear either -- apart from a comment in server.xml. Most > everyone > >> I know who tries mod_jk load balancing gets hung up on this one > >> point unless/until I give them a detailed explanation. > Apart from > >> the lack of clear/obvious information on this in the mod_jk docs > >> (which should include it considering most folk won't think to > >> check both mod_jk and Tomcat docs), this is actually very simple > >> as well, though. > >> > > > > None of the configuration steps in and of itself are difficult. > > Building mod_jk is not difficult. Editing configuration files is > > not difficult. Its after you've put it all together, exactly as > > noted on a hodge-podge of Googled URLs, and it doesn't work, and > > one cryptic line in a log file, and the right connections > not being > > made between apache and tomcat, which send you into hours of trial > > and error. With regards to your comments above, I didn't tangle > > with load balancing at all, and apache and tomcat reside on the > > same box, no firewall between them. Yes, you'd think this would be > > simple. > > > >> I am looking forward to mod_proxy_ajp as it is supposed be a tiny > >> bit faster. > > > > You say you are "looking forward to mod_proxy_ajp" -- does this > > mean its not available yet, or you just aren't using it yet? While > > I am glad to learn now of mod_proxy_ajp, I guess this kind of adds > > to my frustration a bit -- what is the way to go now and why: > > mod_proxy_ajp or mod_jk? > > > > Thanks for your help. > > > > Brad > > > >> > >> -- > >> Jess Holle > >> > >> Brad O'Hearne wrote: > >>> mod_proxy_ajp? Yet another twist. Its just hard for me to > believe > >>> that "how do I integrate tomcat and apache httpd?" is such a > >>> mystery / unknown. This seems like it would be question > #1 on any > >>> Tomcat FAQ. > >>> > >>> So where can I found out more about mod_proxy_ajp. Is there a > >>> Tomcat resource which explains the configuration of it? > >>> > >>> Brad > >>> > >>> > >>> Bill Barker wrote: > >>> > >>>> "Brad O'Hearne" <[EMAIL PROTECTED]> wrote in message news: > >>>> [EMAIL PROTECTED] > >>>> > >>>>> After wasting time trying to configure mod_jk, I thought I'd > >>>>> just wipe my mind free and just play dumb for a moment. If > >>>>> Apache can proxy requests using mod_proxy, what is the benefit > >>>>> of using mod_jk as an integration technique between httpd and > >>>>> tomcat, if integration is *not* in-process, which I understand > >>>>> is not recommended for Tomcat 5.5? > >>>>> > >>>>> >
Re: Which direction: mod_jk or mod_proxy_ajp? (was: why use mod_jk?)
Josh, Thanks a lot for your answer. I am using Apache 2.2.x. Now onto my next question. Bill Barker suggested the httpd.conf / mod_proxy_ajp directive side of the equation. Doesn't there have to be a connector in tomcat's server.xml which will allow listening for the ajp protocol? Is there documentation on this somewhere? Brad On Feb 24, 2006, at 8:07 AM, Fenlason, Josh wrote: That depends if you want to use Apache 2.0.x, Apache 2.2.x, or some other web server (i.e. IIS). If you're planning on using Apache 2.2.x, mod_proxy_ajp is the way to go. For anything else, mod_jk is the way to go. , Josh. -Original Message- From: Brad O'Hearne [mailto:[EMAIL PROTECTED] Sent: Friday, February 24, 2006 9:02 AM To: Tomcat Users List Subject: Which direction: mod_jk or mod_proxy_ajp? (was: why use mod_jk?) I suppose this question deserved its own thread. Before I spend any more time trying to get this configured, I would like to know what is the best way to proceed: mod_jk or mod_proxy_ajp? Thanks, Brad On Feb 24, 2006, at 7:49 AM, Brad O'Hearne wrote: Jess, Thanks for the reply. Responses below: On Feb 24, 2006, at 6:51 AM, Jess Holle wrote: If you're using Apache 1.3.x or 2.0.x, mod_jk is pretty simple overall. No, you don't want to even try in-process stuff and, yes, if you have a firewall in between Apache and Tomcat that drops idle connections you should read carefully (this is covered by the docs). The only big complaint I have is that the mod_jk docs don't make it terribly clear (or didn't last I checked) exactly how to set jvmRoute in Tomcat and how extraordinarily critical this is when doing load balancing. The Tomcat docs don't make this terribly clear either -- apart from a comment in server.xml. Most everyone I know who tries mod_jk load balancing gets hung up on this one point unless/until I give them a detailed explanation. Apart from the lack of clear/obvious information on this in the mod_jk docs (which should include it considering most folk won't think to check both mod_jk and Tomcat docs), this is actually very simple as well, though. None of the configuration steps in and of itself are difficult. Building mod_jk is not difficult. Editing configuration files is not difficult. Its after you've put it all together, exactly as noted on a hodge-podge of Googled URLs, and it doesn't work, and one cryptic line in a log file, and the right connections not being made between apache and tomcat, which send you into hours of trial and error. With regards to your comments above, I didn't tangle with load balancing at all, and apache and tomcat reside on the same box, no firewall between them. Yes, you'd think this would be simple. I am looking forward to mod_proxy_ajp as it is supposed be a tiny bit faster. You say you are "looking forward to mod_proxy_ajp" -- does this mean its not available yet, or you just aren't using it yet? While I am glad to learn now of mod_proxy_ajp, I guess this kind of adds to my frustration a bit -- what is the way to go now and why: mod_proxy_ajp or mod_jk? Thanks for your help. Brad -- Jess Holle Brad O'Hearne wrote: mod_proxy_ajp? Yet another twist. Its just hard for me to believe that "how do I integrate tomcat and apache httpd?" is such a mystery / unknown. This seems like it would be question #1 on any Tomcat FAQ. So where can I found out more about mod_proxy_ajp. Is there a Tomcat resource which explains the configuration of it? Brad Bill Barker wrote: "Brad O'Hearne" <[EMAIL PROTECTED]> wrote in message news: [EMAIL PROTECTED] After wasting time trying to configure mod_jk, I thought I'd just wipe my mind free and just play dumb for a moment. If Apache can proxy requests using mod_proxy, what is the benefit of using mod_jk as an integration technique between httpd and tomcat, if integration is *not* in-process, which I understand is not recommended for Tomcat 5.5? Actually, in-process with mod_jk is only supported (and, I use the term lightly :) for TC 3.3.x. For any higher versions it doesn't work at all. You've managed to grasp the deep, dark plan of the Tomcat developers: It is expected that people will migrate to mod_proxy_ajp with Httpd 2.2+, and mod_jk is expected to move to supporting IIS/SunOne only (and, the later only if somebody steps up with interest :). Brad --- -- 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional co
RE: Which direction: mod_jk or mod_proxy_ajp? (was: why use mod_jk?)
The following connector exists in the Tomcat 5.5.15 OOTB server.xml. I think that is all you need on the Tomcat side. , Josh. > -Original Message- > From: Brad O'Hearne [mailto:[EMAIL PROTECTED] > Sent: Friday, February 24, 2006 9:14 AM > To: Tomcat Users List > Subject: Re: Which direction: mod_jk or mod_proxy_ajp? (was: > why use mod_jk?) > > > Josh, > > Thanks a lot for your answer. I am using Apache 2.2.x. Now onto my > next question. Bill Barker suggested the httpd.conf / mod_proxy_ajp > directive side of the equation. Doesn't there have to be a connector > in tomcat's server.xml which will allow listening for the ajp > protocol? Is there documentation on this somewhere? > > Brad > > On Feb 24, 2006, at 8:07 AM, Fenlason, Josh wrote: > > > That depends if you want to use Apache 2.0.x, Apache 2.2.x, or some > > other web server (i.e. IIS). If you're planning on using Apache > > 2.2.x, > > mod_proxy_ajp is the way to go. For anything else, mod_jk is the > > way to > > go. > > , > > Josh. > > > >> -Original Message- > >> From: Brad O'Hearne [mailto:[EMAIL PROTECTED] > >> Sent: Friday, February 24, 2006 9:02 AM > >> To: Tomcat Users List > >> Subject: Which direction: mod_jk or mod_proxy_ajp? (was: why use > >> mod_jk?) > >> > >> > >> I suppose this question deserved its own thread. Before I > spend any > >> more time trying to get this configured, I would like to > know what is > >> the best way to proceed: mod_jk or mod_proxy_ajp? > >> > >> Thanks, > >> > >> Brad > >> > >> On Feb 24, 2006, at 7:49 AM, Brad O'Hearne wrote: > >> > >>> Jess, > >>> > >>> Thanks for the reply. Responses below: > >>> > >>> On Feb 24, 2006, at 6:51 AM, Jess Holle wrote: > >>> > >>>> If you're using Apache 1.3.x or 2.0.x, mod_jk is pretty simple > >>>> overall. > >>>> > >>>> No, you don't want to even try in-process stuff and, yes, if you > >>>> have a firewall in between Apache and Tomcat that drops idle > >>>> connections you should read carefully (this is covered by > >> the docs). > >>>> > >>>> The only big complaint I have is that the mod_jk docs > don't make it > >>>> terribly clear (or didn't last I checked) exactly how to set > >>>> jvmRoute in Tomcat and how extraordinarily critical this is when > >>>> doing load balancing. The Tomcat docs don't make this terribly > >>>> clear either -- apart from a comment in server.xml. Most > >> everyone > >>>> I know who tries mod_jk load balancing gets hung up on this one > >>>> point unless/until I give them a detailed explanation. > >> Apart from > >>>> the lack of clear/obvious information on this in the mod_jk docs > >>>> (which should include it considering most folk won't > think to check > >>>> both mod_jk and Tomcat docs), this is actually very > simple as well, > >>>> though. > >>>> > >>> > >>> None of the configuration steps in and of itself are difficult. > >>> Building mod_jk is not difficult. Editing configuration > files is not > >>> difficult. Its after you've put it all together, exactly > as noted on > >>> a hodge-podge of Googled URLs, and it doesn't work, and > one cryptic > >>> line in a log file, and the right connections > >> not being > >>> made between apache and tomcat, which send you into hours > of trial > >>> and error. With regards to your comments above, I didn't > tangle with > >>> load balancing at all, and apache and tomcat reside on > the same box, > >>> no firewall between them. Yes, you'd think this would be simple. > >>> > >>>> I am looking forward to mod_proxy_ajp as it is supposed > be a tiny > >>>> bit faster. > >>> > >>> You say you are "looking forward to mod_proxy_ajp" -- > does this mean > >>> its not available yet, or you just aren't using it yet? > While I am > >>> glad to learn now of mod_proxy_ajp, I guess this kind of > adds to my > >>> frustration a bit -- what is the way to go now and why: > >>> mod_proxy_ajp or mod_
Re: Which direction: mod_jk or mod_proxy_ajp? (was: why use mod_jk?)
* Brad O'Hearne wrote (24/02/06 15:14): > Josh, > > Thanks a lot for your answer. I am using Apache 2.2.x. Now onto my > next question. Bill Barker suggested the httpd.conf / mod_proxy_ajp > directive side of the equation. Doesn't there have to be a connector > in tomcat's server.xml which will allow listening for the ajp > protocol? Is there documentation on this somewhere? http://tomcat.apache.org/tomcat-5.5-doc/config/ajp.html In fact, the http://tomcat.apache.org/tomcat-5.5-doc/config/index.html page is a good place to go for a lot of things. I generally find tomcat documentation hard to read and hard to understand (I find httpd.conf much more to my taste), but it's generally possible to get there in the end, and better than following half-baked how-tos. The server.xml that ships with tomcat has an ajp connector by default, I think. By the way, I had a very similar battle getting mod_jk going, except that once I found that mod_proxy_ajp only worked in a version of apache I wasn't using, and that mod_jk2 was obsolete (whereas mod_jk wasn't), and I made the choice of mod_jk, setting it up wasn't actually too bad. However, I've found that a large POST to a web page through mod_jk can get mangled (and the mod_jk debug log simply doesn't show chunks of it), whereas direct to tomcat works fine. So I slightly mistrust ajp. There's not much documentation on the protocol, and what exists suggests that not very many people in the world really know what's going on with it. Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
