aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alasdair Nottingham (Commented) (JIRA)" <>
Subject [jira] [Commented] (ARIES-554) aries JNDI bundle breaks remote JMX clients via RMI
Date Sun, 16 Oct 2011 22:52:11 GMT


Alasdair Nottingham commented on ARIES-554:


The bug is resolved in the svn trunk, there hasn't been a release from trunk. The problem
affected both 0.2 and 0.3 which is why you seeing the problem on 0.3. When we do a release
the Fix version field will be updated to reflect the released version it was fixed in. We
don't know the version until we do the release. Once the release goes out this problem will
be closed.
> aries JNDI bundle breaks remote JMX clients via RMI
> ---------------------------------------------------
>                 Key: ARIES-554
>                 URL:
>             Project: Aries
>          Issue Type: Bug
>          Components: JNDI
>    Affects Versions: 0.2, 0.3
>            Reporter: Stephan Siano
>            Assignee: Alasdair Nottingham
>         Attachments:
> If the aries JNDI bundles are present in the environment, connections to remote JMX agents
fail. I could recreate the issue with a bundle containing only the line
> JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:rmi:///jndi/rmi://localhost:1717/jmxrmi"));
> in the start() method of the bundle activator (and nothing else).
> The bundle will start both on equinox and felix as long as the aries jndi bundles (I
tried version 0.2 and 0.3-SNAPSHOT) are not running and any java application that allows remote
JMX at that port is running (check with jconsole if you are unsure). It will not start as
soon as the jndi bundle is started. As far as I got in debugging this, the JMXConnectionFactory
is trying to do a JNDI lookup for the RMI connection and is delegated to the Aries JNDI coding,
that is trying to determine a bundle context for the call.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message