WebSphere MQ Adaptor Connection problem

, ,
1

Hello.

I have set up a sandbox to test the MQ Adaptor (v6) on IS 6.1 (WinXP) and I am attempting to create a test connection to a WebSphere MQ server (v5.3) on Win2k. I’m a totaly newbie when it comes to MQ, but the installation was straight forward, and the install verifications seemed to go off fine.
I have created a new queue manager (TESTQMANAGER) and also created a new server connection channel (SCC_TEST) via the MQ Explorer GUI. The queue manager and channel are both enabled/running.
When I attempt to create the connection to the queue manager in the “Adapters > WebSphere MQ Adapter > Configure Connection Type” screen of the wM Admin Console, I specify all of these required connection properties:
package: A_SANDBOX
folder name: A_SANDBOX.MQ_Playpen
connection name: TESTCONNECTION
queue manager name: TESTQMANAGER
host name: ip address of the host machine
TCP/IP port: 1414
server connection channel: SCC_TEST
CCSID: CP819

All of the other fields I either leave blank or leave at the default settings.
After saving the connection and trying to enable it, I receive this error message:

Error encountered

[ART.118.5042] Adapter Runtime (Connection): Unable to enable connection resource A_SANDBOX.MQ_Playpen:TESTCONNECTION.
[ART.118.5036] Adapter Runtime (Connection): Unable to configure connection manager.
Connection to Queue Manager TESTQMANAGER could not be initialized; cc=2,rc=2009.

Does anyone have any suggestions as to what the problem could be? The wM admin interface is very simple, so I’m assuming its an MQ settings problem. Its been a few days, and I’ve been unable to find any reference to these error messages online. I’m stumped.
Many thanks in advance!

-Chris

2

The “cc=2, rc=2009” error code is coming from MQ. There is an MQ error message reference available on the installation CDROM. Maybe that will give you an idea.

Mark

3

Chris,

I am not too familiar with v6.0 of MQ yet, but please be aware that the QMgr names etc are case sensitive, so you might want to doublecheck those. Furthermore is the port 1414 ok for the created channel?

For reason codes you can look here: [url=“http://www-306.ibm.com/software/integration/mqfamily/library/manuals/csqfao/CSQFAO1P.HTM”]IBM Products

-Jordy

4

Chris,

Did you make sure that your MQ Listeners are up and running?

Cheers!
Krishna

5

Thanks too all who responded, Mark, Jordy and Krishna.
Mark and Jordy: it was important to know that it was an MQ problem, and not a wM issue.

There were a few problems that I discovered:

  • First, the queue manager wasn’t part of the default cluster so I added it.
  • Second, the listener for the queue manager I created was configured with the same port as the default queue manager listener, preventing it from starting correctly. So I changed the port from the default (of 1414) to another port. (You were right Krishna, thanks!)
  • Third, the server connection channel wasn’t started because (I assume) of the listener port problem.

So, now that all of those things have been corrected, I am able to connect from the MQ Adaptor in the Admin Console without a problem!

The connection now shows up in Developer, and I’m off and running.

Thanks again!
-Chris

6

Chris - We have seen this 2009 reason code when the maximum number of connections available on that Queue Manager (in your case ‘TESTQMANAGER’) has been reached.

Actually this seems to be a problem on the webMethods side as we are not able to close connections once they have been opened.

Has anyone seen this with the WebSphere MQ Adapter v3.0 or 6.0?

7

Rajesh:
Can you set a timeout for the connections? I don’t see this as a configurable parameter in webMethods but perhaps on the MQ side?
…/cc

8

Chris - There is an “Inactive Lifetime” for pooled connections in the Adapter v3.0. Is this what you’re asking?

Also, have you noticed that the connections you open to MQ are not getting dropped? To look at the connection status in Unix, you can use the following command:

netstat -a|grep MqServerHostName

9

I just received a patch from webMethods support for MQAdapter version 6.

We were having problems with the Adapter not closing connections, and this patch addresses that problem. Thanks webMethods!

Here’s the readme for those interested:

       webMethods WebSphere MQ Adapter 6.0.0 Fix 1 

                     May 2004

This file provides important information for applying Fix 1 to
the webMethods WebSphere MQ Adapter 6.0.0. For release
information about the webMethods WebSphere MQ Adapter 6.0.0, see
the Release Notes in the
<integrationserverdirectory>\packages\WmMQAdapter\pub directory.

Contents:

1.0 Fix Name
2.0 Product(s) Affected
3.0 Fix Requirements
4.0 Fix Contents
5.0 Platform Support
6.0 Installation
7.0 Cautions and Warnings
8.0 Globalization Statement
9.0 Copyright
10.0 Contacting Us

1.0 Fix Name

webMethods WebSphere MQ Adapter 6.0.0 Fix 1

2.0 Product(s) Affected

This fix affects webMethods WebSphere MQ Adapter 6.0.0.

6.0 Fix Requirements

None

4.0 Fix Contents

1-QJXA3
The adapter will now disconnect from the Queue Manager
whenever a connection is closed. This will prevent stale
connections from exceeding the channel connection limit.

5.0 Platform Support

This fix is supported on all platforms supported by webMethods
WebSphere MQ Adapter 6.0.0.

6.0 Fix Installation

On Windows:

  1. Stop the webMethods Integration Server.

  2. Double-click the MQS_6-0_Fix1.zip file and extract the
    files into the same directory where your webMethods products
    are installed. For example, C:\Program Files\webMethods6

  3. Restart the webMethods Integration Server.

On UNIX:

  1. Stop the webMethods Integration Server.

  2. Cd into the directory where you installed the webMethods
    Integration Server. For example, /opt/webMethods6.

  3. Run “jar -xvf MQS_6-0_Fix1.zip”.

  4. Restart the webMethods Integration Server

7.0 Cautions and Warnings

None.

8.0 Globalization

webMethods WebSphere MQ Adapter 6.0.0 Fix 1 conforms to the
internationalization standards of webMethods and includes support
for operation in any country, locale or language. Support for
character encodings and proper formatting, display, and
validation of data (such as number and date formats) has been
provided throughout the product. webMethods WebSphere MQ
Adapter 6.0.0 is fully compliant with the requirements of the
Unicode Standard, version 2.1.8 (see http://www.unicode.org).

If you expect to display non-English data in your webMethods
tools, you need to ensure that an appropriate font is installed
in your operating environment. You should test to see if there
are hollow boxes or black squares where you would expect to see
non-English data, and if you see problems, modify your JRE
font.properties file to reference the font on your system.
Information on modifying your font.properties file can be
located on the Javasoft website and in the FAQ at
[url=“Display Problems”]http://www.unicode.org/help/display_problems.html[/url].

9.0 Copyright

webMethods Administrator, webMethods Broker, webMethods
Developer, webMethods Installer, webMethods Integration Server,
webMethods Mainframe, webMethods Manager, webMethods Modeler,
webMethods Monitor, webMethod