Re: tomcat-user Digest 1 Jul 2003 20:23:51 -0000 Issue 3015
Eric J. Pinnell wrote: 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. ;) It works *sorta*. It connects and passes data but some freakish things happen once in a while. We had a problem with this configuration (JK2 to Ajp13Connector, that was put in by mistake) and it would do stuff like forget to pass HTTP headers every so often. Wierd stuff like that. Freakish things once in while? Weird stuff? Sounds like what's happening to us...this is with TC 4.0.4 that I have Ajp13Connector with JK2 - I also have a TC 4.1.24 with CoyoteConnector/JK2 running in test and would like to move to that one. Do you have any strange error messages showing up in your Apache log that could be connected to this? More importantly, to fix this, was it just a matter of substituting Coyote for Ajp13 in server.xml, or was there more to it? Thanks! -- Lynn Hollerman. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat-user Digest 1 Jul 2003 20:23:51 -0000 Issue 3015
Freakish things once in while? Weird stuff? Sounds like what's happening to us...this is with TC 4.0.4 that I have Ajp13Connector with JK2 - I also have a TC 4.1.24 with CoyoteConnector/JK2 running in test and would like to move to that one. Do you have any strange error messages showing up in your Apache log that could be connected to this? What we saw at first was (with TC 4.1.18) the JMX listeners would throw errors on startup. So we commented out: Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/ Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener debug=0/ Just to make the errors go away. Then we had a debug jsp that spit all the info that the app was using out... values in cookies, headers, and other application specific things. We noticed that sometimes the information the application was looking for was there, and sometimes it wasn't. A specific example would be the 'referer' header that our app needed. Sometimes it was there... sometimes it wasn't. More importantly, to fix this, was it just a matter of substituting Coyote for Ajp13 in server.xml, or was there more to it? by default the correct JK2 connector is enabled: !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=0 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ That's the one you want to use. After using this you can uncomment out the JMX Listeners. They play nice with Coyote. -e - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
