| Author |
Message
|
| b_anup |
 Posted: Mon Jan 12, 2015 3:56 am Post subject: MQsyncMessageTable timed out error on performance |
 |
|
Novice
Joined: 26 Jun 2014
Posts: 11
|
Problem Statement: On high thread count (>100) application is failing with the following error
"MQsyncMessageTable timed out message with id messageId" While testing the application on normal load it is working fine as the thread count increases we repeatedly gets the above error.
Name: WebSphere MQ
Version: 6.0.0.0
ALSB3.0 is connecting in binding mode to MQ.
Backend is Apache tomcat There we have simulator to do the job of selecting the response file based on request message.
Please let us know if I need to do any change in configuration of MQ property. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Jan 12, 2015 5:53 am Post subject: Re: MQsyncMessageTable timed out error on performance |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Thank you for deliberately using big print so we old timers can read it. 
| b_anup wrote: |
| Please let us know if I need to do any change in configuration of MQ property. |
This is what you should change:
| b_anup wrote: |
Name: WebSphere MQ
Version: 6.0.0.0
|
Not only is WMQv6 well out of support, that's not even the latest version of it. If you're using a modern version of Apache, that version of WMQ will not understand the threading model Apache's using in it's JMS handling.
Update to a supported version of WMQ, or (gulp!) use a version of Apache consistent with v6. Post again if the problem persists.
Also mention to whoever thought WMQv6 is a good idea that they should look up "business risk" in a dictionary.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jan 12, 2015 5:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| You might also spend some time making sure that MQSynceMessageTable is actually an MQ supplied class or object, and not an application object. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 12, 2015 8:22 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| You might also spend some time making sure that MQSynceMessageTable is actually an MQ supplied class or object, and not an application object. |
I think it's part of the inbuilt JMS, but I could be wrong
Note that this is the second problem you've posted trying to use WMQv6. From your other posts you clearly have WMQv7.5 on your site.
The longer you delay completing your move from WMQv6.0 to WMQv7.5, the more problems like this you will have.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Jan 13, 2015 1:52 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Using release 0 of any version is ill-advised!
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
|
|
