[
https://issues.apache.org/jira/browse/ARTEMIS-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18009935#comment-18009935
]
Grzegorz Grzybek edited comment on ARTEMIS-5427 at 8/1/25 3:58 PM:
-------------------------------------------------------------------
For this issue to be fixed we need these:
On Jolokia side:
* release Jolokia 2.3.0 with
https://github.com/jolokia/jolokia/commit/6e0df9808972ffd12c0b11ca8c4c4da5682a00a4
* release Jolokia Integration 0.6.0 with
https://github.com/jolokia/jolokia-integration/issues/1
On broker side we assume two Jolokia agent deployments:
* Jolokia JVM Agent with {{-javaagent}} in {{etc/artemis.profile}} -
[{{jolokia-integration-artemis-0.6.0.jar}}|https://repo1.maven.org/maven2/org/jolokia/integration/jolokia-integration-artemis/0.6.0/jolokia-integration-artemis-0.6.0.jar]
would have to be added to {{${artemis.home}/lib}}
* Jolokia WAR Agent where Hawtio is used in activemq-artemis-console - this WAR
would need additional
[{{jolokia-integration-artemis-0.6.0.jar}}|https://repo1.maven.org/maven2/org/jolokia/integration/jolokia-integration-artemis/0.6.0/jolokia-integration-artemis-0.6.0.jar]
*and*
[{{jolokia-server-detector-2.3.0.jar}}|https://repo1.maven.org/maven2/org/jolokia/jolokia-server-detector/2.3.0/jolokia-server-detector-2.3.0.jar]
WAR deployment is easy - you don't have to tweak {{etc/artemis.profile}} - you
just need to have activemq-artemis-console.war with additional
jolokia-server-detector-2.3.0.jar.
[~jbertram] for {{-javaagent}} deployments here are my tested options:
h3. with Jolokia own JAAS authenticator:
{noformat}
JAVA_ARGS="$JAVA_ARGS
-javaagent:/home/ggrzybek/.m2/repository/org/jolokia/jolokia-agent-jvm/2.3.0/jolokia-agent-jvm-2.3.0-javaagent.jar=authMode=jaas,realm=activemq,port=7778,protocol=http"
{noformat}
h3. with Artemis authenticator (needs ARTEMIS-5587)
{noformat}
JAVA_ARGS="$JAVA_ARGS -DhttpServerAuthenticator.realm=activemq
-DhttpServerAuthenticator.requestSubjectAttribute=org.jolokia.jaasSubject
-javaagent:/home/ggrzybek/.m2/repository/org/jolokia/jolokia-agent-jvm/2.3.0/jolokia-agent-jvm-2.3.0-javaagent.jar=authClass=org.apache.activemq.artemis.spi.core.security.jaas.HttpServerAuthenticator,port=7778,protocol=http"
{noformat}
Old (management.xml) and new (broker.xml) RBAC differs only with this option:
{noformat}
-Djavax.management.builder.initial=org.apache.activemq.artemis.core.server.management.ArtemisRbacMBeanServerBuilder
{noformat}
was (Author: gzres):
For this issue to be fixed we need these:
On Jolokia side:
* release Jolokia 2.3.0 with
https://github.com/jolokia/jolokia/commit/6e0df9808972ffd12c0b11ca8c4c4da5682a00a4
* release Jolokia Integration 0.6.0 with
https://github.com/jolokia/jolokia-integration/issues/1
On broker side we assume two Jolokia agent deployments:
* Jolokia JVM Agent with {{-javaagent}} in {{etc/artemis.profile}} -
[{{jolokia-integration-artemis-0.6.0.jar}}|https://repo1.maven.org/maven2/org/jolokia/integration/jolokia-integration-artemis/0.6.0/jolokia-integration-artemis-0.6.0.jar]
would have to be added to {{${artemis.home}/lib}}
* Jolokia WAR Agent where Hawtio is used in activemq-artemis-console - this WAR
would need additional
[{{jolokia-integration-artemis-0.6.0.jar}}|https://repo1.maven.org/maven2/org/jolokia/integration/jolokia-integration-artemis/0.6.0/jolokia-integration-artemis-0.6.0.jar]
*and*
[{{jolokia-server-detector-2.3.0.jar}}|https://repo1.maven.org/maven2/org/jolokia/jolokia-server-detector/2.3.0/jolokia-server-detector-2.3.0.jar]
> Integrate Jolokia's MBeanInfo cache
> -----------------------------------
>
> Key: ARTEMIS-5427
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5427
> Project: ActiveMQ Artemis
> Issue Type: Task
> Components: Web Console
> Reporter: Justin Bertram
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> According to the [Jolokia
> documentation|https://jolokia.org/reference/html/manual/extensions.html#_mbeaninfo_cache]
> it's possible to reduce the JSON payload returned by Jolokia to, for
> example, the web console. However, we must provide a
> [{{org.jolokia.service.jmx.api.CacheKeyProvider}}|https://github.com/jolokia/jolokia/blob/main/service/jmx/src/main/java/org/jolokia/service/jmx/api/CacheKeyProvider.java]
> implementation and make it available via a service loader (e.g.
> [here|https://github.com/jolokia/jolokia/blob/main/service/jmx/src/main/resources/META-INF/jolokia/services-default]).
> We must also pass the {{listCache=true}} URL parameter from the web console.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
