-
Bug
-
Resolution: Done
-
Major
-
None
-
7.5.0.CR3
-
None
-
User Experience
-
+
-
Verified in a release
Hi,
This issue was faced by the client previously. Following are the details for the issue.
1. There was a large pile-up of messages in the AMQ Broker.
2. The AMQ broker was configured with 8GB memory(max and min both)
3. Due to some reason the amq broker crashed and was shut down.
4. The client tried to restart the broker, but every time they restarted, it crashed again.
5. They had a case raised and the support team suggested to increase the broker's memory and try to restart.
6. They increased the memory to 12GB and tried restarting, but it still failed to restart.
7. After increasing the heap size to 16GB then the broker was able to start.
We are looking if there could be any enhancements done so that the amq-broker utilizes less memory while starting up even if there are huge pile-up of messages in the journal.
Thanks and Regards,
Shrikant Chavan
- is related to
-
ENTMQBR-2546 Repeated WARN: [AMQ212034: There are more than one servers on the network broadcasting the same node id] after restarting master broker in 3-node multicast cluster
- Closed
- relates to
-
ENTMQBR-2313 Fails to load journal after queue full
- Closed