| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| 2058 problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| kuanhong |
 Posted: Fri Sep 18, 2009 12:35 am Post subject: 2058 problem |
 |
|
Newbie
Joined: 18 Sep 2009
Posts: 3
|
hi,
i am facing the problem below, hope someone can help here.
I am getting the MQ Exception: com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2058. MQJE036: Queue manager rejected connection attempt.
This problem is not due to wrong Queue manager name, as it only occurs about 2 -10 times out of 100 request. My suspect is the channels are all used up. Note that this is a multi-threaded Java MQSeries application.
I tried to increase the Channel settings in qm.ini, it doesnt seem to solve the problem as well.
Any idea? |
|
| Back to top |
|
 |
| WMBDEV1 |
| Posted: Fri Sep 18, 2009 12:46 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
Anything in the QM error logs?
If you suspect "the channels are all used up" have you tried doing a dis chstatus(your channel name) to check this? |
|
| Back to top |
|
|
| mvic |
| Posted: Mon Sep 21, 2009 9:01 am Post subject: Re: 2058 problem |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| 2058 from a client might mean the client has attempted to connect to a port, and the queue manager listening on that port is NOT the same queue manager name named in the code. |
|
| Back to top |
|
|
| kuanhong |
| Posted: Mon Sep 28, 2009 1:22 am Post subject: 2058 problem |
|
|
Newbie
Joined: 18 Sep 2009
Posts: 3
|
| Upon checking, QM error log does not show anything. The number of channel shown when doing chstatus seems ok, looks like i may be wrong to suspect the channel |
|
| Back to top |
|
|
| kuanhong |
| Posted: Mon Sep 28, 2009 1:29 am Post subject: Re: 2058 problem |
|
|
Newbie
Joined: 18 Sep 2009
Posts: 3
|
| mvic wrote: |
| 2058 from a client might mean the client has attempted to connect to a port, and the queue manager listening on that port is NOT the same queue manager name named in the code. |
i dont think its the wrong port problem, as this problem only happens 2-10 times out of 100 identical request (same set of input, code, etc). If its the wrong port, all the request would hit the reason 2058 problem. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
