Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of jason.dillon@gmail.com
 designates 209.85.161.171 as permitted sender)
Sender: Jason Dillon <jason.dillon@gmail.com>
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1251.1)
Subject: Re: How to tell why message sent to DLQ?
From: Jason Dillon <jason@planet57.com>
In-Reply-To: <982B674D-BD67-469B-8AFF-15CD0641F300@planet57.com>
Date: Sat, 21 Jan 2012 15:07:54 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <A0F2603F-9D18-4970-B8F0-5E4E405F21EA@planet57.com>
References: <88AFC357-B2AE-4821-8841-5F39A8BC9FAC@planet57.com>
 <CAH+vQmNqga+GTvstRv5f58aRd0bAga2evcpXrwdt_JG8FzHWkg@mail.gmail.com>
 <0C7EEBF1-89C6-4A91-8393-ECB3A2B39C14@planet57.com>
 <CAH+vQmN_q1wACAAQ8xQ3p+0W35JUN5C-ew1+2PD=eab8Qe1vbA@mail.gmail.com>
 <AF0AC563-BBBE-4BA2-A273-9CB1EA0BC224@planet57.com>
 <CAH+vQmPsEFRrWkDEmDnigm76g+Vyafk9Fnj_g1ZaLAYUCC7Riw@mail.gmail.com>
 <982B674D-BD67-469B-8AFF-15CD0641F300@planet57.com>
To: users@activemq.apache.org

BTW, is there an easy way to via JMX look at the DLQ messages and =
determine if they were sent here due to expiration?  I didn't see any =
hints when I looked that the messages had been expired and thus sent to =
the DLQ.  Perhaps the messages should get a property attached to explain =
the reason for DLQ delivery?  Something like a "dlqDeliveryReason" which =
could be "expired" or "failure" and on "failure" you can go look at =
"dlqDeliveryFailureCause" for more detail.

Are there any other reasons why a message might be sent to the DLQ?

--jason


On Jan 21, 2012, at 2:29 PM, Jason Dillon wrote:

> Doh!  I didn't realize (or maybe I just forgot) that expired messages =
are sent to the DLQ by default.
>=20
> I also didn't realize that the JMSDestination on messages sent to a =
virtual topic will retain the virtual topic destination and not the =
consumer queue destination.
>=20
> --jason
>=20
> On Jan 20, 2012, at 2:20 AM, Gary Tully wrote:
>=20
>> =
org.apache.activemq.broker.region.virtual.VirtualTopicInterceptor#send
>>=20
>> which calls: org.apache.activemq.broker.region.DestinationFilter#send
>>=20
>> On 20 January 2012 01:48, Jason Dillon <jason@planet57.com> wrote:
>>> Can you point me at the code which handles virtual topic =
subscription message propagation to consumer queues plz?
>>>=20
>>> --jason
>>>=20
>>>=20
>>> On Jan 19, 2012, at 12:36 PM, Gary Tully wrote:
>>>=20
>>>> should be, but the use case is narrow, see the test case:
>>>> =
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/or=
g/apache/activemq/MessageListenerRedeliveryTest.java?r1=3D1084175&r2=3D108=
4174&pathrev=3D1084175
>>>>=20
>>>> On 19 January 2012 19:09, Jason Dillon <jason@planet57.com> wrote:
>>>>> Is this change in 5.5.1 and enabled by default?
>>>>>=20
>>>>> If so I don't see any of these properties set.
>>>>>=20
>>>>> --jason
>>>>>=20
>>>>>=20
>>>>> On Jan 19, 2012, at 7:32 AM, Gary Tully wrote:
>>>>>=20
>>>>>> For one use case, when a exception causes a rollback, that =
exception
>>>>>> is trapped. Have a peek at
>>>>>> https://issues.apache.org/jira/browse/AMQ-3236 and the associated
>>>>>> commits. We may be able to build on that.
>>>>>>=20
>>>>>> On 19 January 2012 05:58, Jason Dillon <jason@planet57.com> =
wrote:
>>>>>>> Is there any easy way to get information about why a message had =
been sent to ActiveMQ.DLQ?
>>>>>>>=20
>>>>>>> I'm seeing a bunch of messages sent to a virtual topic (as =
indicated by OriginalDestination property while browsing the =
ActiveMQ.DLQ via visualvm,  which end up in the DLQ.  Really unsure why =
any message sent to a virtual topic would end up here.  Shouldn't the =
virtual topic simply copy the message to all known client's and be done =
with it?
>>>>>>>=20
>>>>>>> More generally though, is there any way to include detail in the =
message when sent to the DLQ as to why it was sent there?
>>>>>>>=20
>>>>>>> --jason
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> --
>>>>>> http://fusesource.com
>>>>>> http://blog.garytully.com
>>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> --
>>>> http://fusesource.com
>>>> http://blog.garytully.com
>>>=20
>>=20
>>=20
>>=20
>> --=20
>> http://fusesource.com
>> http://blog.garytully.com
>=20