| Author |
Message
|
| Igor68 |
 Posted: Sat Aug 19, 2006 4:08 am Post subject: timeout time |
 |
|
Newbie
Joined: 19 Aug 2006
Posts: 3
|
Hi all,
by connecting to the MQ Manager (it is not available) it takes a specific time before the API Call come back.
Ist there a chanche to configure this timeout time
a) for the hole system
b) for the specific API call
Igor |
|
| Back to top |
|
 |
| vennela |
| Posted: Sun Aug 20, 2006 8:25 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I used amqsput while the QMGR is down and I got a response immediately.
What programming language and how much time is it waiting |
|
| Back to top |
|
|
| Igor68 |
| Posted: Mon Aug 21, 2006 12:19 am Post subject: |
|
|
Newbie
Joined: 19 Aug 2006
Posts: 3
|
I used C as programming language.
By my test I unlinked my network cable from the box where MQ Server is running.
From my client it took 90 seconds until the MQCONN came back.
Hope that describes my problem in more detail.
Igor |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 21, 2006 1:17 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Tried to reproduce your problem here (using a simple C program rather than amqsget or put) and got an instant 2059. 
Is there any chance that there's a delay in a DNS server or other piece of network hardware? You say
| Igor68 wrote: |
| By my test I unlinked my network cable from the box where MQ Server is running |
Do you mean by this you disconnected the server itself from the network, or the cable linking you to the network?
I certainly not aware (but stand ready to be corrected) about an MQ timeout on connect. It sounds a lot more like the connect attempt is bouncing round the network for some reason. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Igor68 |
| Posted: Mon Aug 21, 2006 2:00 am Post subject: |
|
|
Newbie
Joined: 19 Aug 2006
Posts: 3
|
I disconnected the server from the network.
By using amqsputc I got the message:
MQCONN ended with reason code 2059 after the same time.
Igor |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 21, 2006 2:25 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Weird! 
In my test I tried to conect to a queue manager on a server that powered down (waiting for parts).
Still not aware of an MQ timeout values for connection. Probably network - weird 2059s are always network......
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Aug 21, 2006 2:48 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The box was disconnected from the network. There is always a TCP/IP lagtime, at least until the box is aware of the fact that is is disconnected (has been isolated). I believe the lagtime is proportional to the number of routes defined that can be used to reach the same target (not factoring in the lagtime to reach the DNS). So you would have at least 1 time x.
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Mon Aug 21, 2006 5:06 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
Igor,
maybe you are able, to change the timeout on your local IP stack - ask the network guys in your company 
_________________
Regards
Hubert |
|
| Back to top |
|
|
|
|
