|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
MQ version 7.5.0.2 Upgrade - Con waits for putting messages |
« View previous topic :: View next topic » |
Author |
Message
|
OzgurAydin |
Posted: Fri Jan 06, 2017 5:32 am Post subject: MQ version 7.5.0.2 Upgrade - Con waits for putting messages |
|
|
 Apprentice
Joined: 08 Sep 2008 Posts: 27
|
Hi,
We have recently upgraded our MQ version from 7.0.1 to 7.5.0.2. After the upgrade we faced an application making a connection but waiting about 4 seconds to send an ACK messages back to the connecting application causing it to wait to put messages to the new queue manager. Which is causing an accumulation of messages to be sent to the queue manager. We have consuled IBM for it but we didn't receive any valuebla info. What they said was upgrade the system to 7.5.0.7 .
Thanks |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Jan 06, 2017 5:40 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
You might be running into a known bug at that level.
So what is preventing you to upgrade to 7.5.0.7 or even 8.0.0.5 ?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
Vitor |
Posted: Fri Jan 06, 2017 5:53 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
fjb_saper wrote: |
You might be running into a known bug at that level. |
Especially if IBM are saying to upgrade.
You could ask them if they've identified a specific APAR that fixes this and apply that, but that's a much inferior strategy to going to the stated version. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Fri Jan 06, 2017 7:59 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
When someone says "Upgrade" without referring to a specif bug identified in the old version and confirmed fixed in the new version, to me its another way of them saying "I don't know what's wrong, go upgrade, maybe its fixed in the new version, maybe the system restart done as part of the upgrade fixes the issue, maybe x hours go by and the external unrelated reason for the failures goes away. Either way we don't know, so go keep yourself busy with an upgrade."
I do think its odd a recent upgrade was done and it went to 7502 instead of the latest fix pack like FJ suggested. You may not be ready for MQ 8, but if you can do 7502 you should have been able to just go 7507 from the get go and eliminated the "Upgrade, see if it goes away" argument. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Jan 09, 2017 5:08 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
There is a list of things fixed in each release. Some basic review of it will help see if there's a similar problem that might be fixed.
But, yes, odd that an upgrade went to 7.5.0.2 instead of 7.5.mostrecent.fp _________________ chmod -R ugo-wx / |
|
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
|
|
|
|