You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by Michael Goulish <mg...@redhat.com> on 2013/02/18 00:05:22 UTC
p-200 is a release blocker
Not immediately obvious from the Jira, but PROTON-200 means that if you set up a simple topology -- one receiver, two senders -- the second sender will block until the first one calls 'stop'. This is still true in 0.4 RC1.
I think that needs to be fixed before release.
Re: p-200 is a release blocker
Posted by Michael Goulish <mg...@redhat.com>.
True, I think I may be running into some of those now.
I will start with a clean F18 system, download your RC1 tarball,
follow the instructions, take notes of what I see, and post here.
----- Original Message -----
From: "Rafael Schloming" <rh...@alum.mit.edu>
To: proton@qpid.apache.org
Sent: Monday, February 18, 2013 9:01:11 AM
Subject: Re: p-200 is a release blocker
It's actually already marked for 0.4. I believe ken is working on a fix. I
put out the RC1 anyways because I figured there would be fallout from the
build changes to work through anyways.
--Rafael
On Sun, Feb 17, 2013 at 6:05 PM, Michael Goulish <mg...@redhat.com>wrote:
>
> Not immediately obvious from the Jira, but PROTON-200 means that if you
> set up a simple topology -- one receiver, two senders -- the second sender
> will block until the first one calls 'stop'. This is still true in 0.4 RC1.
>
> I think that needs to be fixed before release.
>
>
Re: p-200 is a release blocker
Posted by Rafael Schloming <rh...@alum.mit.edu>.
It's actually already marked for 0.4. I believe ken is working on a fix. I
put out the RC1 anyways because I figured there would be fallout from the
build changes to work through anyways.
--Rafael
On Sun, Feb 17, 2013 at 6:05 PM, Michael Goulish <mg...@redhat.com>wrote:
>
> Not immediately obvious from the Jira, but PROTON-200 means that if you
> set up a simple topology -- one receiver, two senders -- the second sender
> will block until the first one calls 'stop'. This is still true in 0.4 RC1.
>
> I think that needs to be fixed before release.
>
>