| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Getting inconsistent errors with queue manager. |
« View previous topic :: View next topic » |
| Author |
Message
|
| prithun |
 Posted: Wed Apr 20, 2005 8:26 am Post subject: Getting inconsistent errors with queue manager. |
 |
|
Apprentice
Joined: 08 Apr 2005
Posts: 33
|
I am using multiple threads to get messages from the queue. But sometimes only the first thread is able to get messages and the other threads fail saying
Cannot connect to QMGR(queue manager). Reason code is 2059
I am using MQOO_INPUT_SHARED option to connect to the queue.
The application that puts the message on to the queue is not multithreaded and is not connected with the SHARED option.
Also I am using setConnectOptions(MQCNO_HANDLE_SHARE_BLOCK) for the threads only.
Can anybody find the problem? |
|
| Back to top |
|
 |
| prithun |
| Posted: Wed Apr 20, 2005 8:55 am Post subject: |
|
|
Apprentice
Joined: 08 Apr 2005
Posts: 33
|
Is there any restriction on the number of threads that can subscribe concurrently from a queue?
I succeeded in getting the messages from the queue with 2 threads.Everything is working fine with 2 threads.But when I increase the number of threads everything goes wrong. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Wed Apr 20, 2005 3:54 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Well I am not aware of any limitation on the number of IPROCS you can have on a Queue.
Here is what the WMQ Messages guide has to say about Reason Code 2059:
| Quote: |
2059 X’080B’ MQRC_Q_MGR_NOT_AVAILABLE
On an MQCONN or MQCONNX call, the queue manager identified by the QMgrName
parameter is not available for connection.
v On z/OS:
– For batch applications, this reason can be returned to applications running in
non-WebSphere MQ LPARs.
– For CICS applications, this reason can occur on any call if the original connect specified a
queue manager whose name was recognized, but which is not available.
v On OS/400, this reason can also be returned by the MQOPEN and MQPUT1 calls, when
MQHC_DEF_HCONN is specified for the Hconn parameter by an application running in
compatibility mode.
This reason code can also occur if a WebSphere MQ client application attempts to connect to a
queue manager within a WebSphere MQ client queue-manager group when none of the queue
managers in the group is available for connection (see the QMgrName parameter of the
MQCONN call).
This reason code can also occur if the call is issued by a WebSphere MQ client application and
there is an error with the client-connection or the corresponding server-connection channel
definitions.
On z/OS, this reason code can also occur if the optional OS/390® client attachment feature
has not been installed.
Corrective action: Ensure that the queue manager has been started. If the connection is from a
client application, check the channel definitions. |
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| prithun |
| Posted: Wed Apr 20, 2005 8:13 pm Post subject: |
|
|
Apprentice
Joined: 08 Apr 2005
Posts: 33
|
The queue manager is started even after it shows the error.
When I try to start the queue manager again it is showing
WebSphere MQ queue manager running. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Wed Apr 20, 2005 8:18 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Um, I think the most relavent part is:
This reason code can also occur if the call is issued by a WebSphere MQ client application and
there is an error with the client-connection or the corresponding server-connection channel
definitions.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| 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
|
|
|
|
