| Author |
Message
|
| simon.starkie |
 Posted: Tue Apr 10, 2007 2:31 pm Post subject: WMBT javaw.exe process usng 99% CPU? |
 |
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
Lately, my WMBT is spawning a javaw.exe process that is usng 99% CPU.
It seems to happen whenever I change a message flow or an esql that is part of a message flow that has been previously deployed to a BAR file. I don;t think there is a memory insufficiency since I have 2gb of RAM and nothing else is running. Help me please  |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Apr 10, 2007 2:33 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Just becuase there's 2gb in the machine doesn't mean that your WMBT (which *is* that javaw process) is USING it.
Try "wmbt.exe -Xmx 1024M -Xms 512M" and see if that helps.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| simon.starkie |
| Posted: Tue Apr 10, 2007 2:47 pm Post subject: |
|
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
| Tuned the java heap as suggested and it launched alot quicker...but it still hits the same 99% CPU utililation problem in javaw.exe when building the BAR files... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 10, 2007 2:49 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Does it happen with a brand new bar file, or with one that you've been using for a while?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| simon.starkie |
| Posted: Tue Apr 10, 2007 3:08 pm Post subject: |
|
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
It was happening with a BAR file I had been re-using for a while.
So I deleted it and created a new BAR file with the same name and now all is well.
Not sure what the root cause is though...but thanks very much for the help.
Last edited by simon.starkie on Tue Apr 10, 2007 3:12 pm; edited 1 time in total |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 10, 2007 3:11 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Likely the log files in the bar got very very big. If you're using 6.0.2.0, at least.
Otherwise, bar files have a history of getting cluttered up with, umm, history when re-used a lot.
Generally, btw, the increased java heap will make your life much easier. So I wouldn't change that back.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| simon.starkie |
| Posted: Tue Apr 10, 2007 3:14 pm Post subject: |
|
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
I left the heap size the way you suggested and it definitly helps.
I'm running the lates fixes for the WMBT but I'll remember to periodically purge the BAR files from now on.
Thanks again.
*EDIT 08-24-2007*
"C:\Program Files\IBM\MessageBrokersToolkit\6.0\wmbt.exe" -vmargs -Xss128k -Xmx1024M -Xms512M
Must have the -vmargs for the paramaters to have any effect at all. |
|
| Back to top |
|
|
|
|
