https://issues.apache.org/bugzilla/show_bug.cgi?id=49521
Summary: Fix ordering issues in setting channelSocket.maxPort
Product: Tomcat 6
Version: 6.0.26
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: Connectors
AssignedTo: dev@tomcat.apache.org
ReportedBy: knst.koli...@gmail.com
There is a feature in org.apache.jk.server.JkCoyoteHandler implementation of
AJP/1.3 protocol: when connector fails to bind to the specified port, it does
not fail immediately but will try next available port number.
This was previously discussed in the following threads:
http://marc.info/?t=126402175600004&r=1&w=2
http://marc.info/?t=119266320200003&r=1&w=2
This feature is implemented in the org.apache.jk.common.ChannelSocket and
ChannelNioSocket classes and can be controlled by setting channelSocket.maxPort
property on a <Connector/>, but there is a bug:
ChannelSocket#setPort(int) resets the value of maxPort, and thus the final
configuration is dependent on the order in which the XML attributes were
processed.
This concerns only JkCoyoteHandler implementation of the protocol, present in
Tomcat 5.5 and 6.0. The new AjpProtocol implementation present in 6.0 and used
by default in Tomcat 7.0, as well AjpAprProtocol are not affected.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
