Yep - that's how the current JMS client is working -- Rob
On 10 October 2014 18:02, Gordon Sim <[email protected]> wrote: > On 10/10/2014 04:27 PM, Rob Godfrey wrote: > >> So, it is trying to update the remote terminus to change the expiry policy >> from NEVER to LINK_DETACH and the to close the link (thus destroying it). >> The seemingly duplicate call is because the first attempt to open the >> receiver doesn't set a source object and so the broker may just send back >> the current source rather than modifying it to change the durability. I >> believe this works with the Qpid Java Broker and SwiftMQ - I'm not sure >> whether it has been tested with the C++ Broker, ActiveMQ or others.... >> > > So on subscribing you create a receiving link with terminus expiry policy > set to never, and then on cancel you detach the receiver, re-open it with a > terminus-expiry of link-detach and then close the link? > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
