I'm good with that list.

DISPATCH-881 is already on the 1.0.x branch.

I've taken the liberty to create pull requests for the backports of
DISPATCH-914, 889, and 882.

-K

On Mon, Feb 12, 2018 at 11:36 AM, Ted Ross <[email protected]> wrote:
> I've moved eleven jiras into 1.0.1 for consideration.  These are all
> resolved and are candidates for backport into 1.0.1.
>
>     DISPATCH-874 - unable to load .json or .woff2 files from local
> file system from http port
>     DISPATCH-881 - Inbound pre-settled messages causes memory leak of 
> deliveries
>     DISPATCH-882 - router buffers messages for slow presettled receiver
>     DISPATCH-883 - Router crashes when it processes management request
> for connections
>     DISPATCH-887 - Dispatch reestablishes connection inspite of
> deleting the connector
>     DISPATCH-889 - linkRoute patterns beginning with #/string match
> substrings after the /
>     DISPATCH-895 - qpid-dispatch crashes with a SEGFAULT in libqpid-proton
>     DISPATCH-900 - Memory leak when repeatedly opening and closing connections
>     DISPATCH-908 - Router loses dispositions over receive link on
> qpid-interop-test 2-node test
>     DISPATCH-914 - qd_connector_t leaks mutexes
>     DISPATCH-920 - Enabled policy blocks inter-router links
>
> -Ted
>
> On Fri, Feb 9, 2018 at 8:03 AM, Ted Ross <[email protected]> wrote:
>> I agree.  Let's do a 1.0.1 with this fix.
>>
>> -Ted
>>
>> On Wed, Feb 7, 2018 at 2:54 PM, Ken Giusti <[email protected]> wrote:
>>> Folks,
>>>
>>> Can we get a fix release for qpid-dispatch containing the fix to
>>> https://issues.apache.org/jira/browse/DISPATCH-881 ?
>>>
>>> This fixes a per-delivery leak that's present in the 1.0.0 release.  This
>>> is a per-message leak that causes the router's memory use to climb linear
>>> to the amount of traffic handled.
>>>
>>> thanks
>>>
>>> --
>>> -K
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>



-- 
-K

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to