karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dillon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-3147) Local JMX connect is not possible
Date Tue, 31 Mar 2015 22:55:54 GMT

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

Jason Dillon commented on KARAF-3147:
-------------------------------------

Seems like the _guard_ is done in the wrong place?  Seems like it should be done on the exposed
remote JMX connection's reference to the MBeanServer, not on the platform installed MBeanServer?
 I'd expect an in-JVM process could still get access to the platform MBeanServer and inspect
it if the feature isn't installed and if installed, w/o needing to provide authentication
details.

So perhaps its simpler to wrap the MBeanServer exposed in the connector with proxy that guards,
and leave the platform mbeanserver alone?

> Local JMX connect is not possible
> ---------------------------------
>
>                 Key: KARAF-3147
>                 URL: https://issues.apache.org/jira/browse/KARAF-3147
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 3.0.1
>         Environment: OS X, JDK 7
>            Reporter: Achim Nierbeck
>            Assignee: Jean-Baptiste Onofré
>            Priority: Critical
>             Fix For: 4.0.0, 2.4.2, 3.0.4
>
>
> With neither local process nor with remote jmx connection 
> {code}
> service:jmx:rmi://0.0.0.0:44444/jndi/rmi://0.0.0.0:1099/karaf-root
> {code}
> it's possible to connect to Karaf via JMX. 
> Neither JConsole nor VisualVM is usable. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message