On Thu, 31 Oct 2002, Aryeh Katz wrote: > > Ok > > > > I just configures it to use ajp12 instead of ajp13. And now it works. > > Now I am really confused. > > First of all, in order for anyone to help you further, you should > really specify EXACTLY what you did (preferably with a screen scrape > so any typos can be caught), instead of saying "it".
Let me echo this. I found it very hard to follow what the person had/hadn't tried, what changed from post to post, etc.. And as a result, I just stayed out of the thread instead of trying to help, figuring it would be too much effort. And the whole idea of "it worked from w2k to w2k but not from linux to w2k, so I don't have to show the configuration" was a real red herring, because there are still so many configuration-related things that could have been involved. > Second of all, the fact that you were able to connect using ajp12, > that would seem to indicate that you had some kind of configuration > error with ajp13. > The easiest way to determine why would be to look at the > tomcat log files (and maybe the apache log files). I'm sure that > something will pop up if you set the logging high enough Another possibility (which perhaps has already been covered; as I said, I didn't follow the details of this thread) has to do with what's running on the remote machine running Tomcat. For example, if it's only got an ajp12 connector on port 8007, then looking for an ajp13 connector on port 8009 isn't going to work (and vice-versa). 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:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
