You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Kevan Miller (JIRA)" <ji...@apache.org> on 2008/12/03 15:49:44 UTC
[jira] Created: (GERONIMO-4442) Unable to configure IP address for
many listening ports
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.1.3, 2.0.2
Reporter: Kevan Miller
Priority: Critical
Fix For: 2.1.4, 2.2
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.
[jira] Commented: (GERONIMO-4442) Unable to configure IP address
for many listening ports
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652822#action_12652822 ]
Donald Woods commented on GERONIMO-4442:
----------------------------------------
Are you testing on 2.1.3 only? We put a fix for the ActiveMQ 0.0.0.0 problem in 2.1.4 and trunk (related to localhost always being mapped to 0.0.0.0, but there may be another scenario that needs fixing...)
> 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
>
>
> 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.
[jira] Commented: (GERONIMO-4442) Unable to configure IP address
for many listening ports
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657492#action_12657492 ]
Donald Woods commented on GERONIMO-4442:
----------------------------------------
Testing ORBConfigAdapter patch from Shawn. Will apply as soon as my build and testsuite runs complete.
> 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.
[jira] Commented: (GERONIMO-4442) Unable to configure IP address
for many listening ports
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (GERONIMO-4442) Unable to configure IP address
for many listening ports
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655086#action_12655086 ]
Shawn Jiang commented on GERONIMO-4442:
---------------------------------------
I did some work on this and here are the results:
* yoko ORB related.
** 1050 127.0.0.1 CORBA Naming Service
** 2001 127.0.0.1 OpenEJB ORB Adapter
** 6882 127.0.0.1 OpenEJB ORB Adapter
If we need to the service/server above to listen to the host we configured, the properties passed in should incluce a "--bind" + host to initiate the ORB. I'll upload a patch on this.
* 1099 RMI Naming
GERONIMO-4386 did some changes on this but seems it only sycronized the IP in console display to that in config. The actual RMI Naming is still *0.0.0.0* whatever serverHost you configured in config files. That's because geronimo uses
following code to start the RMI Naming registry.
{code:title="org/apache/geronimo/kernel/rmi/RMIRegistryService.java"}
public void doStart() throws Exception {
System.setProperty("java.rmi.server.RMIClassLoaderSpi",RMIClassLoaderSpiImpl.class.getName());
registry = LocateRegistry.createRegistry(port);
log.debug("Started RMI Registry on port " + port);
}
{code}
The JDK class *LocateRegistry* does not provide a API to permit a host as a parameter, It's a limitation for now. maybe we should log this somewhere in the document. host config for RMI Naming might need to be removed from the current config file because it does not work at all.
* 9999 0.0.0.0 JMX Remoting Connector
Geronimo use following code to initiate the JMX server in JDK, *0.0.0.0* will be used whatever the real host was passed in the code per http://pub.admc.com/howtos/jmx/ch09.html.
{code:title="org/apache/geronimo/jmxremoting/JMXConnector.java"}
server = JMXConnectorServerFactory.newJMXConnectorServer(jmxServiceURL, env, mbeanServer);
{code}
It's a limitation for now. maybe we should log this somewhere in the document. host config for JMX Remoting Connector might need to be removed from the current config file because it does not work at all.
* ActiveMQ works only with localhost and 127.0.0.1
** 61613 0.0.0.0 ActiveMQ Transport Connector
** 61616 0.0.0.0 ActiveMQ Transport Connector
GERONIMO-4404 fixed the localhost to 0.0.0.0 problem, but the real connector creation code in activemq is:
{code:title="org.apache.activemq.transport.tcp.TcpTransportServer"}
InetAddress addr = InetAddress.getByName(host);
try {
if (host.trim().equals("localhost") || addr.equals(InetAddress.getLocalHost())) {
//#1 start the socket with 0.0.0.0
this.serverSocket = serverSocketFactory.createServerSocket(bind.getPort(), backlog);
}
else {
//#2 start the socket with the ip spcified in addr.
this.serverSocket = serverSocketFactory.createServerSocket(bind.getPort(), backlog, addr);
}
{code}
Since if you config the real IP as a host setting, addr.equals(InetAddress.getLocalHost()) will allways be true so that the #1 will be used to start the socket with 0.0.0.0. I'm not sure if it's a bug of activemq, there's nothing we can do from geronimo side for now to fix this.
* Any comments ?
> 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
>
>
> 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.
[jira] Commented: (GERONIMO-4442) Unable to configure IP address
for many listening ports
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657543#action_12657543 ]
Kevan Miller commented on GERONIMO-4442:
----------------------------------------
Not clear to me from the jira comments that ActiveMQ has been fixed. Looks like we're at least close... Thanks Shawn, Jarek, and Donald!
Has anybody tested with the latest source?
> 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
> Assignee: 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.
[jira] Commented: (GERONIMO-4442) Unable to configure IP address
for many listening ports
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657564#action_12657564 ]
Kevan Miller commented on GERONIMO-4442:
----------------------------------------
Hmm. I'm getting the following error trying to start a server on my Mac:
{noformat}
2008-12-17 16:15:29,776 WARN [2-SNAPSHOT/car,j2eeType=GBean,name=JMXService] Failure in JMXConnector service:jmx:rmi://0.0.0.0:9999/jndi/rmi://0.0.0.0:1099/JMXConnector
2008-12-17 16:15:29,777 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName="org.apache.geronimo.framework/j2ee-security/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.framework/j2ee-security/2.2-SNAPSHOT/car,j2eeType=GBean,name=JMXService"
java.io.IOException: Cannot bind to URL [rmi://0.0.0.0:1099/JMXConnector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 0.0.0.0; nested exception is:
java.net.ConnectException: Operation timed out]
at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
at org.apache.geronimo.jmxremoting.JMXConnector.doStart(JMXConnector.java:201)
at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125)
at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:538)
at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:377)
at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:562)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:815)
at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$7713edc.startConfiguration(<generated>)
at org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:161)
at org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
{noformat}
Anybody else?
> 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
> Assignee: 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.
[jira] Assigned: (GERONIMO-4442) Unable to configure IP address for
many listening ports
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods reassigned GERONIMO-4442:
--------------------------------------
Assignee: Donald Woods
> 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
> Assignee: Donald Woods
> 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.
[jira] Commented: (GERONIMO-4442) Unable to configure IP address
for many listening ports
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669880#action_12669880 ]
Shawn Jiang commented on GERONIMO-4442:
---------------------------------------
Except the ActiveMQ, Others host binding problems have been fixed in both 2.1.4 snapshot and 2.2 snapshot build.
Since It seems that the ActiveMQ host binding problem can't be fixed in geronimo side, I reopened https://issues.apache.org/jira/browse/GERONIMO-4404 to continue to track the remaining ActiveMQ binding problem.
Can you please close this one ? Thanks.
> 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
> Assignee: 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.
[jira] Commented: (GERONIMO-4442) Unable to configure IP address
for many listening ports
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672047#action_12672047 ]
Jarek Gawor commented on GERONIMO-4442:
---------------------------------------
Btw, I updated the code so that ServerHostname property will configure the hostname for Corba services also (that is, got rid off COSNamingHost, ORBSSLHost, and ORBHost properties). Committed to trunk (revision 742781) and branches/2.1 (revision 742782).
> 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
> Assignee: 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.
[jira] Resolved: (GERONIMO-4442) Unable to configure IP address for
many listening ports
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor resolved GERONIMO-4442.
-----------------------------------
Resolution: Fixed
Resolving as indicated by Shawn everything is fixed except ActiveMQ ports and we have a separate JIRA (GERONIMO-4404) to track that.
> 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
> Assignee: 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.
[jira] Commented: (GERONIMO-4442) Unable to configure IP address
for many listening ports
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657570#action_12657570 ]
Kevan Miller commented on GERONIMO-4442:
----------------------------------------
On a hunch, I plugged my ethernet cable into my Mac. I was then able to start the server successfully.
I disconnected my ethernet cable. Server startup again failed.
> 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
> Assignee: 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.
[jira] Commented: (GERONIMO-4442) Unable to configure IP address
for many listening ports
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657533#action_12657533 ]
Donald Woods commented on GERONIMO-4442:
----------------------------------------
ORBConfigAdapter patch from Shawn applied to trunk (2.2-SNAPSHOT) and 2.1.4-SNAPSHOT.
> 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
> Assignee: Donald Woods
> 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.
[jira] Issue Comment Edited: (GERONIMO-4442) Unable to configure IP
address for many listening ports
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657646#action_12657646 ]
genspring edited comment on GERONIMO-4442 at 12/17/08 5:54 PM:
-----------------------------------------------------------------
It seems as the server can't be shutdown when the host is localhost/127.0.0.1.
If the ip is set to the real IP x.x.x.x. use
{code}
Y:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT\bin\shutdown.bat --host x.x.x.x
{code}
the server shutdown without problem. But if you set the ip to 127.0.0.1 then try to shutdown it.
{code}
Y:\geronimo-tomcat6-javaee5-2.2-SNAPSHOT\bin\shutdown.bat --host 127.0.0.1
{code}
will get error:
{code}
Username: system
Password: *******
Locating server on port 1099...
Could not communicate with the server. The server may not be running or the por
t number may be incorrect (Failed to retrieve RMIServer stub: javax.naming.Servi
ceUnavailableException [Root exception is java.rmi.ConnectException: Connection
refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused: connect])
{code}
I guess it's caused by the limited RMI or JMX address.
was (Author: genspring):
It seems as the server can't be shutdown when the host is localhost/127.0.0.1 or the real IP. I got following error when trying to shutdown the server:
{code}
Username: system
Password: *******
Locating server on port 1099...
Could not communicate with the server. The server may not be running or the por
t number may be incorrect (Failed to retrieve RMIServer stub: javax.naming.Servi
ceUnavailableException [Root exception is java.rmi.ConnectException: Connection
refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused: connect])
{code}
guess it's caused by the limited RMI or JMX address.
> 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
> Assignee: 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.
[jira] Updated: (GERONIMO-4442) Unable to configure IP address for
many listening ports
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated GERONIMO-4442:
-----------------------------------
Patch Info: [Patch Available]
Assignee: Kevan Miller (was: Donald Woods)
Kevan, anything else needed for this JIRA?
> 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
> Assignee: 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.
[jira] Commented: (GERONIMO-4442) Unable to configure IP address
for many listening ports
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657646#action_12657646 ]
Shawn Jiang commented on GERONIMO-4442:
---------------------------------------
It seems as the server can't be shutdown when the host is localhost/127.0.0.1 or the real IP. I got following error when trying to shutdown the server:
{code}
Username: system
Password: *******
Locating server on port 1099...
Could not communicate with the server. The server may not be running or the por
t number may be incorrect (Failed to retrieve RMIServer stub: javax.naming.Servi
ceUnavailableException [Root exception is java.rmi.ConnectException: Connection
refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused: connect])
{code}
guess it's caused by the limited RMI or JMX address.
> 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
> Assignee: 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.
[jira] Commented: (GERONIMO-4442) Unable to configure IP address
for many listening ports
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652827#action_12652827 ]
Kevan Miller commented on GERONIMO-4442:
----------------------------------------
Above was with current trunk (2.2-SNAPSHOT). I saw similar behavior on 2.1.4-SNAPSHOT. However, not sure when I last built branches/2.1.
Note that ActiveMQ server sockets is just one of multiple issues... Configuring ServerHostname=127.0.0.1 is the only case that seems to work for ActiveMQ. Any other value seems to lead to incorrect behavior...
> 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
>
>
> 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.
[jira] Updated: (GERONIMO-4442) Unable to configure IP address for
many listening ports
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Jiang updated GERONIMO-4442:
----------------------------------
Attachment: G4222_ORBConfigAdapter.patch
This is a patch to resolve yoko ORB related port setting problems
* 1050 127.0.0.1 CORBA Naming Service
* 2001 127.0.0.1 OpenEJB ORB Adapter
* 6882 127.0.0.1 OpenEJB ORB Adapter
by adding a "--binding host " part to the ORB initializing property "yoko.orb.oa.endpoint". Unit testing passed on both 21 and trunk.
> 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.