Websphere MQ V6.0 plugin

VMware Cloud Community

Hi,
I'm trying to use the websphere_mq-plugin and getting the following exception

2008-12-17 13:31:08,812 ERROR [Thread-0] [AgentDaemon] Critical error running agent
java.lang.NoSuchMethodError: org.hyperic.hq.plugin.wsmq.MQSeriesProductPlugin.getProperty(Ljava/lang/String;)Ljava/lang/String;
at org.hyperic.hq.plugin.wsmq.MQSeriesProductPlugin.getClassPath(Unknown Source)
at org.hyperic.hq.product.ProductPluginManager.registerPluginJar(ProductPluginManager.java:975)
at org.hyperic.hq.product.ProductPluginManager.registerPluginJar(ProductPluginManager.java:741)
at org.hyperic.hq.product.ProductPluginManager.registerPlugins(ProductPluginManager.java:829)
at org.hyperic.hq.agent.server.AgentDaemon.startPluginManagers(AgentDaemon.java:682)
at org.hyperic.hq.agent.server.AgentDaemon.start(AgentDaemon.java:827)
at org.hyperic.hq.agent.server.AgentDaemon$RunnableAgent.run(AgentDaemon.java:925)
at java.lang.Thread.run(Unknown Source)
2008-12-17 13:31:08,828 DEBUG [Thread-0] [AgentDaemon] Notifying that agent startup failed
2008-12-17 13:31:08,859 INFO [Thread-0] [AgentDaemon] Agent shut down
2008-12-17 13:31:08,859 ERROR [Thread-0] [AgentDaemon] Agent startup error:
org.hyperic.hq.agent.server.AgentStartException: Critical shutdown
at org.hyperic.hq.agent.server.AgentDaemon.start(AgentDaemon.java:861)
at org.hyperic.hq.agent.server.AgentDaemon$RunnableAgent.run(AgentDaemon.java:925)
at java.lang.Thread.run(Unknown Source)

I am running agent 4.0.1.

Any ideas?

Thanks

49 Replies

We have updated the plugin to 4.0.x version.
Please, download it again.

http://support.hyperic.com/download/attachments/57476142/websphere_mq-plugin.jar
http://support.hyperic.com/pages/viewpage.action?pageId=57476142

OK... I think we have got everything in place where it is supposed to be. The agent is running now but it doesn't quite get MQ into the inventory. The updated plugin is in place, the hqu gzip is in place on the server. Both were restarted.

This occurs when the inventory configuration properties are set with the Queue Manager name.

Error reported by Agent @ 10.40.2.22:2144: java.lang.UnsatisfiedLinkError: no mqjbnd05 in java.library.path

respectfully
BJ (Who works with Eitan)

Looks like an MQ classpath issue. I didn't do the MQ installation.... have to find where to set this in Windows.

HQ server version?
HQ agent version?
OS version?
MQ version?

Please, add this line to the agent.properties file:
log4j.logger.org.hyperic.hq.plugin.wsmq=DEBUG
Re-start the agent, and upload the agent log file.

Thank you.

HQ Server 4.0.1-EE from your trial, running on Ubuntu 8.04 2.6.24-22-generic SMP

hyperic-hq-agent-4.0.1-EE-905-win32 running on a Windows Server 2003 R2 SP 2 on a VMWare image on an AMD Athlon 64x2 dual core.

Websphere MQ is a version 6.0 trial installation.

I suspect that it can work if I get all the pieces in place corrrectly. I note a different version of Java in MQ vs the Agent.

Taking care of the debug statement now thanks

The log for the last run....

I haven't actually looked at this yet... but if there's something obvious (like I am using the wrong file somewhere somehow) please point it out.

Thanks
BJ

Please, use the attached plugin, and try again.

Thanks.

OK... I have to look at this one too... I haven't seen that it is greatly different.

I have to go home soon. I may have a go at installing on my home systems and have a look, but I suspect we will not get much further with this. The home systems are all Linux. Probably it'll all work 🙂

respectfully
BJ

Where on my windows is /etc/plugin.xml?

¿¿ /etc/plugin.xml ??

Please use this document to install the plugin:
http://support.hyperic.com/display/DOC/Deploy+Plugin

Freshly installed the WS MQ 6 server - This one is mine.
Installed the client
Placed the plugin
Reinstalled the Hyperic server-4.0.2-EE
Put the com.ibm.mq.pcf-6.1.jar file in the MQ server

