Hi.
Our customer (using v.8) had a problem of high memory (11GB) usage of “awbroker.exe” for a month.
They resolved this by restart Broker server but the reason and the impact were not clear because some
logs of Broker & IS were deleted.
To investgate the root cause and the impact for the next,
- Which logs and data of Broker & IS should be keeped after this problem?
- Which logs and data of Broker & IS should be monitored to avoid this problem?
- Which settings of Broker & IS should be set?
- Is there any measure to resolve other than broker restart?
Best regards,
Shotat
Hi Shogo,
we havbe never set anything explicitly related to Broker memory, neither on wM 7.1 nor on wM 9.5.
How big is your Broker Data Storage file?
How full is it?
You can find these informations in MWS under (Broker) Servers → → Utilization.
What is the exact Broker version?
Try "awbroker.exe -version" from a command prompt.
As long as this does not lead to any issues with the box I would avoid restarting the Broker Server.
If it crashes with some sort of "OutOfMemory"-Error Broker Monitor will restart it automatically.
Perhaps it is time to consider Upgrading to 9.x.
Regards,
Holger
Dear Holger-san,
Thanks for the reply very much.
How big is your Broker Data Storage file?
How full is it?
You can find these informations in MWS under (Broker) Servers → → Utilization.
What is the exact Broker version?
Try “awbroker.exe -version” from a command prompt.
I am asking the customer to provide us with those values.
Best regards,
Shotat