|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Disconnect taking 5 minutes at random times? |
« View previous topic :: View next topic » |
Author |
Message
|
Quest |
Posted: Tue May 18, 2004 6:18 am Post subject: Disconnect taking 5 minutes at random times? |
|
|
Newbie
Joined: 02 Dec 2003 Posts: 3
|
We are a client application (in C++) that connections to a remote Queue Manager and puts a message. Most of the time, this process works and is very efficient. Occasionally, the entire call take exactly 5 minutes to process.
From our log:
05/17/04 10:10:02: MQ Connect to
05/17/04 10:10:02: MQ Open
05/17/04 10:10:02: MQ Put
05/17/04 10:10:02: MQ Close
05/17/04 10:10:02: MQ Disconnect
05/17/04 10:15:02: MQ connection result is =0
The last line is the return code from the function that actually does the connect/open/put/close/disconnect. Usually, this entire function executes within the same minute. A few times a day, it takes exactly 5 minutes to return.
Anyone have any ideas? or had similar problems?
IBM has had us apply a CSD, take the CSD off, reapply, etc (bascially no help...). |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue May 18, 2004 6:27 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
|
Back to top |
|
 |
fjb_saper |
Posted: Tue May 18, 2004 6:28 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
According to your symptom description, I would suspect network availability/traffic to be the reason.
What else happens on the network at the times you run into the problem:
file transfers, large amounts of data being moved around ... ?
F.J. |
|
Back to top |
|
 |
Quest |
Posted: Tue May 18, 2004 9:01 am Post subject: |
|
|
Newbie
Joined: 02 Dec 2003 Posts: 3
|
I was thinking along the lines of network availability/traffic, but it seems odd that it is always exactly a 5 minute delay. So far, we have been unable to come up with any network contention ideas.
Also, I have already investigated the other link provided and the client timeout. The call is not failing, as the data is sent sucessful (via the PUT), but the return code from the API takes 5 minutes to return. Note that this only happens a few times a day (1 or 2 in several hundred transactions).
I am trying to invesitgate the network situation more.... |
|
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
|
|
|
|