Yes, it works. And also the JVM_monitor-probe. Looks almost the same, but in the JVM_monitor-probe you have some more options in the monitoring. Maybe someone else can tell the exact different?
Both probes needs to be edited though, regarding running out of memory. Here is what you need to do:
tomcat probe internal used memory error (I think this goes for the JVM-probe as well)
This is how I did it:
1. Open up port 1099 in the firewall between your UIM-server and the ActiveMQ-server.
2. Now you need to activate the JMX-connector so the ActiveMQ-server starts listening to port 1099.
You do this in the XML-config, which you will find in the install directory for ActiveMQ.
In my case it's in here:
/opt/<activemq-dir>/conf/activemq.xml
This is what you need to change/add inbetween your "<Broker xmlns.."-tag:
………..…
………
<managementContext>
<managementContext createConnector="true" connectorPort="1099"/>
</managementContext>
……
………….
</broker>
3. Now you should start ActiveMQ:
- - cd /opt/<activemq-dir>/bin
- ./activemq start --- (If it's already started you need to stop it first with "./activemq stop")
4. Check that the server now is listening at port 1099
5. Now open up your Tomcat or JVM-probe and add the host with port 1099.
- Default User/Password is admin/admin (you should change this later).
6. When it's connected, it should look something like this:
If you still having problem, JMX might not be enabled by default in ActiveMQ. Then add this to the XML-config:
/opt/<activemq-dir>/conf/activemq.xml
<broker xmlns="..….brokerName="localhost" useJmx="true">
.......
.........
</broker>