Hello there. I am trying to find a complete guide on how to setup activemq monitoring. There is surely allot of info out there but it seems to be all over the place. Any precise documentation I can refer to?
Apache Activemq 5.16.4 Download
Hello there. I am trying to find a complete guide on how to setup activemq monitoring. There is surely allot of info out there but it seems to be all over the place. Any precise documentation I can refer to?
Apache Activemq 5.16.4 Download
The following was done:
1) Created jndi.properties and placed it (a) as a jar file in $SPLUNK_HOME\etc\apps\jms_ta\bin\lib\ (jndi.properties is in the root) and (b) at apache-activemq-5.13.3\conf
I was having the same issue and just wanted to pass along the solution in case anyone comes across it again. The solution was to create a jar file with the jndi.properties file, this allowed the properties to be read. And in the case of ActiveMQ 15.5.0 the property for connectionFactoryNames was added as shown below:
//-----
java.naming.factory.initial = org.apache.activemq.jndi.ActiveMQInitialContextFactory
connectionFactoryNames = connectionFactory, queueConnectionFactory, topicConnectionFactry
java.naming.provider.url = tcp://localhost:61616
queue.MyQueue = EVENTS.Q
//-----
I am testing an ActiveMQ with SoapUI - HermesJMS but I got the error "baseDirectory is not a valid property for org.apache.activemq.ActiveMQConnectionFactory - removed". After I selected the plug-in ActivateMQ, I cannot open the created session to add properties or change the properties.
On the Green Host, connected as root, change directory to /opt and expand (untar) the apache-activemq-5.5.1-bin.tar.gz file, to create the /opt/apache-activemq-5.5.1 subdirectory. Then use the chown command to change the ownership of the ActiveMQ directory and files from root to user01
Rapid7's security team looked into CVE-2023-46604 and examined the exploit code available to the public. During their testing, they found that the activemq.log file recorded a single line that confirmed the successful use of CVE-2023-46604. In this specific case, the individual responsible (in this instance, a researcher) operated from the IP address 192[.]168[.]86[.]35 and targeted TCP port 61616. It's important to note that the level of detail in the log entries can be different, depending on the logging settings, which can be adjusted as needed.
caa09b180b