REST API question regarding clientId parameter and action=unsubscribe

I have a client application that use the REST API. I have the clientId parameter on my URL, and I'm wondering what happens on the broker/server when the client terminates without posting with an action=unsubscribe parameter. Does the server's garbage collector eventually destroy any orphaned

Re: REST API question regarding clientId parameter and action=unsubscribe

I ran a test where I don't post the unsubscribe and I notice a consumer I created is still active. That is harmful because it can consume messages even though the client is no longer connected. Is there a way to destroy that consumer if the client app forgets to post the action=unsubscribe?

Re: [DISCUSS] - AcitveMQ 5.7.1 release

Any update on this? Thanks, sv - Stephen Vincent -- View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-AcitveMQ-5-7-1-release-tp4658048p4659843.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: JMS java client having trouble receiving with message selector

Gary Tully responded to my in the user forum and provide me with the info I needed to find my mistake. Below is the follow-up I sent to the user forum describing my mistake. -- …snip… It does not poll the broker for messages unless prefetch is 0. …snip… Gary, Thank