I am running into a strange problem on Tomcat 4.1.18.
I setup a CoyoteConnector on port 8009 using the JkCoyoteHandler
protocol handler to handle AJP13 requests. This worked perfectly.
I then needed to add a second AJP13 connector to process secure requests
(though an ssl apache virtual
There is a bug in 4.1.18 where it will always behave as you are seeing. It
should be fixed in 4.1.24. Even with 4.1.18, you should be able to override
the port setting in the jk2.properties file.
Quinton McCombs [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
I am running into a
