Greetings! When a (non-HA) Artemis broker is restarted, almost everything self-heals. But we seem to be finding, in ways that are of course hard to reproduce, that occasionally the consumer of a temporary reply-to queue will stop receiving permanently. Does this sound familiar? If it should be considered a bug, please give me some help to capture whatever trace or stack you might need to diagnose it.
Do I need to detect the broker failure and re-create the temporary queues? I’m not sure how to do that, other than using a watchdog to detect non-delivery within an acceptable timeout. Thanks John [rg] <https://www.redpointglobal.com/> John Lilley Data Management Chief Architect, Redpoint Global Inc. 888 Worcester Street, Suite 200 Wellesley, MA 02482 M: +1 7209385761<tel:+1%207209385761> | john.lil...@redpointglobal.com<mailto:john.lil...@redpointglobal.com> PLEASE NOTE: This e-mail from Redpoint Global Inc. (“Redpoint”) is confidential and is intended solely for the use of the individual(s) to whom it is addressed. If you believe you received this e-mail in error, please notify the sender immediately, delete the e-mail from your computer and do not copy, print or disclose it to anyone else. If you properly received this e-mail as a customer, partner or vendor of Redpoint, you should maintain its contents in confidence subject to the terms and conditions of your agreement(s) with Redpoint.
