Turner, John <[EMAIL PROTECTED]> wrote:
>
> My point about the connectors was that, in server.xml, you should
> DISABLE Ajp13Connector and ENABLE CoyoteConnector on port 8009.
> CoyoteConnector supports both JK and JK2 *and HTTP and HTTPS).
>
> So, you can use Apache 1.3, mod_jk, but then on the Tomcat side choose
> CoyoteConnector instead of Ajp13Connector. CoyoteConnector is
> enabled by default...just reverse the change you made in server.xml.
<!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
^^^
That had mistaken me! :)
- I thought is was only for JK2
I've just removed Ajp13Connector and deployed CoyoteConnector
and indeed it works much better. After 5 minutes of tests
I don't see any strange errors in tomcat/logs.
There is only one error message in httpd mod_jk.log:
---------------------------------------------------------------
[Thu Feb 27 18:41:29 2003] [jk_ajp_common.c (970)]: ERROR sending data to client.
Connection aborted or network problems
---------------------------------------------------------------
I looks that is somehow connected with this catalina.out message:
---------------------------------------------------------------
Feb 27, 2003 6:41:29 PM org.apache.jk.common.ChannelSocket processConnection
INFO: Server has been restarted or reset this connection
---------------------------------------------------------------
which I don't understand exactly (maybe it is because I use it for the first time)?
BTW: which JkLogLevel is more verbose: info or error?
Info is usually used to get more verbose output then error,
does it work differently in JK?
Anyway, thanks for all your hints till now, John.
--
Tomasz Nowak
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