Autodiscovery fails - silently so far, but the java command -
"java -jar pdk/lib/hq-product.jar -Dplugins.include=websphere_mq -m discover -a metrics -Dlog=debug > result.log

... shows that we have discovered everything down to the queues.... when commanded that way.

I've tried everything I can think of. I removed the Websphere MQ 5 from the inventory. I pulled the old mqseries-plugin from the bundle\agent-4.0.2-EE-940 plugins.

At wits end.

Could you attach the result.log or the agent.log?

Thanks.

Message was edited by: laullon

Darn it!

I attached this to the last message... Should have checked after sending.

I don't see it so I will try again.

respectfully
BJ

The only error I saw in this appears to relate to the channels. Since no channel was defined yet for this trial installation, that seemed a reasonable thing.

If it doesn't display anything because of that error I'd be astonished. I will push the agent log in a couple of hours. I looked at it and it was ,,, uninteresting. I had requested a discovery from the console and it dutifully reports all the other bits but there is no mention of any error or of MQ IIRC.

Only thing I am thinking is whether my removal of the "MQ 5" it initially discovered could have persuaded it to omit any subsequent discovery. I wiped the agent data directory and re-configured twice without result. Not sure how to do THAT with the console, though I deleted the machine and it appeared to be starting from scratch.

respectfully
BJ

Hi,

The "result.log" looks good.
Please try with this command:
java -jar pdk/lib/hq-product.jar -Dplugins.include=websphere_mq -mdiscover -ametric -Ddiscover.SYSTEMS=true -Dlog=debug > result.log
And attach the "result.log".

And then execute these steps:
1. Stop the agent
2. delete agent.log
3. edit agent.propteries and put this lines
discover.SYSTEMS=true
log4j.logger.org.hyperic.hq.plugin.wsmq=DEBUG
4. start the agent
5. wait 5 minutes
6. attach the agent.log

The plugin by default discard all "system.*" object, but setting the "discover.SYSTEMS" to true, these objects aren't discarded

Thanks.

Returning to the scene of the first problem I had with IBM... and starting from a much firmer knowledge of how the plugins work....

The java command gives us this result log and pops the following...

MQJE001: Completion code 2 Reason 2085

Which seems to mean something dumb in the WSMQ setup.

http://www.mqseries.net/phpBB2/viewtopic.php?t=655

In the agent log I see the Reason 2033 which is "queue empty" which is perfectly correct. The test WSMQ setup has nothing in its queues. The message is of course, one of the more annoying exceptions as it is going to pop up all the time.

Otherwise seems sort of normal. Except that there is no indication whatsoever, that it is discovering things in the UI. In order to get anywhere with it I moved the mqseries-plugin.jar to a .jar.old in both the server and the agent. It seems to get in the way ( MQ 5 is always autodiscovered by mistake ).

I am pursuing the first MQ error to see if I can't work out what its problem is. I am by no means an MQ wizard.

Thanks
BJ

OK.... so far no luck getting rid of the 2085. It is a demo version of WSMQ and it is the 6 series that I have to connect to on AIX. The folks maintaining that undoubtedly have it working nicely being specialists. I only have to get it to work at all here and show that it can. The problems don't seem to be preventing your plugin from seeing the queues and the queue manager I set up. Nothing shows up in the server though. Just the tick box for autodiscovery... but it isn't-doesn't.

respectfully
BJ

Please, try with attached version. This version solve some bug related with AIX

That's pretty good. I am still not getting autodiscovery but it isn't hard for me to configure a new server.

At the point it wants to connect to the "homebrew" queue manager and the "gozinta" queue (as I go through the final configuration steps) it throws up the 2033 error on the UI.

"The configuration has not been set for this resource due to: Invalid configuration: Error contacting resource: MQJE001 Completion code 2, Reason 2033"

That is the annoying "queue-empty" exception. People who program things so that EXPECTED conditions are exceptions annoy me greatly. It is sloppy programming on IBM's part.

Just my opinion. Which along with $3.00 will get you a long-black at the coffee shop.

🙂

I can live without autodiscovery here. It's a bell-whistle thing. They'll move to MQ 7 in time. If I could figure out a way to suppress the error message I'd be happier. We shouldn't have to adapt to their bad-practice.

The queues may not be empty when I start this up in production (or I can perhaps arrange for them not to be empty but that gets "ugly" in terms of customer relations.) .

respectfully
BJ

All

Websphere MQ V6.0 plugin