-
1. Core API: queue with filter - bug or misunderstanding
clebert.suconic Jan 19, 2011 12:29 PM (in response to zyz)You send a message towards the address.
If queues have filters, only the queues with a matching filter will accept the message.
-
2. Re: Core API: queue with filter - bug or misunderstanding
zyz Jan 20, 2011 5:36 AM (in response to clebert.suconic)Thanks, of course, I get that.
After some investigation I found that my question should be changed as follows:
Why does a (non-durable) message dissappear from a (non-durable) queue (with a filter) only after explicit call to session.commit() after message acknowledgement though the session was created as non-transacted, with autoCommitSends == autoCommitAcks == true?
Don`t autoCommitXxxx work with non-transacted sessions? Or with non-durable messages/queues?
You can see different results of the attached test if the value of manualCommit variable is changed to false.
-
FilterTest.java.zip 1.2 KB
-
-
3. Re: Core API: queue with filter - bug or misunderstanding
timfox Jan 20, 2011 5:53 AM (in response to zyz)That's odd, autoCommitAcks seems to be ignored in the current code when acking (it should force a flush), perhaps something was changed recently.
Workaround would be to set ackBatchSize to zero, to force an acknowledgement flush every time you acknowledge.
-
4. Core API: queue with filter - bug or misunderstanding
zyz Jan 20, 2011 6:46 AM (in response to timfox)Thanks, that works.
-
5. Core API: queue with filter - bug or misunderstanding
clebert.suconic Jan 20, 2011 8:59 AM (in response to timfox)Tim Fox wrote:
That's odd, autoCommitAcks seems to be ignored in the current code when acking (it should force a flush), perhaps something was changed recently.
Workaround would be to set ackBatchSize to zero, to force an acknowledgement flush every time you acknowledge.
That's the way it's always been as far as I know.