Either give the messages an expiration time or write something to drain the
destinations according to your own business logic. Then
gcInactiveDestinations doesn't need to care about your specific use-case.
On 28 June 2013 20:42, Paul Gale wrote:
> gcInactiveDestinations is defined a
gcInactiveDestinations is defined as delete inactive destinations that are
empty. An empty destination is not the only criteria under which I want a
destination to be deleted.
Is there a setting, or combination of settings, that will automatically
delete a destination that's not empty but ha
th-pending-messages-td3229098.html
>> ).
>> Unfortunately I never got an answer. It seems to me there might be a
>> bug. I never raised a Jira issue, though. We just stopped using the
>> gcInactiveDestinations feature, but of course this is not a real
>> solution.
>
h. We just stopped using the
> gcInactiveDestinations feature, but of course this is not a real
> solution.
>
> I don't think that it is related to STOMP, because we have only been
> using OpenWire, via the Java and C++ libraries.
>
> Best regards,
> Martin
>
>
stopped using the
gcInactiveDestinations feature, but of course this is not a real
solution.
I don't think that it is related to STOMP, because we have only been
using OpenWire, via the Java and C++ libraries.
Best regards,
Martin
On Tue, Oct 11, 2011 at 5:55 PM, James Green wrote:
> In 5.
In 5.5.0 with gcInactiveDestinations=true, we've been sending messages via
STOMP with a receipt (proven in the stomp.log).
Just occassionally, the message appears to go missing, as does the queue
itself. The message is set to persist and has an expiry of several days.
Is this an issue t
