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 Index » WebSphere Message Broker (ACE) Support » High CPU from flow

Post new topic  Reply to topic
 High CPU from flow « View previous topic :: View next topic » 
Author Message
mqsme
PostPosted: Fri Feb 13, 2015 10:02 am    Post subject: Reply with quote

Acolyte

Joined: 16 Sep 2013
Posts: 51

Hi,

My testing environment broker in Linux keeps taking high CPU consumption whenever it starts. I check by TOP command, different message flows alternatively take high CPU consumption, not any particular one, so i can't spot whether it is broker's problem, or any broker flow's problem.

Not many meaningful errors captured during the loop other than

Feb 13 09:04:28 WebSphere Broker v7002[25039]: (broker1)[1]BIP2080E: Execution group EGChanges failed to return an internal configuration Start message response within a 318 second time period. : mqbroker_01.agent: /build/S700_P/src/AdminAgent/ImbAdminAgent.cpp: 10303: ImbAdminAgent::getXMLResponse: :

I failed to stop broker flows since high CPU, always got a timeout response when issuing mqsistopmsgflow.

what i can do is to kill the pid of broker, but can't help to solve the issue since it's taking high CPU again if i start the broker again.

Any idea what happen? thanks !
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Feb 13, 2015 11:14 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

What Linux?

What version of broker?

How many execution groups are defined?

How many flows deployed to the broker?

What's the average number of flows per EG?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
mqsme
PostPosted: Fri Feb 13, 2015 11:31 am    Post subject: Reply with quote

Acolyte

Joined: 16 Sep 2013
Posts: 51

I have to say this is an environment setup by previous guy and not used for 3 years. so it is full of challenges to set the environment right.

Red Hat Enterprise Linux ES release 4 (Nahant Update 9)

Name: WebSphere MQ
Version: 7.0.1.4

BIP1280I: The number of WebSphere Message Broker runtime installations on this machine is '2'.

6.0.0.7 : /opt/mqsi/6.0
7.0.0.2 : /opt/mqsi/7.0

around 25 EG running on this 2Gb ram machine, roughly 1-10 flows in each EG
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Feb 13, 2015 11:53 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

You complain about high CPU, and then don't mention how much CPU the box has. But in short:

- you have a v6.0 out of support broker that's not even on the latest and most efficient maintenance of that level consuming resources
- you have a v7.0 broker that's not on a supported maintenance level (the lowest supported level is v7.0.0.3) consuming resources
- you have a v7 queue manager that's not on the latest and most efficient mantenaince by a fair way
- you have 25 EGs, each of which will consume an overhead irrespective of the flows (if any) deployed to it
- you have between 25 - 250 flows, each of which consumes resource

Unless that box has a fair number of cores, I can see why the CPU usage is a large percentage of that available. Does it have a large number of cores? Most testing boxes do not, because of license costs.

Note that the broker error in your original post, and the general lack of responsiveness, are symptoms of the heavy workload the server is under, not the cause.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
zpat
PostPosted: Fri Feb 13, 2015 2:17 pm    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

Add memory - it's cheap, it's easy and it will fix a lot of problems.

CPU usage is generally only an issue with badly written (or looping) flows.
_________________
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
mqsme
PostPosted: Fri Feb 13, 2015 4:31 pm    Post subject: Reply with quote

Acolyte

Joined: 16 Sep 2013
Posts: 51

Bingo ! Add memory, exactly what i think.

Now memeory added to 8Gb and the broker managed to start successfully, thanks guys!
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » High CPU from flow
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.