apache MQ giving error in log file: nullpointerexception

[CommunityUser]

Hi,

This is the only error I see, when I try running the active mq extension.

[pool-12-thread-1] 24 Nov 2014 06:28:41,026 ERROR ActiveMQMonitorTask - Error JMX-ing into the server :: localhost
java.lang.NullPointerException

Is there any other method by which I can monitor my apache mq data.

We have apache mq running as a wrapper service. But when I give javaagent in the wrapper config the mq does not start. 

Why is the extension not working?

Please also let me know what should I fill in the config.yml file. I have apache mq running in my locathost and port 1616 is enabled for jmx. There are no username and password.

How should I configure? 

[Arun_Dasetty]

Hi Nagendra,

yes you could monitor as jvm and you should jmx in node dashboard if active mq startup script is properly configured with -javagent entry , if you have trouble in configuring -javaagent entry startup script you can start activemq as follows with agent:

shell> cd <activemq_install_dir>/bin

shell> java -javaagent:<agent_dir>/javaagent.jar -jar run.jar start

Regarding extension error, We would like to check basic settings in logs and machine agent version and will suggest to raise help ticket at help@appdynamics.com so the extension experts team will debug from there. Hope that is fine with you.

Can you  please send the following logs:

- zipped version of logs directory from <machineagent_dir>/logs paht and <machineagent_dir>/monitors/ApacheMQMonitor folder 

- after capturing logs above now change "<logger leve="info"/>>  info to debug in log4j.xml at <machineagent_dir>/conf/logging path and collect machineagent.log after running for 10 minutes and attach the logs in this post.

Regarding other query did you mean you have left user/.password values as blank in monitor.xml and config.yml file if so please provide and see how it goes with restart of machien agent.

Regards,

Arun

[CommunityUser · Accepted solution]

Thanks kumar,

I figured it out. I was giving the path of config.yml wrongly. Now the extension is working fine.