[
https://issues.apache.org/jira/browse/KARAF-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-2506.
-----------------------------------------
Resolution: Not a Problem
Now the documentation specifies to use the JMX service URL to connect to Karaf
(even locally, instead of use the Process ID).
> MBeans attributes are "unavailable"
> -----------------------------------
>
> Key: KARAF-2506
> URL: https://issues.apache.org/jira/browse/KARAF-2506
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
> Affects Versions: 3.0.0
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Critical
> Fix For: 3.0.1, 4.0.0
>
>
> Running Karaf 3.0.0-SNAPSHOT (trunk), and connecting jconsole, all Karaf
> MBeans attributes are displayed as "unavailable" in red.
> It's the case for:
> - bundles in org.apache.karaf:type=bundle
> - configs in org.apache.karaf:type=config
> - features and repositories in org.apache.karaf:type=feature
> - instances in org.apache.karaf:type=instances
> - kars in org.apache.karaf:type=kar
> - level in org.apache.karaf:type=log
> - exports and imports in org.apache.karaf:type=package
> - services in org.apache.karaf:type=service
> - all attributes in org.apache.karaf:type=system
> I'm checking if it's not some ACLs missing (as the JMX ACL check attributes
> using some operations name like get/set/is).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
