rce)
> at my.package.JmxAccessPaxTest.test_jmxAccess(JmxAccessPaxTest.java:47)
>
>
> Martin
>
> --
> *From:* Achim Nierbeck
> *To:* Martin Lichtin
> *Cc:* "user@karaf.apache.org"
> *Sent:* Monday, March 23, 2015 3:56 PM
> *Subject:* Re
.apache.org"
Sent: Monday, March 23, 2015 3:56 PM
Subject: Re: Is local access to MBeans also protected
Hi,
actually I think an internal access should always be possible, you're in the
same container, right.
About the strange behavior of not beeing able to access local jmx beans,
Hi,
actually I think an internal access should always be possible, you're in
the same container, right.
About the strange behavior of not beeing able to access local jmx beans,
that's what I regard an issue :-)
regards, Achim
2015-03-22 15:13 GMT+01:00 Martin Lichtin :
> Maybe I'm missing so
Maybe I'm missing something, but a simple Pax run shows that MBeans are
accessible:
E.g:
@RunWith(PaxExam.class)
@ExamReactorStrategy(PerClass.class)
public class JmxAccessPaxTest {
public static final String GROUP_ID = "org.apache.karaf";
public static final String ARTIFACT_ID = "apache-kar
Hi,
I think I've seen this behavior too. AFAIC this is a bug.
Do you happen to have a scenario where it's really reproducible?
Could you open a issue for it?
Thanks, Achim
2015-03-10 14:23 GMT+01:00 Martin Lichtin :
> I understand that access to MBeans is protected via RBAC mechanism:
>
>h
I understand that access to MBeans is protected via RBAC mechanism:
http://karaf.apache.org/manual/latest/users-guide/monitoring.html
However, is this also the case for code running inside Karaf?
E.g. when doing
MBeanServer mbs = ManagementFactory.getPlatformMBeanServer();
it seems I c
