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 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 host). I created a second CoyoteConnector
using the JkCoyoteHandler listening on port 8443. I should be able to
have multiple connectors as long as they are on different ports, right?
After I restarted the sever, I saw an error message when the second AJP
connector tried to initialize. It reported that port 8009 was already
bound. It then promptly bound the second connector to port 8010. This
truly confused me. I double checked my configureation and everything
seemed to be correct. I also did a netstat -l to see what ports were
actually in use. Ports 8009 and 8010 had listeners.
I removed the second connector. I then changed the original connector
to listen on port 8019. I now had only one CoyoteConnector for AJP13
connections configured. The only port is 8019.
After I restarted the server, the connector bound itself to 8009.
netstat -l confirmed that this was not a bogus log message.
From the way this looks, a coyote connector using the JkCoyoteHandler
will always attempt to use port 8009 reguadless of the port attribute of
the connector. If the port is not available, it increment the port
number by one and try again. This appears to be a bug.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
