You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Arjen van der Meijden <ac...@tweakers.net> on 2018/11/02 09:41:58 UTC
Re: Broker redelivery predispatch check across consumers is not
working
We have roughly the same issue, did you find a solution yet?
We use Stomp queue consumers with which we had a message that caused a
crash, the consumer restarted, crashed again, etc.
Obviously the crashing part is our responsibility, but we wanted to see
if we could prevent endless resends from ActiveMQ and ran into this same
scenario with redelivery regardless of redeliveryPolicy-rules.
Best regards,
Arjen
On 30-10-2018 04:32, djdkedev wrote:
> Thank you for quick response.
>
> ActiveMQ Version:5.15.6
>
> I want to test the broker redelivery predispatch check, therefore
> jms.redeliveryPolicy.maximumRedeliveries is set to zero at consumer level.
> Even though there is no mismatch, the redelivery counter goes beyond what is
> set in the redelivery plugin.The message got redelivered more than 20 times.
> I observed the same behavior when jms.redeliveryPolicy.maximumRedeliveries
> is 1 or 0 on client side.
> I kept it zero because
> http://activemq.2283324.n4.nabble.com/redeliveryPlugin-seems-to-have-problems-with-defaultEntry-td4685094.html
> suggested to keep it zero to avoid conflict between client redelivery and
> broker redelivery.
>
> Message:ActiveMQTextMessage {commandId = 6, responseRequired = true,
> messageId = ID:T320-2881-1540869039378-6:1:1:1:1, originalDestination =
> null, originalTransactionId = null, producerId =
> ID:T320-2881-1540869039378-6:1:1:1, destination = queue://DATAITEM_QUEUE,
> transactionId = null, expiration = 0, timestamp = 1540869039752, arrival =
> 0, brokerInTime = 1540869039763, brokerOutTime = 1540869640172,
> correlationId = ee0676b859f9af68, replyTo = null, persistent = false, type =
> null, priority = 4, groupID = null, groupSequence = 0, targetConsumerId =
> null, compressed = false, userID = null, content =
> org.apache.activemq.util.ByteSequence@619a52c3, marshalledProperties = null,
> dataStructure = null, *redeliveryCounter = 21*, size = 0, properties = null,
> readOnlyProperties = true, readOnlyBody = true, droppable = false,
> jmsXGroupFirstForConsumer = false, text = Item:1,
> CorelationId:ee0676b859f9af68}
>
> Hope this helps.
>
>
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>
Re: Broker redelivery predispatch check across consumers is not
working
Posted by Arjen van der Meijden <ac...@tweakers.net>.
Sure I created this issue: https://issues.apache.org/jira/browse/AMQ-7090
Best regards,
Arjen
On 2-11-2018 13:32, Tim Bain wrote:
> This sounds like a bug. Can one of you please submit a bug in JIRA for it?
>
> Tim
>
> On Fri, Nov 2, 2018, 3:42 AM Arjen van der Meijden <acmmailing@tweakers.net
> wrote:
>
>> We have roughly the same issue, did you find a solution yet?
>> We use Stomp queue consumers with which we had a message that caused a
>> crash, the consumer restarted, crashed again, etc.
>>
>> Obviously the crashing part is our responsibility, but we wanted to see
>> if we could prevent endless resends from ActiveMQ and ran into this same
>> scenario with redelivery regardless of redeliveryPolicy-rules.
>>
>> Best regards,
>>
>> Arjen
>>
>> On 30-10-2018 04:32, djdkedev wrote:
>>> Thank you for quick response.
>>>
>>> ActiveMQ Version:5.15.6
>>>
>>> I want to test the broker redelivery predispatch check, therefore
>>> jms.redeliveryPolicy.maximumRedeliveries is set to zero at consumer
>> level.
>>> Even though there is no mismatch, the redelivery counter goes beyond
>> what is
>>> set in the redelivery plugin.The message got redelivered more than 20
>> times.
>>> I observed the same behavior when
>> jms.redeliveryPolicy.maximumRedeliveries
>>> is 1 or 0 on client side.
>>> I kept it zero because
>>>
>> http://activemq.2283324.n4.nabble.com/redeliveryPlugin-seems-to-have-problems-with-defaultEntry-td4685094.html
>>> suggested to keep it zero to avoid conflict between client redelivery and
>>> broker redelivery.
>>>
>>> Message:ActiveMQTextMessage {commandId = 6, responseRequired = true,
>>> messageId = ID:T320-2881-1540869039378-6:1:1:1:1, originalDestination =
>>> null, originalTransactionId = null, producerId =
>>> ID:T320-2881-1540869039378-6:1:1:1, destination = queue://DATAITEM_QUEUE,
>>> transactionId = null, expiration = 0, timestamp = 1540869039752, arrival
>> =
>>> 0, brokerInTime = 1540869039763, brokerOutTime = 1540869640172,
>>> correlationId = ee0676b859f9af68, replyTo = null, persistent = false,
>> type =
>>> null, priority = 4, groupID = null, groupSequence = 0, targetConsumerId =
>>> null, compressed = false, userID = null, content =
>>> org.apache.activemq.util.ByteSequence@619a52c3, marshalledProperties =
>> null,
>>> dataStructure = null, *redeliveryCounter = 21*, size = 0, properties =
>> null,
>>> readOnlyProperties = true, readOnlyBody = true, droppable = false,
>>> jmsXGroupFirstForConsumer = false, text = Item:1,
>>> CorelationId:ee0676b859f9af68}
>>>
>>> Hope this helps.
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Sent from:
>> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: Broker redelivery predispatch check across consumers is not working
Posted by Tim Bain <tb...@alumni.duke.edu>.
This sounds like a bug. Can one of you please submit a bug in JIRA for it?
Tim
On Fri, Nov 2, 2018, 3:42 AM Arjen van der Meijden <acmmailing@tweakers.net
wrote:
> We have roughly the same issue, did you find a solution yet?
> We use Stomp queue consumers with which we had a message that caused a
> crash, the consumer restarted, crashed again, etc.
>
> Obviously the crashing part is our responsibility, but we wanted to see
> if we could prevent endless resends from ActiveMQ and ran into this same
> scenario with redelivery regardless of redeliveryPolicy-rules.
>
> Best regards,
>
> Arjen
>
> On 30-10-2018 04:32, djdkedev wrote:
> > Thank you for quick response.
> >
> > ActiveMQ Version:5.15.6
> >
> > I want to test the broker redelivery predispatch check, therefore
> > jms.redeliveryPolicy.maximumRedeliveries is set to zero at consumer
> level.
> > Even though there is no mismatch, the redelivery counter goes beyond
> what is
> > set in the redelivery plugin.The message got redelivered more than 20
> times.
> > I observed the same behavior when
> jms.redeliveryPolicy.maximumRedeliveries
> > is 1 or 0 on client side.
> > I kept it zero because
> >
> http://activemq.2283324.n4.nabble.com/redeliveryPlugin-seems-to-have-problems-with-defaultEntry-td4685094.html
> > suggested to keep it zero to avoid conflict between client redelivery and
> > broker redelivery.
> >
> > Message:ActiveMQTextMessage {commandId = 6, responseRequired = true,
> > messageId = ID:T320-2881-1540869039378-6:1:1:1:1, originalDestination =
> > null, originalTransactionId = null, producerId =
> > ID:T320-2881-1540869039378-6:1:1:1, destination = queue://DATAITEM_QUEUE,
> > transactionId = null, expiration = 0, timestamp = 1540869039752, arrival
> =
> > 0, brokerInTime = 1540869039763, brokerOutTime = 1540869640172,
> > correlationId = ee0676b859f9af68, replyTo = null, persistent = false,
> type =
> > null, priority = 4, groupID = null, groupSequence = 0, targetConsumerId =
> > null, compressed = false, userID = null, content =
> > org.apache.activemq.util.ByteSequence@619a52c3, marshalledProperties =
> null,
> > dataStructure = null, *redeliveryCounter = 21*, size = 0, properties =
> null,
> > readOnlyProperties = true, readOnlyBody = true, droppable = false,
> > jmsXGroupFirstForConsumer = false, text = Item:1,
> > CorelationId:ee0676b859f9af68}
> >
> > Hope this helps.
> >
> >
> >
> >
> >
> > --
> > Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
> >
>