I have observed inexplicable behavior (to me, at least) when using the Stomp C API to consume messages from a durable subscription. I could not find prior discussion or bugs filed on this topic, so I would like to know if this is expected behavior.
I am using the 4.2 snapshot, built from the trunk on 1/19. The broker is running on Windows with JRE 1.5.0_10. The clients are using the Stomp C API from a remote Solaris box. Sending a Stomp UNSUB command after successfully creating and receiving messages on a durable topic appears to have no effect. The JMX console still shows the durable subscription under the tree path: org.apache.activemq/Subscription/Durable. If I manually execute the destroy() method from the console, the console shows the subscription moved to org.apache/activemq/Subscription/false. I am passing the topic destination in the UNSUB header. The broker appears to receive the UNSUB command (I specify a receipt in the UNSUB request and subsequently receive the corresponding RECEIPT response from the broker) but does not appear to handle it properly. Am I missing some trick to unsubscribing durable topics? Thanks for any response. -- View this message in context: http://www.nabble.com/Stomp-durable-topic-do-not-UNSUB-tf3042823.html#a8458129 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
