Major Description
Running with qpid-tool against either the Java (after the QMF patch) or the C++ Broker it seems like no matter how many messages the broker sends the qpid-tool client, the client never acknowledges these incoming commands at the session level
While the subscriber is acting in "no-ack" mode, this still seems to cause a build up in memory usage of the C++ broker (possibly because it is buffering unacknowledged frames
Simply running a couple of qpid-tool instances against an otherwise idle qpid-broker, the amount of memory being used by the broker has gradually increased from 4Mb to 200Mb over the last two days