[ 
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.

Reply via email to