Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
MIME-Version: 1.0
In-Reply-To: <5694D09E.3040604@redhat.com>
References: 
 <CAMsD-yDWkPJREqMU10PQskXqEbM=GdQAZvo+Ce8ggep2NE4yFg@mail.gmail.com>
	<5693F146.8080601@redhat.com>
	<CAMsD-yCSkANYsZhjLazuihA940-Fcf=NM0z4QyLp+3gcaYMjWg@mail.gmail.com>
	<CAMsD-yD2sOXE2Nf74L=a6cHAqhmKEW6-A2smPG6S4VOd_iHivw@mail.gmail.com>
	<CAMsD-yBR3T45vcuV+G5bHP-GQ4JauTb4-z_1QohWKf9Apt912w@mail.gmail.com>
	<5694D09E.3040604@redhat.com>
Date: Tue, 12 Jan 2016 08:39:22 -0500
Message-ID: 
 <CAMsD-yAxiNSvOU30t=j+xugYYFCPja5q_3K69xWuR6i3xuvgjw@mail.gmail.com>
Subject: Re: spurious ABRT in qpidd
From: Matt Broadstone <mbroadst@gmail.com>
To: users <users@qpid.apache.org>
Content-Type: multipart/alternative; boundary=001a11c32ddc615d810529232e72

--001a11c32ddc615d810529232e72
Content-Type: text/plain; charset=UTF-8

On Tue, Jan 12, 2016 at 5:08 AM, Gordon Sim <gsim@redhat.com> wrote:

> On 01/11/2016 09:29 PM, Matt Broadstone wrote:
>
>> Looks like I did just get a valid assertion, but I'm not even clear
>> anymore
>> whether this is related to the initially reported bug (since we're trying
>> to throw the kitchen sink at it to cause ABRTs). The log indicated:
>>
>> 2016-01-11 21:21:21 [Broker] debug clean(): 0 messages remain; head is
>> now 0
>> 2016-01-11 21:21:21 [Broker] trace qpid.127.0.0.1:5672-127.0.0.1:56687
>> handling outgoing delivery for 0x7f3fdc262590 on session 0x7f3fdc111650
>> qpidd:
>>
>> /build/qpid-cpp-RtJ4Dg/qpid-cpp-0.34/src/qpid/broker/amqp/Outgoing.cpp:115:
>> virtual void
>> qpid::broker::amqp::OutgoingFromQueue::handle(pn_delivery_t*):
>> Assertion `r.delivery == delivery' failed.
>>
>
> Do you have the core for that? If so can you check the values of
> 'delivery' and 'r.delivery'? Is either of them 0?
>
>
>
Hi Gordon,
I unfortunately don't have access to the box at the moment (and won't for a
few hours, if its even still in a reproducible state), but I'll try to get
a core next time. In the meantime, do you have any ideas for values I
should check on the sending side that might cause this? I can certainly
look through all of that code and see if I can make a smaller case that
exhibits this behavior.

Matt


>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>

--001a11c32ddc615d810529232e72--