Major Lloyd, David J. <CTR> <David.Lloyd@tsa.dhs.gov>
9:26 AM (3 hours ago)
to me, matt.batterham, Jan, Shingyip, Terry
Thank you for checking in. You are one step ahead of me. Just got back to that after I got sidetracked on other ongoing work we have here. Unfortunately no. The alter statement you sent me was applied and both the queue manager and Lamaxu were restarted, however it did not help, same null pointer exception as before and I still only see 2 queues on one of our servers.
I have verified on the server which is only displaying 2 queues in the JMX jconsole application that Lamaxu is in fact connecting up and successfully pulling data on channels, topics, queues, queue manager status etc, because they show up in your log files. The status information is not showing up in the JMX MBean, which is what I need to connect to SolarWinds. I also tried the agent on a different test server we have and get similar results, but incomplete information is showing up in the JMX MBean.
The error is the same as before on the test server
2015-11-09 15:17:52 ERROR Sweeper:140 - [DEMO data collector] - Exception encountered collecting data from message broker CSDEVISB51
java.lang.NullPointerException
at com.qm.lamaxu.messagebroker.mq.WebSphereMQQueueManager.getAllObjects(WebSphereMQQueueManager.java:181)
at com.qm.lamaxu.cache.Sweeper.captureObjectData(Sweeper.java:68)
at com.qm.lamaxu.cache.Sweeper.run(Sweeper.java:130)
at java.lang.Thread.run(Thread.java:745)
David