Saturday 12 January 2013

WebSphere Message Broker 8.0.1 and WebSphere MQ 7.5 together - com.ibm.broker.config.proxy.ConfigManagerProxyLoggedMQException: Could not connect to queue manager 'MB8QMGR' (MQ reason code 2495)

I was struggling to import/use any of the sample flows that come with the WebSphere Message Broker 8.0.1 Toolkit, and kept seeing the following exception: -

$ cat /home/wasadmin/IBM/wmbt80/workspace/.metadata/SamplePreparationWizard.log

Throwable occurred: com.ibm.broker.config.proxy.ConfigManagerProxyLoggedMQException: Could not connect to queue manager 'MB8QMGR' (MQ reason code 2495)
at com.ibm.broker.config.proxy.MQConnectionHelper.connectToMQ(Unknown Source)
at com.ibm.broker.config.proxy.MQSender.connect(Unknown Source)
at com.ibm.broker.config.proxy.MQSender.<init>(Unknown Source)
at com.ibm.broker.config.proxy.MQBrokerConnectionParameters.getSender(Unknown Source)
at com.ibm.broker.config.proxy.BrokerProxy.<init>(Unknown Source)
at com.ibm.broker.config.proxy.BrokerProxy.getInstance(Unknown Source)
at com.ibm.etools.mft.eou.operations.sampleprepwiz.ToolkitConnectedOperation.checkToolkitConnection(Unknown Source)
at com.ibm.etools.mft.eou.operations.sampleprepwiz.ToolkitConnectedOperation.run(Unknown Source)
at com.ibm.etools.mft.eou.operations.EouCommands.checkToolkitConnection(Unknown Source)
at com.ibm.etools.mft.eou.operations.LinuxEouCommands.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Jan 12, 2013 2:32:16 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction


Digging further, I also found that I was unable to connect to the Broker / Queue Manager from within the Toolkit: -



but the exception was FAR more useful: -


Following the recommendations in the dialogue: -

echo $LD_LIBRARY_PATH

/opt/ibm/mqsi/8.0.0.1/jre16/lib/amd64:/opt/ibm/mqsi/8.0.0.1/jre16/lib/amd64/classic:/opt/ibm/mqsi/8.0.0.1/xml4c/lib:/opt/ibm/mqsi/8.0.0.1/lib:/opt/ibm/mqsi/8.0.0.1/bin:/opt/ibm/mqsi/8.0.0.1/ODBC/V6.0/lib:/opt/ibm/mqsi/8.0.0.1/xlxpc/lib:/opt/ibm/mqsi/8.0.0.1/dfdlc/lib

export LD_LIBRARY_PATH=/opt/mqm/java/lib:$LD_LIBRARY_PATH
$ echo $LD_LIBRARY_PATH

/opt/mqm/java/lib:/opt/ibm/mqsi/8.0.0.1/jre16/lib/amd64:/opt/ibm/mqsi/8.0.0.1/jre16/lib/amd64/classic:/opt/ibm/mqsi/8.0.0.1/xml4c/lib:/opt/ibm/mqsi/8.0.0.1/lib:/opt/ibm/mqsi/8.0.0.1/bin:/opt/ibm/mqsi/8.0.0.1/ODBC/V6.0/lib:/opt/ibm/mqsi/8.0.0.1/xlxpc/lib:/opt/ibm/mqsi/8.0.0.1/dfdlc/lib

Having done this, when I re-started Eclipse and attempted to connect to my Broker - this time it worked out of the box.

Additionally, I was able to import and use the sample flow.

Another hurdle vaulted …….

No comments:

Visual Studio Code - Wow 🙀

Why did I not know that I can merely hit [cmd] [p]  to bring up a search box allowing me to search my project e.g. a repo cloned from GitHub...