This content has been marked as final.
Show 5 replies
-
1. Re: JBMESSAGING-1495 - Replicate Expiry and DLQ
clebert.suconic Feb 16, 2009 4:10 PM (in response to 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? -
2. Re: JBMESSAGING-1495 - Replicate Expiry and DLQ
timfox Feb 16, 2009 4:55 PM (in response to clebert.suconic)Management is always available.
You just need to replicate the messages as we have discussed (several times now)! -
3. Re: JBMESSAGING-1495 - Replicate Expiry and DLQ
timfox Feb 16, 2009 4:57 PM (in response to clebert.suconic)Obviously if the server is not clustered you don't need to replicate
-
4. Re: JBMESSAGING-1495 - Replicate Expiry and DLQ
clebert.suconic Feb 16, 2009 5:10 PM (in response to 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. -
5. Re: JBMESSAGING-1495 - Replicate Expiry and DLQ
timfox Feb 16, 2009 5:19 PM (in response to clebert.suconic)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.