I could be wrong...it was my understanding that JK2 was only supported by CoyoteConnector. Since both, I believe, use the AJP13 protocol, I guess its possible that Ajp13Connector could/would/might work. I know more about what DOES work than what DOESN'T work. ;)
In any case, my point (perhaps not clearly stated) was that:
1) there is no need to do anything in server.xml to allow a default Tomcat install to work with one of the connectors
2) Ajp13Connector is not the preferred connector for either JK or JK2 in recent versions of Tomcat ( > 4.1.12?)
There's bound to be people that have unusual/uncommon environments that work...but for people just getting started, I think its less traumatic to guide them towards the usual/common environments until they get some experience.
John
On Tue, 01 Jul 2003 12:32:12 -0500, Geralyn M Hollerman <[EMAIL PROTECTED]> wrote:
John Turner wrote: Tomcat comes with a JK2 compatible connector enabled by default on port 8009. The class name for this connector is CoyoteConnector. Ajp13Connector is for JK and is incompatible with JK2...it will never work.
Whoa! I couldn't get the CoyoteConnector to work with 4.0.4 (I got errors in catalina.out about the CoyoteConnector not being found), but the Ajp13Connector behaved fine with JK2 - at least I *thought* - we *have* had some odd things going on with Tomcat 4.0.4 lately, but attributed that to trying too many upgrades at one time (like JDK 1.3 -> JDK 1.4, upgrade of an EDBC driver) as we didn't see anything obvious in any Tomcat or Apache logs...I can see (thru "ps -ef") when Tomcat and/or Apache are/is running, and from the messages in the various logs, it appears things are working right, but...what would I see that might tell me that there was a problem with Ajp13Connector?
Thanks!
-- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
