I think that publishing/consuming transactions should not be committable after queue deletion.
As a developer of messaging solution I would find it odd to be able to commit transaction successfully after queue deletion (even when all my messages settled and reached terminal state). Though, I would expect to complete rollback successfully in this case. I think that such behaviour would be least surprising for the end users. Though, I am not sure what behaviour should be when messages are published via exchange and routed into deleted queue On 20 March 2018 at 11:37, Rob Godfrey <[email protected]> wrote: > On 20 March 2018 at 12:30, Gordon Sim <[email protected]> wrote: > >> On 20/03/18 11:13, Oleksandr Rudyy wrote: >> >>> I think than on queue deletion the Broker should do the following for >>> AMQP 1.0 endpoints >>> * send DETACH performative with an error "amqp:resource-deleted" to >>> all attached links >>> * delete all information about detached links >>> >> >> That is what the c++ broker does. >> >> >> > How do we treat transactions which have transactionally enqueued a message > on the (now deleted) queue - do we allow them to commit successfully, or do > we force a rollback? Similarly when a message has been sent from the queue > and accepted as part of a transaction? > > -- Rob > > >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
