CODEWITHSUNDEEP
activemq-classicjames
JackTheKnife
JackTheKnife

Reputation: 4154

How to monitor ActiveMQ queue in Apache James

We're using Apache James 3.0-beta4 which uses embedded ActiveMQ 5.5.0 for FIFO message queue, and sometimes messages get stuck. Therefore, we need to monitor it. Is there any way to monitor an ActiveMQ queue like message size and most recent message-id in the queue (if possible).

In the JAMES spring-server.xml I found that:

    <amq:broker useJmx="true" persistent="true" brokerName="james" dataDirectory="filesystem=file://var/store/activemq/brokers" useShutdownHook="false" schedulerSupport="false" id="broker">
        <amq:destinationPolicy>
            <amq:policyMap>
                <amq:policyEntries>
                    <!-- Support priority handling of messages -->
                    <!-- http://activemq.apache.org/how-can-i-support-priority-queues.html -->
                    <amq:policyEntry queue=">" prioritizedMessages="true"/>
                </amq:policyEntries>
            </amq:policyMap>
        </amq:destinationPolicy>
        <amq:managementContext>
            <amq:managementContext createConnector="false"/>
        </amq:managementContext>
        <amq:persistenceAdapter>
            <amq:amqPersistenceAdapter/>
        </amq:persistenceAdapter>
        <amq:plugins>
            <amq:statisticsBrokerPlugin/>
        </amq:plugins>
        <amq:transportConnectors>
            <amq:transportConnector uri="tcp://localhost:0" />
        </amq:transportConnectors>
    </amq:broker>

also one old part from readme:

    - Telnet Management has been removed in favor of JMX with client shell
    - More metrics counters available via JMX
   
...

  * Monitor via JMX (launch any JMX client and connect to URL=service:jmx:rmi:///jndi/rmi://localhost:9999/jmxrmi)

which is confusion on how to use it.

This is part of the bigger "monolith" project which now is recreated for microservices but still need to be supported ;) All was fine till mid of March.

Upvotes: 0

Views: 330

Answers (1)

Justin Bertram
Justin Bertram

Reputation: 35123

It looks like ActiveMQ management and monitoring is not possible because JMX is disabled.

Upvotes: 1

Related Questions