Aaron,
I am confident we handle this. The ConnectorGBean is a simply a GBean
proxy for the Tomcat Connector object. You can declaritively change the
ip address to listen on with an initParam called "address" in the GBean
configuration. See here for an example of how this would be done in our
j2ee-server-tomcat-plan.xml using 192.168.0.1:
<gbean name="TomcatWebConnector"
class="org.apache.geronimo.tomcat.ConnectorGBean">
<attribute name="initParams">
address=192.168.0.1
port=${PlanTomcatHTTPPort}
maxHttpHeaderSize=8192
maxThreads=150
minSpareThreads=25
maxSpareThreads=75
enableLookups=false
redirectPort=${PlanTomcatHTTPSPort}
acceptCount=100
connectionTimeout=20000
disableUploadTimeout=true
</attribute>
<reference name="TomcatContainer">
<name>TomcatWebContainer</name>
</reference>
</gbean>
Since we are proxying the call to the Connector object, we support and
pass on all Tomcat configurations to the Tomcat engine as listed here:
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/http.html. So,
IMHO, I believe we support this for Tomcat.
Does this handle the concern?
Thanks,
Jeff
Aaron Mulder (JIRA) wrote:
Can't set listen host/IP for Tomcat Connectors
----------------------------------------------
Key: GERONIMO-702
URL: http://issues.apache.org/jira/browse/GERONIMO-702
Project: Geronimo
Type: Bug
Components: Tomcat
Versions: 1.0-M3
Reporter: Aaron Mulder
Currently the Tomcat network connector GBean lets you specify the port to
listen on, but not the host/IP. Both should be allowed. The class in question
is:
geronimo/modules/tomcat/org/apache/geronimo/tomcat/ConnectorGBean
When this is done, the getAddress method on that class should be changed to return the
correct listen address instead of being hardcoded to return "0.0.0.0" and the
relevant port.
