| Author |
Message
|
| murdeep |
 Posted: Thu Apr 09, 2009 8:27 am Post subject: MQExplorer V7 High CPU |
 |
|
Master
Joined: 03 Nov 2004
Posts: 211
|
Anyone else experiencing an issue with MQExplorer in V7 FP01 monopolizing CPU? I have a test node that has about 5 qmgrs on it and when I start MQExplorer it maxes out all four of my CPUs. Even if I wait for a very long time it just grinds. I enabled a trace for IBM support and after 20 or so minutes elapsed time (80 minutes of CPU time) it was barely functional. Resulting trace file was close to 2G and just shows explorer accessing the queue manager and collecting info on the queues/channel etc.
Just curious to know if others are experiencing similar issues. BTW, we uninstalled, reinstalled and same problem. |
|
| Back to top |
|
 |
| exerk |
| Posted: Thu Apr 09, 2009 8:29 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Sorry, my crystal balls are down...any chance of a hint as to platform etc.? 
EDIT: I'm guessing Vitor's favourite platform...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Apr 09, 2009 8:39 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| exerk wrote: |
| EDIT: I'm guessing Vitor's favourite platform... |
There are only two platforms that MQExplorer officially runs on.
Certain mavericks may have tried it out on AIX, but that's not recommended for the casual user. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Apr 09, 2009 8:50 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Hence my guess...I've not personally encountered it chewing up resource on Linux. As to those 'mavericks', I find they're generally the sort of people who like to see if they can get z/OS to run on a digital watch - if you get my drift 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| murdeep |
| Posted: Thu Apr 09, 2009 9:36 am Post subject: |
|
|
Master
Joined: 03 Nov 2004
Posts: 211
|
Sorry W2K. 2003 Server SP2.
BTW, installing eclipse 3.3 and MQExplorer (MS0T) on XP SP2 node and then remotely attaching results in similar issue. Something fundamentally wrong with new implementation of MQExplorer. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Apr 09, 2009 9:40 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You maybe got Auto Refresh turned on for each QM and have the Refresh Interval set to something like 1 second?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| murdeep |
| Posted: Thu Apr 09, 2009 10:02 am Post subject: |
|
|
Master
Joined: 03 Nov 2004
Posts: 211
|
Autorefresh set to default 300 seconds.
IMO, looks like MQExplorer V7 has been rearchitected to take advantage of multi threading to the point where every CPU on a node gets monopolized by an MQExplorer thread. On my two way both CPUs go 100% and on my 4 way all 4 CPUs go 100%. MQExplorer V7 in my environment is totally useless. Godd thing I prefer runmqsc. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 09, 2009 12:03 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I'm running WMQv7 on WinXP & Vista HP without issues. Aside from the usual Windoze ones. Default refresh rate and other settings. Can't say I've pushed it to the limit, but it starts, runs, browses messages, creates test queues, that sort of thing.
(Vista - urgh!) 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Apr 10, 2009 4:40 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
How many QMs, Vitor? Maybe that be the issue.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| murdeep |
| Posted: Mon Apr 13, 2009 11:41 am Post subject: |
|
|
Master
Joined: 03 Nov 2004
Posts: 211
|
| PeterPotkay wrote: |
| How many QMs, Vitor? Maybe that be the issue. |
5 qmgrs.
On the MS0T install I define one connection to one of the queue managers. This qmgr has:
Queues: 303
Channels: 28
Namelists: 110
Processes: 1
Services: 4
Listeners: 6
Topics: 5
Subs: 1
MQExplorer starts and pegs the CPU. So after 12mins CPU I RDC to the qmgr node and display the client channel status and I see over 15000 msgs sent across the channel and it's increasing with each display. So clearly something is wrong.
MQExplorer need only do a handful of PCF commands to get everything it needs to populate the GUI so why are over 15000 messages being sent? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Apr 13, 2009 12:12 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Just for testing purposes, set the MCAUSER on the SVRCONN you're using to mqm, and see if that helps. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 13, 2009 1:01 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| PeterPotkay wrote: |
| How many QMs, Vitor? Maybe that be the issue. |
I got 4 QMs, 3 of them in a cluster, all seems to be working.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Apr 13, 2009 1:04 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| murdeep wrote: |
| MQExplorer need only do a handful of PCF commands to get everything it needs to populate the GUI so why are over 15000 messages being sent? |
A "message" over a SVRCONN channel is not a message. An MQOPEN call is 2 "messages", the MQOPEN request, and the results. An MQGET that returns a 2033 is 2 "messages". An MQGET that returns an actual message is also seen as 2 "messages" on the SVRCONN channel.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Apr 13, 2009 4:17 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
[quote="PeterPotkay"]
| murdeep wrote: |
| A "message" over a SVRCONN channel is not a message. |
Every MQ verb is "two" messages over a client channel, at a minimum. One for the MQI call, and one for the MQI response.
Where the MCAUSER/effective user id is *not* the mqm user, there may be an incrementally bigger set of calls, one to inquire all of {queue, channel, etc.} names, and one to {inquire queue, channel, etc... name} individually to avoid security problems trying to read SYSTEM.AUTH.DATA.QUEUE or etc. objects that anyone other than "mqm" is forbidden to see. |
|
| Back to top |
|
|
| PhilBlake |
| Posted: Tue Apr 14, 2009 7:09 am Post subject: |
|
|
Acolyte
Joined: 25 Oct 2005
Posts: 64
|
| murdeep wrote: |
| PeterPotkay wrote: |
| How many QMs, Vitor? Maybe that be the issue. |
5 qmgrs.
On the MS0T install I define one connection to one of the queue managers. This qmgr has:
Queues: 303
Channels: 28
Namelists: 110
Processes: 1
Services: 4
Listeners: 6
Topics: 5
Subs: 1
MQExplorer starts and pegs the CPU. So after 12mins CPU I RDC to the qmgr node and display the client channel status and I see over 15000 msgs sent across the channel and it's increasing with each display. So clearly something is wrong.
MQExplorer need only do a handful of PCF commands to get everything it needs to populate the GUI so why are over 15000 messages being sent? |
You are correct that 15000 messages is waaay too many. The Explorer basically uses a single thread to manage the connection to the queue manager and only sends PCF requests for objects selected in the navigator view. Worker threads are used to populate each content view.
Some questions which may help identify the problem...
1. What's the command level/platform/ccsid of the target queue manager ?
2. Do you have any 3rd party plug-ins installed ?
3. Any errors in the eclipse error log (found in %APPDATA%\IBM\MQ Explorer\.metadata\.log) ?
4. Any FFST's ?
Some things to try...
1. Do you see the same problem with a clean workspace ? Rename the current workspace location (found in %APPDATA%\IBM\MQ Explorer) and start the Explorer (with "strmqm -i" and then "strmqm -c") and just add the one queue manager that shows the problem.
2. You could also try disabling all plugins not needed for basic administration (go to Windows -> Preferences... -> WebSphere MQ Explorer -> Enable Plug-ins and untick all except "Queue Manager Administration"), then restart the Explorer. This would show a problem with any of the provided plugins.
HTH
Phil |
|
| Back to top |
|
|
|
|
