3 Replies Latest reply on Jul 20, 2009 2:15 PM by clebert.suconic

Expiry requires a consumer in order to work?

clebert.suconic Jul 20, 2009 1:37 PM

Is this by design or a bug?

Expiry Message requires a consumer on the original address in order to work. All the expiries are being done at client level, as far as I could see on code.

Say.. I send a message, with expiry in the past... the message will be expired only after a consumer received it first.

1. Re: Expiry requires a consumer in order to work?

clebert.suconic Jul 20, 2009 1:47 PM (in response to clebert.suconic)
This came into my attention as I was writing a test.

I" m sending a message as:

clientFile.setExpiration(System.currentTimeMillis()); producer.send(clientFile);

Expiry Address is properly configured:

AddressSettings addressSettings = new AddressSettings(); addressSettings.setExpiryAddress(ADDRESS_EXPIRY); server.getAddressSettingsRepository().addMatch("*", addressSettings);

But no message expiried until I added these two lines of code:

ClientConsumer consumer2 = session.createConsumer(ADDRESS); assertNull(consumer2.receive(1000));
Actions
2. Re: Expiry requires a consumer in order to work?

ataylor Jul 20, 2009 2:07 PM (in response to clebert.suconic)

Clebert,

we have an expiry reaper that runs every thirty seconds and expires messages on the server.

see PostOfficeImpl:Reaper
Actions
3. Re: Expiry requires a consumer in order to work?

clebert.suconic Jul 20, 2009 2:15 PM (in response to clebert.suconic)

Duh.. right!

thanks! :-)
Actions

Go to original post