This isn't fixed in 4.2 yet either I'm afraid :(
On 23 Feb 2007, at 18:13, manav wrote:
Any ideas if this is fixed in any latest development build? I see a
4.2-SNAPSHOT and 4.2-incubator-snapshot under the 'source' link..
Not sure
how 'incubator' build is different from the other one.. but am
ready to try
anything if it is fixed...
Christopher G. Stach II wrote:
manav wrote:
Could someone pease respond back to the posted question?
We are holding off a release as we cannot get (do not know how to
get)
message expiry to work in 4.1. This is critical to a big company
using
AMQ.
Any immediate help / suggestion is appreciated.
Manav
I don't think expiration works in 4.1.
--
Christopher G. Stach II
--
View this message in context: http://www.nabble.com/Expired-Message-
Listener-tf3270915s2354.html#a9123819
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
