I have a multihomed server on which I have installed two identical versions of JBoss 4.2.0. I have also installed JBoss native on each in order to use the Tomcat APR optimizations. I also set up an HTTPS connector on each server. I use the -b option on each instance in order to bind it to a dedicated network card. Running each server by itself prevents no issues. When I try to start the second server when the first is already running, I get a port binding error (the port configurations on each instance are identical, since they will be using a different NIC).
A little investigation reveals that the HTTPS connector is listening on all available IP addressed. Thus when the second server starts, it fails to bind to the HTTPS port. When I adjust the HTTPS port on the second server I no longer get this error. Is there a configuration beyond the -b start up parameter I should be using to prevent the SSL connector from listening on all IP addresses? The configuration for the connector, as detailed at http://tomcat.apache.org/tomcat-6.0-doc/apr.html, is below: | <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true" | maxThreads="150" scheme="https" secure="true" | clientAuth="false" sslProtocol="TLS" | SSLCertificateFile="C:/certs/cert.pem" | SSLCertificateKeyFile="C:/certs/key.pem" | SSLPassword="notmyrealpassword" /> | Thanks, Ray View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066817#4066817 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066817 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user