Greetings,
Are there known issues with a “filtering consumer” calling receive(timeout)?
I’ve found that we need to call receive twice, e.g.
try (var consumer = session.createConsumer(destination, selector)) {
Message message = consumer.receive(PURGE_TIMEOUT_MS);
if (message == null) {
message = consumer.receive(PURGE_TIMEOUT_MS);
}
…
}
If we only call it once, the message is never received, regardless of the
timeout value. This kind of looks like ARTEMIS-3916, but that was for a legacy
JMS client and was reported fixed in 2.25.
If this doesn’t sound familiar, I can write up a reproduction test.
Thanks
John
PLEASE NOTE: This e-mail from Redpoint Global Inc. (“Redpoint”) is
confidential and is intended solely for the use of the individual(s) to whom it
is addressed. If you believe you received this e-mail in error, please notify
the sender immediately, delete the e-mail from your computer and do not copy,
print or disclose it to anyone else. If you properly received this e-mail as a
customer, partner or vendor of Redpoint, you should maintain its contents in
confidence subject to the terms and conditions of your agreement(s) with
Redpoint.
