hawtio, artemis and WildFly - plugin for monitoring messaging configuration (?) problem

[kot.filemon]

I have ActiveMQ Artemis embedded to WildFly10 (as it comes) and want to monitor it via Hawt.io.

What I did:

• ActiveMQ Artemis is configured and running
• I dropped hawtio.war to deployment directory.
• I dropped builded by maven artemis-plugin with name chanaged just to artemis-plugin.war
• I even dropped jolokia.war

I tried with the standalone jar - made a plugin directory and put artemis-plugin.war there.

when I connect to jolokia I get CPU usage (and stuff like that) for WildFly, I can see, via JMX the queue, but still, to success with Artemis.

hawtio doesnot recognize the pluginhawtio doesnot recognize the plugin however it got loaded:

[main] INFO org.eclipse.jetty.webapp.WebAppContext - An Artemis plugin at http://0.0.0.0:8081/artemis-plugin [main] INFO jetty - Added 3rd party plugin with context-path: /artemis-plugin Added 3rd party plugin with context-path: /artemis-plugin 

I donot have 'Artemis' tab. , going to http://0.0.0.0:8081/artemis-plugin shows me the dir:

Directory: /artemis-plugin/

META-INF/ 4096 bytes Aug 4, 2016 10:41:10 AM 
WEB-INF/ 4096 bytes Aug 4, 2016 10:41:10 AM 
log4j.properties 215 bytes Aug 3, 2016 3:39:10 PM p
lugin/ 4096 bytes Aug 4, 2016 10:41:09 AM 

Any ideas? what I am doing wrong?

[jbertram]

Try adding this to the Artemis configuration:

<management jmx-enabled="true"/>

[bligny]

By adding the line:

<management jmx-enabled="true"/>

I am now able to have the Artemis plugin working (with Wildfly 10).
I do see the Artemis tab, I do see the tree with the queues. Nice !

However, the actions such as "create" (queue/topic), "browse" and "send" are not working. No real error but yet not effect :-(

As these "special" operations are not exposed in JMX (and cannot therefore be invoked via jolokia like other standard JMX operations), I would like to know if such operations are supposed to work also in Wildfly (or in contrary are implemented specifically for a standalone artemis distribution)

Thx in advance

PS: I did fill the credentials security settings in the preferences pane of artemis.

And the credential i am using has the sufficient privileges:

<server name="default">
  <management jmx-enabled="true"/>

  <security-setting name="#">
  ...
  <role name="admin" manage="true" delete-non-durable-queue="true" create-non-durable-queue="true" delete-durable-queue="true" create-durable-queue="true" consume="true" send="true"/>
  </security-setting>

[bligny]

For information, Wildfly 10 is bundled with Artemis 1.1, while the hawtio-artemis plugin is not compatible with this version :-(

Is there a version compatible with Artemis version 1.1.0? · Issue #17 · rh-messaging/artemis-hawtio · GitHub

Sight...

[jbertram]

I suppose I misunderstood what you wanted to do based on your original comment.  You indicated you wanted to "monitor" Artemis which I took to mean that you just wanted read-only operations.  If you really want to "manage" the broker (i.e. do read and write operations like creating queues, etc.) then you should use the Wildfly management layer as it will take care of updating the XML configuration e.g. when a queue is created.  There's lots of ways to interact with the Wildfly management layer (e.g. HTTP interface, CLI, etc.).  You should also be able to use JConsole or HawtIO (although I haven't tried it) as the management layer is exposed via MBeans.  If you don't want to use the Wildfly management layer and you would really like to use the hawtio-artemis plugin then I would recommend running Artemis independently of Wildfly.