geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dain Sundstrom (JIRA)" <...@geronimo.apache.org>
Subject [jira] Closed: (GERONIMO-1575) JMX service doesn't start up when server hostname does not resolve correctly
Date Wed, 19 Apr 2006 06:52:19 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1575?page=all ]
     
Dain Sundstrom closed GERONIMO-1575:
------------------------------------

    Fix Version: 1.1
                     (was: 1.2)
     Resolution: Fixed

The host can be set via the config.xml file:

    <configuration name="geronimo/j2ee-security/${pom.currentVersion}/car">
        <gbean name="JMXService">
          <attribute name="protocol">rmi</attribute>
          <attribute name="host">${PlanServerHostname}</attribute>
          <attribute name="port">${PlanJMXPort}</attribute>
          <attribute name="urlPath">/jndi/rmi://${PlanServerHostname}:${PlanNamingPort}/JMXConnector</attribute>
        </gbean>
    </configuration>

> JMX service doesn't start up when server hostname does not resolve correctly
> ----------------------------------------------------------------------------
>
>          Key: GERONIMO-1575
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1575
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: core
>     Versions: 1.0
>  Environment: OS: Linux Fedora Core 3, Kernel 2.6.11-7 with SMP enabled (dual-core processor)
> Java: jdk 1.4.2_10
> Network: DHCP network
> Hardware: 3Ghz dual-core pentium 4, 1Gb of RAM.
>     Reporter: Timotej Ecimovic
>     Assignee: Dain Sundstrom
>     Priority: Minor
>      Fix For: 1.1

>
> This problem occurs ONLY when I am on the DHCP network. It does not happen when I'm off
the network or on the static IP network.
> When I'm on the DHCP network (wired or wireless). I can't talk to JMX. Running: 'geronimo.sh
stop' doesn't work as it says 'can't connect'.
> My startup geronimo.log shows:
> 08:26:57,700 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED
state: objectName="geronimo.server:J2EEApplication=null,J2E
> EModule=geronimo/j2ee-security/1.0/car,J2EEServer=geronimo,j2eeType=GBean,name=JMXService"
> java.io.IOException: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException:
Exception creating connection to: 192.168.8
> 1.141; nested exception is:
>        java.net.NoRouteToHostException: No route to host]
>        at mx4j.remote.resolver.rmi.Resolver.bindServer(Resolver.java:199)
>        at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:152)
>        at org.apache.geronimo.jmxremoting.JMXConnector.doStart(JMXConnector.java:122)
>        at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:936)
>        at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:325)
>        at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:110)
>        at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:132)
>        at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:537)
>        at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:208)
>        at org.apache.geronimo.kernel.config.Configuration.startRecursiveGBeans(Configuration.java:315)
>        at org.apache.geronimo.kernel.config.Configuration$$FastClassByCGLIB$$7f4b4a9b.invoke(<generated>)
>        at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
> So for some or another reason, JMX server tries to use the DHCP hostname in some way,
which does not make it happy.
> When this happen, I can run: arp -a, and in my ARP table I see an '<incomplete>'
entry for my DHCP hostname which is the underlying problem. 
> The workaround is to force your hostname to be localhost.localdomain or 127.0.0.1 or
something like that.  (run 'hostname localhost').
> Other workaround is to delete the DHCP hostname specified with your DHCP configuration.
> Do note that everything else works ok. I can deploy the EAR through the admin console
for example. I can run it normally. But the JMX part does not start up, so I can't deploy
the ant through ant target.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message