JBMESSAGING-1495 - Replicate Expiry and DLQ

[clebert.suconic]

As part of the Expiry Queue and DLQ task, we have talked about using Management to send Move messages to the backup node.

But that would add a dependency on Management for both DLQ and ExpiryQueue management. Do we really want to do that?


IMO it would be better to have some sort Communication Channel between MessagingServerImpl on live and MessagingServerImpl on backup. This way if we embed start a server without Management, DLQ and Expiry would still work.


Any thoughts?

[clebert.suconic]

I mean...

I agree that Management should replicate calls properly when an user is using management to manually expire/move messages.

However I don't think that QueueImpl should rely on Management to expiry queues, as Management may not be available, right? Or am I missing anything here?

[timfox]

Management is always available.

You just need to replicate the messages as we have discussed (several times now)!

[timfox]

Obviously if the server is not clustered you don't need to replicate

[clebert.suconic]

"timfox" wrote:
Management is always available.

Ok... I thought it was optional on the embedded case.

Obviously if the server is not clustered you don't need to replicate

The DLQ/expire/move call will be sent to Management, and Management will deal with that.

[timfox]

JMX is optional, not management.

You don't have to call management, but management and your code should share the same code for expiry/dlq, and this should be replicated when the server is clustered.