| Author |
Message
|
| KishoreN |
 Posted: Wed Jun 11, 2008 12:14 pm Post subject: How the duration of the connection wait timeout is determine |
 |
|
Newbie
Joined: 11 Jun 2008
Posts: 4
|
Hi,
How the duration of the connection wait timeout is determined in the VB6 version of the MQ Client library?
I'm invoking the MQCONNXAny function to connect to the QueueManager.
Thanks in advance,
Kishore |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Jun 12, 2008 12:58 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
Refer to DISCINT (disconnect interval) channel attribute in the WMQ Intercommunication manual.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Sun Jun 15, 2008 8:19 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| bruce2359 wrote: |
| Refer to DISCINT (disconnect interval) channel attribute in the WMQ Intercommunication manual. |
DISCINT doesn't apply to CLNTCONN or SVRCONN channels.
If a successful connection cannot be made, MQCONN and MQCONNX seems to time out after about 30 seconds at most. I don't think this can be changed.
_________________
Glenn |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jun 17, 2008 7:17 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| DISCINT doesn't apply to ... SVRCONN channels |
DISCINT is a valid attribute of SVRCONN channel according to the WMQ MQSC manual.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Jun 17, 2008 6:56 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| bruce2359 wrote: |
| Quote: |
| DISCINT doesn't apply to ... SVRCONN channels |
DISCINT is a valid attribute of SVRCONN channel according to the WMQ MQSC manual. |
but only on z/OS 
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Jun 17, 2008 6:58 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
but I don't think Kishore is after that. I think he is asking how long will the MQCONNX call "hang" before it returns a 2059.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| KishoreN |
| Posted: Wed Jun 18, 2008 9:43 am Post subject: |
|
|
Newbie
Joined: 11 Jun 2008
Posts: 4
|
but I don't think Kishore is after that. I think he is asking how long will the MQCONNX call "hang" before it returns a 2059.
As it is being approximately 30 seconds, I would like to shorten the duration of the connection wait timeout.
Thanks,
Kishore
Last edited by KishoreN on Wed Jun 18, 2008 11:59 am; edited 1 time in total |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jun 18, 2008 9:51 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
Are you asking how long the client layer will take to successfully find a svrconn channel that answers up from the clntconn channel(s) defined in the client connection channel table - before it gives up trying?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| KishoreN |
| Posted: Wed Jun 18, 2008 12:02 pm Post subject: |
|
|
Newbie
Joined: 11 Jun 2008
Posts: 4
|
Are you asking how long the client layer will take to successfully find a svrconn channel that answers up from the clntconn channel(s) defined in the client connection channel table - before it gives up trying?
Yes, thats what I'm looking for....
Thanks,
Kishore |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jun 18, 2008 1:47 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
Your 30 second wait until it finally fails has been my experience, as well.
It appears that each of the CLNTCONN entries in the table is/are tried (in some mysterious order) and retried; then at some undocumented point of frustration, no further trying takes place and, voila, 2059.
Someone from IBM care to step in here??
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| KishoreN |
| Posted: Thu Jun 19, 2008 12:13 pm Post subject: |
|
|
Newbie
Joined: 11 Jun 2008
Posts: 4
|
Thank you all for your concerns.
Thanks,
Kishore |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Jun 19, 2008 1:06 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| bruce2359 wrote: |
| It appears that each of the CLNTCONN entries in the table is/are tried (in some mysterious order) and retried; then at some undocumented point of frustration, no further trying takes place and, voila, 2059. |
The order is very specific. It searches the table alphabetically by channel name for every entry that matches by the QM name provided by the app.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
