[ 
https://issues.apache.org/jira/browse/ARIES-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129678#comment-13129678
 ] 

Alasdair Nottingham commented on ARIES-554:
-------------------------------------------

Generally we do releases when someone says they would like one. The last one we 
were asked to do was for the JPA module which has been more challenging than we 
thought. Until the JPA release is live it doesn't make sense to do a JNDI 
release.

So if you would like a release I suggest you send an email to 
[email protected] and ask for one and we will see what we can do.
                
> aries JNDI bundle breaks remote JMX clients via RMI
> ---------------------------------------------------
>
>                 Key: ARIES-554
>                 URL: https://issues.apache.org/jira/browse/ARIES-554
>             Project: Aries
>          Issue Type: Bug
>          Components: JNDI
>    Affects Versions: 0.2, 0.3
>            Reporter: Stephan Siano
>            Assignee: Alasdair Nottingham
>         Attachments: Utils.java.patch
>
>
> 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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to