This is certainly not caused by a large message which exceeded the journal
file size. That kind of error would be seen when the message was *sent*.
This error is occurring when the message is being acknowledged.
A couple of questions...
- Is this something which you've been able to reproduce in testing or
development?
- What's the use-case involved here?
- There is nothing in the broker that would retry this operation. Do you
know why this operation is getting retried in a loop? I assume it's
something in your application. Can you confirm?
- What queue is being created and destroyed? How is that queue related to
your application (it at all)?
- What version of ActiveMQ Artemis are you using?
Justin
Justin
On Thu, Mar 2, 2023 at 12:02 PM Ekta Awasthi
<ekta.awas...@theodpcorp.com.invalid> wrote:
> Hello,
>
> I am in need of some help as to why the exception below occurs in broker
> logs though it is not continuous but definitely intermittent. I am trying
> to understand if this is caused by a largemessage which exceeded the
> journal file size? Have observed that if this message goes into loop of
> retries, the broker is destroying queues and recreating queues in a loop.
> Would be great if someone can shed some light on the error for me to better
> understand. Thanks
>
>
>
> 2023-03-01 11:40:30,197 WARN
> [org.apache.activemq.artemis.protocol.amqp.proton.handler.ProtonHandler]
> AMQ119008: error cancelling message AMQPLargeMessage( [durable=true,
> messageID=180227946434, address=test.unicast, size=0,
>
> applicationProperties{}
>
> Cannot find ref to ack 180227946434
>
>
>
> Ekta Awasthi
>
> CONFIDENTIALITY NOTICE: The information contained in this email and
> attached document(s) may contain confidential information that is intended
> only for the addressee(s). If you are not the intended recipient, you are
> hereby advised that any disclosure, copying, distribution or the taking of
> any action in reliance upon the information is prohibited. If you have
> received this email in error, please immediately notify the sender and
> delete it from your system.
>
