ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexWebSphere Message Broker SupportMessage broker timeout issue

Post new topicReply to topic
Message broker timeout issue View previous topic :: View next topic
Author Message
prabhuoist
PostPosted: Fri Nov 24, 2017 12:16 am Post subject: Message broker timeout issue Reply with quote

Novice

Joined: 10 Oct 2017
Posts: 23

Hi There,

we faced one issue in production where MB service was giving timeouts.

We restarted EG followed by broker but it dint resolved the issue.
That particular EG calls two database(one by one and DB is common for all EG's). We checked with DBA but no issue observed there also.

Finally we observed that some messages are piled up in SYSTEM.BROKER.TIMEOUT.QUEUE and once we clear that queue service started running fine.
User logs also suggest nothing.

What could be the issue here.
Back to top
View user's profile Send private message
zpat
PostPosted: Fri Nov 24, 2017 1:42 am Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5578
Location: UK

The issue is that you don't know the details of the service you are supporting and are just restarting things in the hope the problem goes away by magic....

Find out what the service does, what resources outside of the broker that it uses (e.g. web services). Are they working normally - were they down for a period?
_________________
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
View user's profile Send private message
prabhuoist
PostPosted: Fri Nov 24, 2017 1:48 am Post subject: Reply with quote

Novice

Joined: 10 Oct 2017
Posts: 23

This service uses store procedure call to connect to database.

And we have checked connectivity using mqsicvp command and it was working.

So my only doubt is whether actually clearing system.broker.timeout.queue resolve the issue or it was just coincidence that at the same time somebody from dba (they dont reveal the details) done something.

And if clearing queue resolve the issue then how.
Back to top
View user's profile Send private message
zpat
PostPosted: Fri Nov 24, 2017 3:27 am Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5578
Location: UK

What is in the syslog?

Why would clearing a timeout queue stop further timeouts?

Clearing a timeout queue means you are discarding those transactions - so I hope you have investigated each and every one to ensure no business impact?
_________________
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
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker SupportMessage broker timeout issue
Jump to:



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
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.