[
https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656559#action_12656559
]
Jarek Gawor commented on GERONIMO-4442:
---------------------------------------
RMIRegistry and JMXConnectors can bind to a specific address using a custom
RMIServerSocketFactory. I created this factory and made RMI registry and JMX
connectors use it. Changes committed to trunk (revision 726624) and
branches/2.1 (revision 726626).
> Unable to configure IP address for many listening ports
> -------------------------------------------------------
>
> Key: GERONIMO-4442
> URL: https://issues.apache.org/jira/browse/GERONIMO-4442
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.0.2, 2.1.3
> Reporter: Kevan Miller
> Priority: Critical
> Fix For: 2.1.4, 2.2
>
> Attachments: G4222_ORBConfigAdapter.patch
>
>
> I tried to configure the listening IP address for our server sockets. I
> configured all 'host' properties in config-substitution.properties to be
> '127.0.0.1' and got the following results:
> Listening on Ports:
> 1050 127.0.0.1 CORBA Naming Service
> 1099 127.0.0.1 RMI Naming
> 1527 127.0.0.1 Derby Connector
> 2001 127.0.0.1 OpenEJB ORB Adapter
> 4201 127.0.0.1 OpenEJB Daemon
> 6882 127.0.0.1 OpenEJB ORB Adapter
> 8009 127.0.0.1 Tomcat Connector AJP AJP
> 8080 127.0.0.1 Tomcat Connector HTTP BIO HTTP
> 8443 127.0.0.1 Tomcat Connector HTTPS BIO HTTPS
> 9999 127.0.0.1 JMX Remoting Connector
> 61613 127.0.0.1 ActiveMQ Transport Connector
> 61616 127.0.0.1 ActiveMQ Transport Connector
> Unfortunately, that's not accurate. netstat reveals the following actual
> results:
> $ netstat -an | grep LISTEN
> tcp4 0 0 *.6882 *.* LISTEN
> tcp4 0 0 *.2001 *.* LISTEN
> tcp4 0 0 *.63519 *.* LISTEN
> tcp4 0 0 *.1050 *.* LISTEN
> tcp4 0 0 127.0.0.1.4201 *.* LISTEN
> tcp4 0 0 127.0.0.1.61613 *.* LISTEN
> tcp4 0 0 127.0.0.1.61616 *.* LISTEN
> tcp4 0 0 127.0.0.1.1527 *.* LISTEN
> tcp4 0 0 127.0.0.1.8443 *.* LISTEN
> tcp4 0 0 127.0.0.1.8009 *.* LISTEN
> tcp4 0 0 127.0.0.1.8080 *.* LISTEN
> tcp4 0 0 *.9999 *.* LISTEN
> tcp4 0 0 *.1099 *.* LISTEN
> Configuring the host properties to be an actual ip address/hostname is a bit
> worse (not sure what's going on with ActiveMQ):
> Listening on Ports:
> 1050 10.0.1.196 CORBA Naming Service
> 1099 10.0.1.196 RMI Naming
> 1527 10.0.1.196 Derby Connector
> 2001 10.0.1.196 OpenEJB ORB Adapter
> 4201 10.0.1.196 OpenEJB Daemon
> 6882 10.0.1.196 OpenEJB ORB Adapter
> 8009 10.0.1.196 Tomcat Connector AJP AJP
> 8080 10.0.1.196 Tomcat Connector HTTP BIO HTTP
> 8443 10.0.1.196 Tomcat Connector HTTPS BIO HTTPS
> 9999 10.0.1.196 JMX Remoting Connector
> 61613 0.0.0.0 ActiveMQ Transport Connector
> 61616 0.0.0.0 ActiveMQ Transport Connector
> Netstat shows:
> $ netstat -an | grep LISTEN
> tcp6 0 0 fe80::1%lo0.631 *.* LISTEN
> tcp4 0 0 *.6882 *.* LISTEN
> tcp4 0 0 *.2001 *.* LISTEN
> tcp4 0 0 *.63569 *.* LISTEN
> tcp4 0 0 *.1050 *.* LISTEN
> tcp4 0 0 10.0.1.196.4201 *.* LISTEN
> tcp4 0 0 *.61613 *.* LISTEN
> tcp4 0 0 *.61616 *.* LISTEN
> tcp4 0 0 10.0.1.196.1527 *.* LISTEN
> tcp4 0 0 10.0.1.196.8443 *.* LISTEN
> tcp4 0 0 10.0.1.196.8009 *.* LISTEN
> tcp4 0 0 10.0.1.196.8080 *.* LISTEN
> tcp4 0 0 *.9999 *.* LISTEN
> tcp4 0 0 *.1099 *.* LISTEN
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
