Thanks. One thing I'm not clear about is what the ant build instructions for the connectors are doing. Those files aren't used anywhere that I can see.
I think there is going to be a lot more traffic regarding the connectors in the next few days/weeks. I just spent several hours trying to get the 4.1.10 connectors built from source, both JK and JK2, using both ./configure and ant, without success. Maybe the dev team is focusing only on JK2. That's fine, but the docs I have seen are just copies of earlier docs with no new information whatsoever. It doesn't look to me like very much effort was put into fixing and cleaning up the build process, either. I'm not complaining, just observing. I hope the plan is to get a nice group of JK2 binaries up on the Jakarta site. John -----Original Message----- From: Milt Epstein To: Tomcat Users List Sent: 9/9/02 5:14 PM Subject: RE: AJP 1.3 Connector fails to load on Tomcat 4.1.10 On Mon, 9 Sep 2002, Turner, John wrote: > OK. Hopefully docs are coming soon! I've always wondered what the > heck the difference was between the "Java" side and the "C" side, > obvious differences aside. > > I really want to understand how a .jar file can be an Apache module, > which is what I think you mean when you say "Java" side, though I am > probably wrong. Here's my understanding of this: Connectors that integrate Apache and Tomcat have a "side" that "is part of" Apache, and another that "is part of" Tomcat. They can be separated this way because they communicate through a port, and are not otherwise connected (i.e. they are otherwise independent, e.g. in terms of implementation language, they just have to "speak" the same protocol and know what port to communicate through). It's just like you have a separate web browser and web server, and they can use HTTP to communicate on some agreed upon port (usually 80), and it doesn't matter what language they're implemented in. The side that is part of Apache is a module (e.g. mod_jk), and is written in C, as most/all modules are. This is essentially what mod_jk.so is. (I imagine you can have a module written in java, but that it's probably not the best/easiest way to go.) The side that is part of Tomcat is written in Java, as most/all of Tomcat is. This is essentially what tomcat-ajp.jar (on my set up/version, at least) is. > > -----Original Message----- > > From: Remy Maucherat [mailto:[EMAIL PROTECTED]] > > Sent: Monday, September 09, 2002 4:16 PM > > To: Tomcat Users List > > Subject: Re: AJP 1.3 Connector fails to load on Tomcat 4.1.10 > > > > > > Turner, John wrote: > > > So JK (mod_jk) is incompatible with Tomcat 4.1.10? Or is there a > > > configuration parameter that turns off the JMX features? > > > > Yes, remove the ServerLifecycleListener Listener. > > > > On the Java side, the old AJP 1.3 connector is deprecated. > > Use Coyote JK2. > > > > On the C side, both mod_jk and mok_jk2 are supported. > > > > There's a page in the docs about all the connectors to help you > > understand what does what. > > > > Remy > Milt Epstein Research Programmer Integration and Software Engineering (ISE) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
