aries-dev mailing list archives

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


Alasdair Nottingham commented on ARIES-554:


You are right, the CT doesn't seem to test for this, but it is wrong. I was going to apply
your patch and commit, but I started to look at the code and decided there were other issues
here, such as potential class consistency errors. So I am going to put a different fix in,
which will make the code a little more sane.

> 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
>         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.
For more information on JIRA, see:


View raw message