Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
fadams discovered that soak testing the Java Broker sending AMQP 1.0 messages through the proton messenger javascript binding caused the Java broker to grow in memory usage continuously and eventually spend all its time trying to garbage collect.
The issue is that when a link is set up as sender settles, the unsettled state associated with a delivery is not all being cleared when the final settlement arrives from the sender.