Hi all,
we were looking for a way to have expired messages sent to a dead-letter-queue
rather than being discarded. The broker documentation does not mention any such
feature.
Then I found issue https://issues.apache.org/jira/browse/QPID-7153 which
describes exactly the desired behavior.
Is t
Hi Timothy,
I just synced that change and verified that it fixes the issue in my test setup.
Thanks for the quick turnaround! __
-Timo
On 8/12/20, 8:38 AM, "Timothy Bish" wrote:
On 8/10/20 5:05 PM, Timo Naroska wrote:
> Hi,
>
> we're seeing s
Hi,
we're seeing sporadic cases in our JMS application where the
AmqpTransferTagGenerator used inside JMS MessageProducer is sending duplicate
delivery-tags. This leads to the producer being closed and unusable for any
further operations.
Setup:
QPID-J 7.16 broker cluster of 3 using BDB HA rep
21f5fd0753"
Does that meet your requirements?
Thanks,
Rob
On Wed, 6 Nov 2019 at 01:54, Timo Naroska
wrote:
> https://issues.apache.org/jira/browse/QPID-8373
>
> Thanks,
> Timo
>
> On 11/5/19, 3:53 PM, "Olek
ov 2019 at 10:11, Rob Godfrey wrote:
> Hi
>
> On Tue, 19 Nov 2019 at 00:27, Timo Naroska
> wrote:
>
>> Hi,
>>
>> we’re using Qpid’s message grouping feature and are sending messages
>> through Qpid java client
Hi,
we’re using Qpid’s message grouping feature and are sending messages through
Qpid java client with the JMSXGroupID property. This is working great.
We noticed that when using the getMessageInfo REST API there is no way to
retrieve the groupId for enqueued messages.
There is no field in the
nsumer
number is reported in operational logs due to historical reasons.
I agree that it make more sense for this REST operation to provide the
consumer id in 'deliveredTo' field.
Please raise a JIRA to request the change.
Kind regards,
Alex
On
Hi,
for monitoring purposes we're looking for a way to retrieve the current
messages from a queue and which consumer, if any, is currently processing them.
I found the getMessageInfo operation on Queue objects which enumerates
messages. I can determine messages that are currently processed by f
Hi,
we're trying to set up Broker J 7.1.4 / Qpid JMS 0.44.0 to retry messages on
failure.
On broker side, the queue is set up with Maximum Delivery Attempts = 5.
On client side, we set a JmsDefaultRedeliveryPolicy with setMaxRedeliveries(5).
The client is not transacted, using Session.AUTO_ACKNO
