Out of memory error about stompit HOT 4 CLOSED

I think I ran into #13.

Why is it necessary to do mesage.ack() for auto ack mode. STOMP specification says there is no need for client to send ACK to server in this mode. Is this an API requirement ?

Thanks,
Abhishek

from stompit.

Until recently it was a requirement of the API to use message.ack() in any ack mode. It forces application code to be ack-mode agnostic, which can potentially prevent errors if the ack mode is specified in config.

But this requirement is now deprecated (in master) and applications are expected to fully manage ACK messages themselves.

from stompit.

Do the application still need to do "message.ack()" even if the subscription header 'ack' is set to 'auto'?

I didn't understand 'applications are expected to fully manage ACK messages themselves.' Do the application need to acknowledge all messages regardless of 'ack' mode?

from stompit.

Yes you still have to use message.ack() even if the subscription is in auto ack mode.

But in the next version of stompit (probably v0.23), using message.ack() in an auto ack subscription will be optional, and client mode subscriptions will no longer be managed. The method message.ack will be deprecated, and the recommended way to send an ACK message is with client.ack(message)

from stompit.