Is the DLQ behaviour also hard coded (and supposed to work)?
Am "playing" with the redelivery behaviour by having a simple mdb that just calls setRollbackOnly.
We watch messages being delivered a number of times and eventually get a log message along the lines of:
JBossMessage:PERSISTENT has exceed maximum delivery attempts and will be removed
However, the message is never moved onto a dlq...
There's no DLQ support at present.
This is part of the same task, so will be in 1.0.2 (not too long).
Aah, fair enough - I'll have another go when 1.0.2 comes out.
Am I reading the JIRA right on this? Has it moved from 1.0.2 to 1.2.0Beta? If so, is there any way for us to have some form of DLQ until then?
That feature is badly needed by others as well, so I raised it to critical.
Product management took the decision to move all new feature development that is not related to clustering to 1.2, after anything clustering, so that's why you see it in 1.2.0.Beta. That release is planned to be available around November, but we may release bits of it before the planned date, and we're trying to include 127 within those bits.
toddjtidwell, would you be interested to contribute some of these features?
Let us know. Cheers,
Good to see this is getting attention :)
I appreciate that clustering is important - in fact I have couple of customers who are waiting for it. However, for them the DLQ is an absolute "must have". Without the DLQ we cannot have MDBs processing a queue, even in a single node environment.
The situtation for the customer I'm working with that started this thread is that we would accept two standalone messaging servers rather than a clustered pair for our availability requirements - so long as we had a DLQ ...
I guess this is a round about way of saying that for us a DLQ is higher priority than clustering.
Unfortunately I am currently working flat out on a couple of projects so my ability to contribute towards making it happen is severly limited (quite happy to run our tests again if anyone does make progress on the DQL ;)
Getting the DLQ to work is really a rather simple task too.
Ordinarily, yes, I'd be incredibly happy to contribute here. I love JBoss and I'd love to be a part of making it even more robust. However, I'm staring down a huge deadline on a project that uses JBoss Messaging. If I start contributing, neither of you will get my best work.
When it's done, however, I promise, I'll be back here IDE in hand and ready to go.