| Author |
Message
|
| TBS |
 Posted: Fri Dec 04, 2009 3:48 am Post subject: Start of Broker is slow . |
 |
|
Centurion
Joined: 29 Jan 2007
Posts: 143
Location: Hillerød / Denmark
|
Hi !
WMB v 6.1.0.4
Windows server 2003 SP2
After a Windows patch the broker seems to be wherry slow.
There is about 300 flows in default exec group
The DB2 activity is very small and the increase of MEM is also wherry slow.( DataFlowEngine.exe) " 1 1/2 hour before the broker is up and running and normally it takes 15 min.
Can Anyone help ?
How do i trace the start of my broker ?
Torben |
|
| Back to top |
|
 |
| AkankshA |
| Posted: Fri Dec 04, 2009 4:14 am Post subject: Re: Start of Broker is slow . |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
| TBS wrote: |
There is about 300 flows in default exec group
The DB2 activity is very small and the increase of MEM is also wherry slow.( DataFlowEngine.exe) " 1 1/2 hour before the broker is up and running and normally it takes 15 min.
Can Anyone help ?
How do i trace the start of my broker ?
Torben |
Never clutter default execution group so heavily.... not an IBM recommendation...
what about the CPU usage ??
in windows the golden mantra is RESTART 
_________________
Cheers |
|
| Back to top |
|
|
| TBS |
| Posted: Fri Dec 04, 2009 4:41 am Post subject: |
|
|
Centurion
Joined: 29 Jan 2007
Posts: 143
Location: Hillerød / Denmark
|
tryed restart no change 
CPU % low, ( 2 % on all 4 CPU's)
No Problems with DB2 .. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Fri Dec 04, 2009 5:01 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
uninstall the windows patch and try again to make sure it was the windows patch causing that issue.
what windows patch did you install? what did it "fix" ?!?
_________________
Regards, Butcher |
|
| Back to top |
|
|
| aditya.aggarwal |
| Posted: Fri Dec 04, 2009 5:12 am Post subject: |
|
|
Master
Joined: 13 Jan 2009
Posts: 252
|
| Quote: |
| How do i trace the start of my broker ? |
Step 1:
set MQSI_UTILITY_TRACE=DEBUG
Step 2
$ mqsistart <broker name>
Step 3:
$ mqsireadlog utility -t -b mqsistart -f -o mqsistartTrace.xml
$ mqsiformatlog -i mqsistartTrace.xml -o mqsistartTrace.txt
Check the txt trace file.
Step 4:
set MQSI_UTILITY_TRACE=none |
|
| Back to top |
|
|
| aditya.aggarwal |
| Posted: Fri Dec 04, 2009 5:17 am Post subject: |
|
|
Master
Joined: 13 Jan 2009
Posts: 252
|
Sorry the Step 3 will be...
$ mqsireadlog <brokername> -t -b mqsistart -f -o mqsistartTrace.xml
$ mqsiformatlog -i mqsistartTrace.xml -o mqsistartTrace.txt |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Dec 04, 2009 5:58 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| TBS |
| Posted: Fri Dec 04, 2009 6:02 am Post subject: |
|
|
Centurion
Joined: 29 Jan 2007
Posts: 143
Location: Hillerød / Denmark
|
Thanks for your help..
The patch "people" says that no patching is done.. Just a restart of the server.
In the mean time we traced the IP traffic and some time it stall between the Broker and the DB2 AIX server..
I follow that and this weekend i will start the broker with a trace and what see what i brings
Have a nice Weekend and again Thans for your corporation ...
Torben |
|
| Back to top |
|
|
|
|
