I have implemented expiry queue functionality, and also improved our DLQ functionality.
Now, a default expiry queue and dlq can be specified on the server peer level, but also an
expiry queue and dlq can be optionally specified on a per destination level. If specified
it will override that default expiry / dlq for that destination.
There is still an issue with multiple of the same message in the expiry / dlq that we need
to resolve (see my previous post). I have added a task for this and a test that will fail
until we sort it out.
View the original post :
Reply to the post :