Author |
Message
|
benethridge |
Posted: Thu Feb 17, 2005 2:46 pm Post subject: MQJE001: Completion Code 2, Reason 2009 |
|
|
Newbie
Joined: 17 Feb 2005 Posts: 7
|
Hi, all.
We are getting the error shown in the subject. Apparently, this is a pretty common error in MQ. This is in WSAD 5.0,
using the classes in the com.ibm.mq package. Here is what we know so far:
( ) We have two client pc's which run the WSAD app and connect successfully to a server-based MQ Queue, so we know the
server queue is up and running solid. All the other pc's we've configure don't connect successfully.
( ) The pc's which work were both configured a while (several months?) ago. The pc's which don't were configured recently, so there may be some version differences in the MQ software.
( ) The properties file values for the MQ parameters (MQHost, MQChannel, MQPort, etc.) are the same on the succeeding pc's and the failing pc's. Several programmers have checked these, comparing them on the good pc's and the bad, so we don't think we spelled anything wrong.
( ) On the failing pc's the error always occurs on this line:
MQQueueManager qMgr = new MQQueueManager(imsQMgrName);
...and this is always on a first attempt to make a connection.
( ) A debug step-through shows all variables correctly loading from the properties file values.
( ) We believe that this is exactly the
same app code on the failing pc's as it is on the succeeding pc's.
Because this last one is just a belief, at this point, I think I need to narrow down the problem a bit more, with tools. Are there downloadable tools
and simple client programs in java which I can use to do a simple connection test to the server queue?
I've looked over your downloads, but don't see one that jumps out at me yet.
Respectfully,
Ben |
|
Back to top |
|
 |
EddieA |
Posted: Thu Feb 17, 2005 3:04 pm Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
Quote: |
simple connection test to the server queue |
Is there connectivity between the boxes. Telnet to <MQHost> <MQPort>. The receiving MQ will throw an error, but it won't cause any harm.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
csmith28 |
Posted: Thu Feb 17, 2005 3:17 pm Post subject: |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
Can you run amqsputc from the Clients Servers?
From a DOS prompt:
Code: |
C:\> set MQSERVER=SVRCONN.CHL.NAME/TCP/hostname.domain.com
|
amqsputc should be in your ~WebSphere MQ\bin directory.
Code: |
amqsputc <QUEUE.NAME> <MQMGRNAME> |
You might also want to have a look at this active thread:
http://www.mqseries.net/phpBB2/viewtopic.php?t=10678&postdays=0&postorder=asc&start=15 _________________ Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
Back to top |
|
 |
bower5932 |
Posted: Thu Feb 17, 2005 7:51 pm Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
From the active thread that csmith28 pointed you to, I believe this is a back level version of a jar file. I'd also double-check that your WMQ is at least at CSD 4. |
|
Back to top |
|
 |
benethridge |
Posted: Fri Feb 18, 2005 2:09 am Post subject: |
|
|
Newbie
Joined: 17 Feb 2005 Posts: 7
|
Thanks, everyone, for the troubleshooting tips. I'll try them out today.
bower5932 wrote: |
I'd also double-check that your WMQ is at least at CSD 4. |
Sorry, but I'm not familiar with all the MQ acronyms yet. This is a version level of "WebSphere Message Queuing", right?
If so, why does it need to be at that level?
Ben |
|
Back to top |
|
 |
bower5932 |
Posted: Fri Feb 18, 2005 4:18 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
mqver will give you the level of code you are running. Why does it need to be at least CSD 4? I've seen numerous connectivity problems (especially with WAS/WSAD) that were fixed with CSD 4. |
|
Back to top |
|
 |
benethridge |
Posted: Fri Feb 18, 2005 5:36 am Post subject: |
|
|
Newbie
Joined: 17 Feb 2005 Posts: 7
|
Thanks.
mqver shows:
Name: WebSphere MQ
Version: 530
CMVC Level: p000-L021011
BuildType: IKAP - (Production)
However, I'm not certain that this is in the classpath such that WSAD is using it. How can I tell what version WSAD is using?
Also, for the amqsputc command, what's its synax? (I've looked around a bit, but not finding it yet.
The parameters I have that I hope I can map to amqsputc's parameters, similar to what you show above in this thread, are:
MQHost=LPBEN
MQChannel=MQMP.CLNTCBEN.CHL01
MQPort=1414
IMSQueueManager=MQMP
IMSQueue=MQMP.IBEN.BRIDGE01
MessageWaitInterval=15
Ben |
|
Back to top |
|
 |
bower5932 |
Posted: Fri Feb 18, 2005 8:04 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
The mqver indicates that you don't have CSD4 installed. Here is mine:
Code: |
C:\>mqver
Name: WebSphere MQ
Version: 530.7 CSD07
CMVC level: p530-07-L040527
BuildType: IKAP - (Production) |
You can get the latest fixes from:
http://www-306.ibm.com/software/integration/mqfamily/support/summary/
As far as using amqsputc, it requires an MQSERVER environment variable:
set MQSERVER=channel/protocol/host(port)
so,
set MQSERVER=MQMP.CLNTCBEN.CHL01/TCP/LPBEN
you can leave off the port since it defaults to 1414. The actual program requires a queue/qmgr:
amqsputc MQMP.IBEN.BRIDGE01 MQMP
I think I have all of the parameters right based on your append, but I may have missed a typo. |
|
Back to top |
|
 |
benethridge |
Posted: Fri Feb 18, 2005 8:38 am Post subject: |
|
|
Newbie
Joined: 17 Feb 2005 Posts: 7
|
|
Back to top |
|
 |
benethridge |
Posted: Fri Feb 18, 2005 10:28 am Post subject: |
|
|
Newbie
Joined: 17 Feb 2005 Posts: 7
|
We have WSAD running fine now as well. We were tipped off to some updated MQSeries jars, which we used to replace the older ones that came with orig WSAD CD (5.0).
I suspect that this will turn out have come from a WSAD or MQ fixpack along the lines of what you explain above.
Thanks, again!
Ben |
|
Back to top |
|
 |
|