| Author |
Message
|
| vjakka |
 Posted: Tue Feb 26, 2002 7:27 am Post subject: |
 |
|
Newbie
Joined: 25 Feb 2002
Posts: 4
|
Am trying to connect to a remote queue manager and I end up getting this error:
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009
MQJE001: Completion Code 2, Reason 2009
An MQSeries error occurred :Completion code 2Reason code 2009
Can someone help me out please.
Thanks,
Venkat
|
|
| Back to top |
|
 |
| StefanSievert |
| Posted: Tue Feb 26, 2002 10:56 am Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Feb 26, 2002 12:37 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7716
|
I once spent a couple hours on this one till we noticed that the channl name being set in the program was CLIENTQMGR1 instead of CLIENT.QMGR1.
(I know, I know, it looks painfully obvious now......)
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| vjakka |
| Posted: Wed Feb 27, 2002 7:36 am Post subject: |
|
|
Newbie
Joined: 25 Feb 2002
Posts: 4
|
Thank you Stefan and Peter.
Even though I made sure that all the MQ Environment variables are set to the correct names (exactly)am still getting the same problem.
The other thing is that the MQManager, Queue and the Channel all are on a remote server. Is it right trying to connect directly from my localhost.
please advise.
Thanks,
Venkat |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Wed Feb 27, 2002 7:51 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
Hi,
In our setup (with security exits), the connections are broken with reason code 2009... meaning connection_broken.
This occurs if any of the required credentials are wrong.
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| drivett |
| Posted: Thu Apr 04, 2002 3:40 am Post subject: |
|
|
Newbie
Joined: 03 Apr 2002
Posts: 7
Location: Gimlet e-solutions
|
Hi,
I had this problem when using multiple Queue Managers. Make sure you set the MQEnvironment.port to the specific port the Queue Manager is listening on (get this from the listener properties) |
|
| Back to top |
|
|
| Ning Xiao |
| Posted: Mon Apr 15, 2002 10:55 am Post subject: |
|
|
Newbie
Joined: 14 Apr 2002
Posts: 1
|
I ran into the same error and it turned out that on the server end, when creating the channel, I mistakenly selected Server Channel instead of Server Connection Channel.
Ning |
|
| Back to top |
|
|
|
|
