| Author |
Message
|
| sethuramb |
 Posted: Wed Oct 15, 2008 11:53 pm Post subject: IBM MQ 6.0 - MQQueueManager client timeout |
 |
|
Newbie
Joined: 15 Oct 2008
Posts: 2
|
We are using IBM MQ Version 6.0.
We are using MQSimpleConnectionManager to connect with MQQueueManager. While we attempt to connect with QueueManager, if the MQ is down (network lan cable unplugged / network issues) or there is delay in providing the QueueManager object, the client is waiting for an infinite period and we get an error rejecting connection with 2009 and 2058
private static MQSimpleConnectionManager myConnMan=new MQSimpleConnectionManager();
MQQueueManager qMgr = null; // Queue Manager object
qMgr = new MQQueueManager("TestQueue", myConnMan);
Is there any client timeout in JAVA API available to handle this situation. Also, are there any better approach to handle this situation while we wait for MQQueeManager object to PUT the message into the queue.
Thanks!
-Sethu |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Thu Oct 16, 2008 2:12 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Reason Code 2058 x'80A'
MQRC_Q_MGR_NAME_ERROR
On an MQCONN or MQCONNX call, the value specified for the QMgrName parameter is not valid or not known. This reason also occurs if the parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.) 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 (see the QMgrName parameter of MQCONN), and either:
* Queue-manager groups are not supported.
* There is no queue-manager group with the specified name.
Corrective action: Use an all-blank name if possible, or verify that the name used is valid.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| sethuramb |
| Posted: Thu Oct 16, 2008 3:37 am Post subject: |
|
|
Newbie
Joined: 15 Oct 2008
Posts: 2
|
I wanted to know the MQQueueManager client timeout only from a MQ failure perspective.
Can any one help! |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Oct 16, 2008 9:56 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Talk to the people responsible for your TCP/IP communications timeout on the box. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| tng123 |
| Posted: Wed Dec 31, 2008 12:32 am Post subject: |
|
|
Newbie
Joined: 31 Dec 2008
Posts: 2
|
I am facing the same issue except in my case I am getting only 2009 exception with a delay.
Please help.
Thanks,
tng123 |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 31, 2008 12:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| tng123 wrote: |
| I am facing the same issue |
And oddly the same advice is applicable.... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| tng123 |
| Posted: Wed Dec 31, 2008 1:08 am Post subject: |
|
|
Newbie
Joined: 31 Dec 2008
Posts: 2
|
Thanks Vitor for your quick reply.
Want to let you know we also got some occurrences of 2059 error but those times we received the exception without any delay.
Any idea how to see/set TCP/IP communications timeout?
Do you think changing TCP/IP communications timeout will help to get the exception without delay? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 31, 2008 1:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| tng123 wrote: |
| Want to let you know we also got some occurrences of 2059 error but those times we received the exception without any delay. |
.
Thank you. I feel better for knowing that.
| tng123 wrote: |
| Any idea how to see/set TCP/IP communications timeout? |
And again...
| fjb_saper wrote: |
| Talk to the people responsible for your TCP/IP communications timeout on the box. |
| tng123 wrote: |
| Do you think changing TCP/IP communications timeout will help to get the exception without delay? |
Perhaps, but a 2059 results from a pure comms failure. A 2009 may occur when the queue manager decides to hang up. There may be software delays here.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
