-
1. Re: hawtio, artemis and WildFly - plugin for monitoring messaging configuration (?) problem
buehlmann Dec 11, 2017 3:04 AM (in response to kot.filemon)Have you managed to get this setup working? Maybe under Wildfly 11 (Artemis 1.5.5)?
-
2. Re: hawtio, artemis and WildFly - plugin for monitoring messaging configuration (?) problem
jbertram Dec 11, 2017 8:17 AM (in response to kot.filemon)Have you enabled JMX management in the embedded Artemis instance? I believe it's disabled by default because Wildfly has its own management layer.
-
3. Re: hawtio, artemis and WildFly - plugin for monitoring messaging configuration (?) problem
buehlmann Dec 12, 2017 5:23 AM (in response to jbertram)Good point! Now I enabled JMX Management in messaging Subsystem in EAP 7.1:
<subsystem xmlns="urn:jboss:domain:messaging-activemq:1.1"> <server name="default"> <management jmx-enabled="true"/> ... </server> </subsystem>
Now I can see the Artemis tab in Hawtio and the configured destinations:
... but I get errors when trying to show consumers, producers etc. And there is no button where I can manage the destinations or send messages like on standalone artemis installation..
What I've deployed with the corresponding log output:
1. Jolokia 1.3.7:
10:41:53,812 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "jolokia.war" (runtime-name: "jolokia.war")
10:41:54,425 INFO [io.undertow.servlet] (ServerService Thread Pool -- 72) jolokia-agent: No access restrictor found, access to any MBean is allowed
10:41:55,173 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0021: Registered web context: '/jolokia' for server 'default-server'
10:41:55,239 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "jolokia.war" (runtime-name : "jolokia.war")
2. Hawtio 1.5.6 default offline:
10:42:05,596 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "hawtio.war" (runtime-name: "hawtio.war")
10:42:07,095 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry log4j.jar in /content/hawtio.war/WEB-INF/lib/commons-logging-1.0.3.jar does not point to a valid jar for a Class-Path reference.
10:42:07,095 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry log4j-core.jar in /content/hawtio.war/WEB-INF/lib/commons-logging-1.0.3.jar does not point to a valid jar for a Class-Path reference.
10:42:07,126 INFO [org.jboss.as.pojo] (MSC service thread 1-8) WFLYPOJO0001: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions).
10:42:07,494 WARN [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0013: Deployment hawtio.war contains CDI annotations but no bean archive was found (no beans.xml or class with bean defining annotations was present).
INFO | ServerService Thread Pool -- 84 | Initialising hawtio services
INFO | ServerService Thread Pool -- 84 | Configuration will be discovered via JNDI
INFO | ServerService Thread Pool -- 84 | Welcome to hawtio 1.5.6 : http://hawt.io/ : Don't cha wish your console was hawt like me? ;-)
INFO | ServerService Thread Pool -- 84 | Using file upload directory: /tmp/uploads
10:42:07,569 INFO [io.undertow.servlet] (ServerService Thread Pool -- 84) Loading Blueprint contexts [vfs:/content/hawtio.war/WEB-INF/classes/OSGI-INF/blueprint/blueprint.xml, vfs:/content/hawtio.war/WEB-INF/lib/hawtio-aether-1.5.6.jar/OSGI-INF/blueprint/blueprint.xml, vfs:/content/hawtio.war/WEB-INF/lib/hawtio-core-1.5.6.jar/OSGI-INF/blueprint/blueprint.xml, vfs:/content/hawtio.war/WEB-INF/lib/hawtio-git-1.5.6.jar/OSGI-INF/blueprint/blueprint.xml, vfs:/content/hawtio.war/WEB-INF/lib/hawtio-json-schema-mbean-1.5.6.jar/OSGI-INF/blueprint/blueprint.xml, vfs:/content/hawtio.war/WEB-INF/lib/hawtio-local-jvm-mbean-1.5.6.jar/OSGI-INF/blueprint/blueprint.xml]
INFO | ServerService Thread Pool -- 84 | Connected to Log4j appender to trap logs with hawtio log plugin
INFO | ServerService Thread Pool -- 84 | hawtio using config directory: /home/bbuehlmann/.hawtio/config
INFO | ServerService Thread Pool -- 84 | git pull from remote config repo on startup is disabled
WARN | ServerService Thread Pool -- 84 | Local JVM discovery disabled as this JVM cannot access com.sun.tools.attach.VirtualMachine due to: com/sun/tools/attach/VirtualMachine
INFO | ServerService Thread Pool -- 84 | Initial proxy whitelist: [localhost, 127.0.0.1, 10.61.228.61]
INFO | ServerService Thread Pool -- 84 | Jolokia has not found any overriden configuration property passed at launch time; Default configuration values will be used.
INFO | ServerService Thread Pool -- 84 | Using MBean [hawtio:type=security,area=jmx,rank=0,name=HawtioDummyJMXSecurity] for role based access control
10:42:08,732 INFO [io.undertow.servlet] (ServerService Thread Pool -- 84) jolokia-agent: Using restrictor io.hawt.web.RBACRestrictor
10:42:09,139 INFO [io.undertow.servlet] (ServerService Thread Pool -- 84) jolokia-agent: Jolokia Discovery MBean registration is skipped because there is already one registered.
10:42:09,140 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 84) WFLYUT0021: Registered web context: '/hawtio' for server 'default-server'
10:42:09,154 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "hawtio.war" (runtime-name : "hawtio.war")
3. Artemis Hawtio Plugin from master (activemq-artemis/artemis-hawtio/artemis-plugin at master · apache/activemq-artemis · GitHub ):
INFO | default task-7 | Starting hawtio authentication filter, JAAS authentication disabled
10:42:24,233 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "artemis-plugin.war" (runtime-name: "artemis-plugin.war")
10:42:24,320 INFO [org.apache.activemq.hawtio.plugin.PluginContextListener] (ServerService Thread Pool -- 81) Initialized artemis-plugin plugin
10:42:24,324 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 81) WFLYUT0021: Registered web context: '/artemis-plugin' for server 'default-server'
10:42:24,336 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "artemis-plugin.war" (runtime-name : "artemis-plugin.war")
Hawtio web console output:
[ARTEMIS] plugin running [object Object]
[ARTEMIS] *************creating Artemis Console************
[Core] hawtio started
[RBAC] Using mbean hawtio:type=security,area=jmx,rank=0,name=HawtioDummyJMXSecurity for client-side role based access control
[ARTEMIS] init tree org.apache.activemq.artemis
[ARTEMIS] workspace tree has changed, lets reload the artemis tree
[ARTEMIS] tree=[object Object]
[ARTEMIS] folder=[object Object]
[ARTEMIS] %%%%%%DynaTreeNode<root-org.apache.activemq.artemis-Broker-"default">: '"default"'
[ARTEMIS] broker=org.apache.activemq.artemis:broker=Broker
-
4. Re: hawtio, artemis and WildFly - plugin for monitoring messaging configuration (?) problem
jbertram Dec 12, 2017 9:49 AM (in response to buehlmann)What version of Artemis is running in the container? If it doesn't match the version which you took the console from then I wouldn't expect it to work very well (if at all).
-
5. Re: hawtio, artemis and WildFly - plugin for monitoring messaging configuration (?) problem
buehlmann Dec 12, 2017 10:39 AM (in response to jbertram)That's what I thought.. EAP 7.1 Beta comes with Artemis 1.5.5 (1.5.5.002-redhat-1) embedded. I was not able to find out which version of the artemis-hawtio plugin is compatible with Artemis 1.5.5 because of the change of the Git repository. Could not find the Plugin under the Tag 1.5.5 in the Repository https://github.com/apache/activemq-artemis. It seems to be integrated from another repository (https://github.com/rh-messaging/artemis-hawtio?) in the past. But in this repository I could not find any correlation between the tags and the Artemis versions..
-
6. Re: hawtio, artemis and WildFly - plugin for monitoring messaging configuration (?) problem
jbertram Dec 12, 2017 10:50 AM (in response to buehlmann)As far as I know the Artemis web-console has always been targeted at 2.x (which is why you couldn't find it under the 1.5.5 tag). There were some significant changes between 1.5.x and 2.x so I wouldn't expect the web-console to work with 1.5.x.
In the past the console was integrated into AMQ (i.e. Red Hat's supported messaging platform based on ActiveMQ) from a separate repository, but the console was recently integrated into the upstream repository.