Problem Description: The Broker Server restarted.
One of our broker server restarted with following log details
Entry in log:
Alert 09/04/2007 10:04:18 1241 - Broker ran out of memory. Failing memory allocation request of 0x4136 bytes. Broker will exit.
Alert 09/04/2007 10:04:23 1033 - Unexpected stop of Broker Server in directory /brokerservices/vol01/app18/data/default/ pid 22354 - exit code 1
Info 09/04/2007 10:04:28 1038 - Broker Server Monitor starting Broker Server executable /sbcimp/run/tp/webMethods/Enterprise/6.1sp3fp11/Broker/bin/awbroker in directory /brokerservices/vol01/app18/data/default/
Info 09/04/2007 10:04:31 1000 - Broker Server ready, process id 5899 (Version 6.1.0.3.93 061206)
Need someone to suggest what best could be done to avoid this to happen again.
can you advise, also advise on what if any, monitoring is available on the broker for memory thresholds(sample java code).
As we use only wM Broker as JMS service provider and JMS clients.
Thanks in advance.
Regards
Santosh Arora
There have been multiple slow memory leak issues for Broker 6.5.x over the last few months. There were fixes released last week for Broker 6.5.2 that addressed some or all of these. Have a look at the “Fixes To Known Issues” section on Advantage for Broker to see if these fixes apply to your Broker version.
On a recent project, we experienced these issues more frequently with Broker 6.5.2 on IBM AIX than on Windows Server, but ultimately saw slow memory leaks on both.
Mark
Hi carlson,
Thanks a lot for your immdt response.I had verified in advantage release notes. there had ben one issue fixed in wM6.1-SP3-FP17 FixPack wrt to broker out of memory.
Checking the same.Will keep you posted reg the same
Thanks and Regards
Santosh Arora
Hi ksantosharora,
Is the Issue has been resolved with wM6.1-SP3-FP17 FixPack for Out of Memory in Broker?
please let us know
Thanks in Advance
Gouse.
[SIZE=2]Hi Gouse,
As per the explanation from wM TS team they said Broker_Core_6-1_SP3_Fix17 is abd fix pack and adviced not to upgrade the broker sever to fp17.
They have corrected this in Broker_Core_6-1_SP3_Fix18
###################################[SIZE=2]
1-1QCRJ0
A memory leak was introduced in Broker_Core_6-1_SP3_Fix17 as part of the fix for the storage leak.
The code has been modified to fix the memory leak.
######################################
we are still in the process of upgrading the Broker Server with FP18 .
I would suggest yout to upgrade the FP18 if you ahve faced this kind of issue.
Pls let me know your inputs
Thanks and Regards
Santosh ARora
[/size][/SIZE]