geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Updated: (GERONIMO-1575) JMX service doesn't start up when server hostname does not resolve correctly
Date Thu, 02 Feb 2006 15:48:04 GMT
     [ ]

Aaron Mulder updated GERONIMO-1575:

      Component: core
        Summary: JMX service doesn't start up when server hostname does not resolve correctly
 (was: JMX service doesn't start up when in the DHCP network)
    Fix Version: 1.1

To work around this problem, change the JMX URLs in var/config/config.xml to bind to localhost
only (not  For more information, see the recent thread on the mailing list "Start
up Error" and also GERONIMO-1349

> JMX service doesn't start up when server hostname does not resolve correctly
> ----------------------------------------------------------------------------
>          Key: GERONIMO-1575
>          URL:
>      Project: Geronimo
>         Type: Bug
>   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
>     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: '
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"
> javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException:
Exception creating connection to: 192.168.8
> 1.141; nested exception is:
> No route to host]
>        at mx4j.remote.resolver.rmi.Resolver.bindServer(
>        at
>        at org.apache.geronimo.jmxremoting.JMXConnector.doStart(
>        at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(
>        at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(
>        at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(
>        at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(
>        at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(
>        at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(
>        at org.apache.geronimo.kernel.config.Configuration.startRecursiveGBeans(
>        at org.apache.geronimo.kernel.config.Configuration$$FastClassByCGLIB$$7f4b4a9b.invoke(<generated>)
>        at net.sf.cglib.reflect.FastMethod.invoke(
> 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 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:
For more information on JIRA, see:

View raw message