"Mark Thomas" <ma...@apache.org> wrote in message
news:4b57bb79.3010...@apache.org...
On 20/01/2010 17:08, Christopher Schultz wrote:
Paul,
On 1/20/2010 4:08 PM, Paul Guglielmino wrote:
I'm setting up the server to only listen on an ajp port (8009). If I
already
have something listening on that port then tomcat starts listening on
the next
port number (8010). This doesn't happen if the shutdown port is already
in use
or if I try it with a http connector port that is in use.
I don't seem any mention of this behavior in the docs. I do see an
autobind
option for clustering which will turn on behavior like this but I'm not
using
clustering.
I don't see any mention of the auto-port-choosing for <Connector>s,
either. Are you doing this manually?
It is an undocumented feature of the
org.apache.jk.server.JkCoyoteHandler implementation. Setting maxPort to
the same value as port should disable it.
I think that mod_jk2 had logic to handle discovery. Granted, it isn't a
very useful feature with mod_jk.
Alternatively use the newer (and default in Tomcat 7)
org.apache.coyote.ajp.AjpProtocol implementation.
And currently the only pure Java implementation in Tomcat 7 :).
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
