Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Rafael Schloming]

 <http://0.0.0.0/TPRBOX@%5Cx83%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx83%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00@R%5Cx00@%5Cx00Sw%5Cxa0%5Cxa1%5Cx08%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx8c#%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00>
>> >>
>> !\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00alma\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
>> >>
>> \x00\x00\x00alma\x00\x00\x00\x00\x00\x00\x00\x00\x00\x1aR\xfc\xff\x7f\x00\x00%\x00\x00\x0024.10.14
>> >> 21:21:04 ALMA apl_start:
>> >> OK\x0a\x00[28883]"
>> >> [0x129d770]:0 <- @flow(19) [next-incoming-id=1,
>> >> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=0,
>> handle=0,
>> >> delivery-count=1, link-credit=100, drain=false]
>> >> [0x129d770]:0 -> @transfer(20) [handle=0, delivery-id=2,
>> >> delivery-tag=b"\x02\x00\x00\x00\x00\x00\x00\x00", message-format=0,
>> >> settled=true, more=false] (281)
>> >> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR
>> >> \x00\x00Ss\xd0\x00\x00\x008\x00\x00\x00\x0d@@\xa1\x15amqp://
>> >>
>> 0.0.0.0/TPRBOX@\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa0\xc1\x08\x00\x00\x00\x00\x00\x00\x00\x8c#\x00\x00\x00\x00\x00\x00
>> <http://0.0.0.0/TPRBOX@%5Cx83%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx83%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00@R%5Cx00@%5Cx00Sw%5Cxa0%5Cxc1%5Cx08%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx8c#%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00>
>> >>
>> !\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00alma\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
>> >>
>> \x00\x00\x00alma\x00\x07\x0a\x00\x18\x00\x15\x00\x15\x00\x04\x00L\x00\x00\x00E\x00\x00\x0024.10.14
>> >> 21:21:04 ALMA Connecting to
>> >> oracle database as omgr@CCS_APP\x0a\x00R\xfc\xff\x7f\x00\x00P"
>> >> [0x129d770]:0 -> @transfer(20) [handle=0, delivery-id=3,
>> >> delivery-tag=b"\x03\x00\x00\x00\x00\x00\x00\x00", message-format=0,
>> >> settled=true, more=false] (284)
>> >> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR
>> >> \x00\x00Ss\xd0\x00\x00\x008\x00\x00\x00\x0d@@\xa1\x15amqp://
>> >>
>> 0.0.0.0/TPRBOX@\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa0\xc4\x08\x00\x00\x00\x00\x00\x00\x00\x8c#\x00\x00\x00\x00\x00\x00
>> <http://0.0.0.0/TPRBOX@%5Cx83%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx83%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00@R%5Cx00@%5Cx00Sw%5Cxa0%5Cxc4%5Cx08%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx8c#%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00%5Cx00>
>> >>
>> !\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00alma\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
>> >>
>> \x00\x00\x00alma\x00\x13R\xfc\xff\x7f\x00\x00b\xf7F\x999\x00\x00\x00H\x00\x00\x0024.10.14
>> >> 21:21:04 ALMA Oracle database
>> >> connected as user "omgr@CCS_APP"\x0a\x00\x00\x00\x00gT\xfc\x18"
>> >> [0x129d770]:0 <- @flow(19) [next-incoming-id=2,
>> >> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=0,
>> handle=0,
>> >> delivery-count=2, link-credit=100, drain=false]
>> >> [0x129d770]:0 <- @flow(19) [next-incoming-id=3,
>> >> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=0,
>> handle=0,
>> >> delivery-count=3, link-credit=100, drain=false]
>> >> [0x12862d0]:0 <- @open(16)
>> >> [container-id="e5584c39-5ae9-4fad-ba53-2528475d71ba"]
>> >> [0x12862d0]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
>> >> incoming-window=2147483647, outgoing-window=0]
>> >> [0x12862d0]:0 <- @attach(18) [name="TPRBOX", handle=0, role=false,
>> >> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40)
>> >> [address="TPRBOX", durable=0, timeout=0, dynamic=false],
>> >> target=@target(41) [durable=0, timeout=0, dynamic=false],
>> >> initial-delivery-count=0]
>> >> [0

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Rafael Schloming]

00\x00\x1aR\xfc\xff\x7f\x00\x00%\x00\x00\x0024.10.14
> >> 21:21:04 ALMA apl_start:
> >> OK\x0a\x00[28883]"
> >> [0x129d770]:0 <- @flow(19) [next-incoming-id=1,
> >> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=0,
> handle=0,
> >> delivery-count=1, link-credit=100, drain=false]
> >> [0x129d770]:0 -> @transfer(20) [handle=0, delivery-id=2,
> >> delivery-tag=b"\x02\x00\x00\x00\x00\x00\x00\x00", message-format=0,
> >> settled=true, more=false] (281)
> >> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR
> >> \x00\x00Ss\xd0\x00\x00\x008\x00\x00\x00\x0d@@\xa1\x15amqp://
> >>
> 0.0.0.0/TPRBOX@\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa0\xc1\x08\x00\x00\x00\x00\x00\x00\x00\x8c#\x00\x00\x00\x00\x00\x00
> >>
> !\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00alma\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
> >>
> \x00\x00\x00alma\x00\x07\x0a\x00\x18\x00\x15\x00\x15\x00\x04\x00L\x00\x00\x00E\x00\x00\x0024.10.14
> >> 21:21:04 ALMA Connecting to
> >> oracle database as omgr@CCS_APP\x0a\x00R\xfc\xff\x7f\x00\x00P"
> >> [0x129d770]:0 -> @transfer(20) [handle=0, delivery-id=3,
> >> delivery-tag=b"\x03\x00\x00\x00\x00\x00\x00\x00", message-format=0,
> >> settled=true, more=false] (284)
> >> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR
> >> \x00\x00Ss\xd0\x00\x00\x008\x00\x00\x00\x0d@@\xa1\x15amqp://
> >>
> 0.0.0.0/TPRBOX@\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa0\xc4\x08\x00\x00\x00\x00\x00\x00\x00\x8c#\x00\x00\x00\x00\x00\x00
> >>
> !\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00alma\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
> >>
> \x00\x00\x00alma\x00\x13R\xfc\xff\x7f\x00\x00b\xf7F\x999\x00\x00\x00H\x00\x00\x0024.10.14
> >> 21:21:04 ALMA Oracle database
> >> connected as user "omgr@CCS_APP"\x0a\x00\x00\x00\x00gT\xfc\x18"
> >> [0x129d770]:0 <- @flow(19) [next-incoming-id=2,
> >> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=0,
> handle=0,
> >> delivery-count=2, link-credit=100, drain=false]
> >> [0x129d770]:0 <- @flow(19) [next-incoming-id=3,
> >> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=0,
> handle=0,
> >> delivery-count=3, link-credit=100, drain=false]
> >> [0x12862d0]:0 <- @open(16)
> >> [container-id="e5584c39-5ae9-4fad-ba53-2528475d71ba"]
> >> [0x12862d0]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
> >> incoming-window=2147483647, outgoing-window=0]
> >> [0x12862d0]:0 <- @attach(18) [name="TPRBOX", handle=0, role=false,
> >> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40)
> >> [address="TPRBOX", durable=0, timeout=0, dynamic=false],
> >> target=@target(41) [durable=0, timeout=0, dynamic=false],
> >> initial-delivery-count=0]
> >> [0x129d770]:0 -> @transfer(20) [handle=0, delivery-id=4,
> >> delivery-tag=b"\x04\x00\x00\x00\x00\x00\x00\x00", message-format=0,
> >> settled=true, more=false] (253)
> >> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR
> >> \x00\x00Ss\xd0\x00\x00\x008\x00\x00\x00\x0d@@\xa1\x15amqp://
> >>
> 0.0.0.0/TPRBOX@\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa0\xa5\x08\x00\x00\x00\x00\x00\x00\x00\x8c#\x00\x00\x00\x00\x00\x00
> >>
> !\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00alma\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
> >>
> \x00\x00\x00alma\x00\x13R\xfc\xff\x7f\x00\x00b\xf7F\x999\x00\x00\x00)\x00\x00\x0024.10.14
> >> 21:21:04 ALMA apl_start_ora:
> >> OK\x0a\x00nected "
> >> [0x129d770]:0 <- @flow(19) [next-incoming-id=4,
> >> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=0,
> handle=0,
> >> delivery-count=4, link-credit=100, drain=false]
> >>
> >> Best regards,
> >>
> >> 24.10.2014 22:36, Rafael Schloming пишет:
> >>> You can

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Michael Ivanov]

00\x00H\x00\x00\x0024.10.14
>> 21:21:04 ALMA Oracle database
>> connected as user "omgr@CCS_APP"\x0a\x00\x00\x00\x00gT\xfc\x18"
>> [0x129d770]:0 <- @flow(19) [next-incoming-id=2,
>> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=0, handle=0,
>> delivery-count=2, link-credit=100, drain=false]
>> [0x129d770]:0 <- @flow(19) [next-incoming-id=3,
>> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=0, handle=0,
>> delivery-count=3, link-credit=100, drain=false]
>> [0x12862d0]:0 <- @open(16)
>> [container-id="e5584c39-5ae9-4fad-ba53-2528475d71ba"]
>> [0x12862d0]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
>> incoming-window=2147483647, outgoing-window=0]
>> [0x12862d0]:0 <- @attach(18) [name="TPRBOX", handle=0, role=false,
>> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40)
>> [address="TPRBOX", durable=0, timeout=0, dynamic=false],
>> target=@target(41) [durable=0, timeout=0, dynamic=false],
>> initial-delivery-count=0]
>> [0x129d770]:0 -> @transfer(20) [handle=0, delivery-id=4,
>> delivery-tag=b"\x04\x00\x00\x00\x00\x00\x00\x00", message-format=0,
>> settled=true, more=false] (253)
>> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR
>> \x00\x00Ss\xd0\x00\x00\x008\x00\x00\x00\x0d@@\xa1\x15amqp://
>> 0.0.0.0/TPRBOX@\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa0\xa5\x08\x00\x00\x00\x00\x00\x00\x00\x8c#\x00\x00\x00\x00\x00\x00
>> !\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00alma\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
>> \x00\x00\x00alma\x00\x13R\xfc\xff\x7f\x00\x00b\xf7F\x999\x00\x00\x00)\x00\x00\x0024.10.14
>> 21:21:04 ALMA apl_start_ora:
>> OK\x0a\x00nected "
>> [0x129d770]:0 <- @flow(19) [next-incoming-id=4,
>> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=0, handle=0,
>> delivery-count=4, link-credit=100, drain=false]
>>
>> Best regards,
>>
>> 24.10.2014 22:36, Rafael Schloming пишет:
>>> You can check out the trunk source code from here:
>>>
>>> http://svn.apache.org/repos/asf/qpid/proton/trunk/
>>>
>>> You should be able to turn on the protocol trace by setting the
>>> PN_TRACE_FRM environment variable to 1, e.g.:
>>>
>>>   export PN_TRACE_FRM=1
>>>   run-client-program
>>>
>>> You will need to do this on the server side as well in order to get the
>>> server's version of the protocol trace.
>>>
>>> --Rafael
>>>
>>>
>>> On Fri, Oct 24, 2014 at 2:31 PM, Michael Ivanov 
>> wrote:
>>>
>>>> Sorry, should I check out the trunk from the repository or can I
>> download
>>>> the new sources tar archive from somewhere? The last version I used I
>> have
>>>> downloaded from
>>>> http://people.apache.org/~rhs/qpid-proton-0.8rc4/qpid-proton-0.8.tar.gz
>>>> If the sources are to be checked out which url should I use?
>>>>
>>>> And pls can you explain me how to turn the proitocol trace on? Or
>> should I
>>>> just tcpdump during exchange?
>>>>
>>>> Best regards,
>>>>
>>>> 24.10.2014 22:24, Rafael Schloming пишет:
>>>>> Hi Michael,
>>>>>
>>>>> I just committed the change Ken suggested to at least fix the abort. Is
>>>>> there any way you could retest with trunk?
>>>>>
>>>>> If the problem still occurs (I expect it will, just not quite so
>> fatally)
>>>>> it would be good to get the protocol trace for both the client and the
>>>>> server and see if that will shed some light on what is going on.
>>>>>
>>>>> --Rafael
>>>>>
>>>>>
>>>>> On Fri, Oct 24, 2014 at 2:00 PM, Michael Ivanov 
>>>> wrote:
>>>>>
>>>>>> I just rebuilt all client processes to use proton 0.8 (it was still
>> 0.7
>>>>>> before)
>>>>>> Error is still the same.
>>>>>>
>>>>>> Best regards,
>>>>>>
>>>>>> 24.10.2014 18:16, Ken Giusti пишет:
>>>>>>> >From the trace, it seems like the broker is receiving a transfer
>> whose
>>>>>> delivery id is o

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Chuck Rolke]

The mailing list scrubs attachments so it didn't get included.

You can create an issue at 
https://issues.apache.org/jira/secure/CreateIssue.jspa?pid=12313720&issuetype=1&priority=3

and post the trace there.

-Chuck

- Original Message -
> From: "Michael Ivanov" 
> To: proton@qpid.apache.org
> Sent: Friday, October 24, 2014 5:02:43 PM
> Subject: Re: VOTE: Release Proton 0.8 RC4 as 0.8 final
> 
> Hallo Rafael,
> 
> Sorry, but this time I have to attach a file :-) (I was usually trying to
> avoid it because sending to mailing list) But qpidd trace is uncompressed
> 2Mb, compressed 80Kb
> 
> So compressed qpidd log is attached.
> 
> Best regards,
> 
> 25.10.2014 00:41, Rafael Schloming пишет:
> > Hi Michael,
> > 
> > Sorry for misleading you. I think the way qpidd integrates proton must
> > override the PN_TRACE_FRM configuration. I believe you should be able to
> > get the protocol trace from the broker by using the -t option, e.g. "qpidd
> > -t". I'll take a look at the logs you posted, however I suspect the most
> > useful one will be the broker trace, so I would appreciate any effort you
> > can make to obtain it.
> > 
> > Thanks,
> > 
> > --Rafael
> > 
> > 
> > On Fri, Oct 24, 2014 at 3:40 PM, Michael Ivanov  wrote:
> > 
> >> Ok I have some results. Now the core is not dumped but I have unusual
> >> delays
> >> during application startup. I have started qpidd up with PN_TRACE_FRM set,
> >> but do not see any trace output. Only thing I have are the following
> >> entries
> >> from syslog:
> >>
> >> Oct 24 21:17:24 ccsfat qpidd[28477]: 2014-10-24 21:17:24 [Broker] notice
> >> Broker 28477 initializing
> >> Oct 24 21:17:24 ccsfat qpidd[28477]: 2014-10-24 21:17:24 [Security] notice
> >> SSL plugin not enabled, you must set --ssl-cert-db to
> >> enable it.
> >> Oct 24 21:17:24 ccsfat qpidd[28477]: 2014-10-24 21:17:24 [Store] notice
> >> Journal "TplStore": Created
> >> Oct 24 21:17:24 ccsfat qpidd[28477]: 2014-10-24 21:17:24 [Store] notice
> >> Store module initialized; store-dir=/var/spool/qpid
> >> Oct 24 21:17:24 ccsfat qpidd[28477]: 2014-10-24 21:17:24 [Store] warning
> >> Message store plugin: No storage providers available.
> >> Oct 24 21:17:24 ccsfat qpidd[28477]: 2014-10-24 21:17:24 [Network] notice
> >> Listening on TCP/TCP6 port 5672
> >> Oct 24 21:17:24 ccsfat qpidd[28477]: 2014-10-24 21:17:24 [Broker] notice
> >> Broker 28477 initialized
> >> Oct 24 21:17:24 ccsfat qpidd[28477]: 2014-10-24 21:17:24 [Broker] notice
> >> Broker 28477 running
> >> Oct 24 21:21:04 ccsfat qpidd[28477]: 2014-10-24 21:21:04 [System] error
> >> Connection qpid.127.0.0.1:5672-127.0.0.1:39178 No
> >> protocol received closing
> >> Oct 24 21:21:04 ccsfat qpidd[28477]: 2014-10-24 21:21:04 [System] error
> >> Connection qpid.127.0.0.1:5672-127.0.0.1:39180 No
> >> protocol received closing
> >> Oct 24 21:21:04 ccsfat qpidd[28477]: 2014-10-24 21:21:04 [Management]
> >> error Detected two management objects with the same
> >> identifier:
> >> 0-5-1--174(org.apache.qpid.broker:incoming:aa8fef78-607a-4913-a9ba-f10972657cd7,sender-xxx)
> >> Oct 24 21:21:05 ccsfat qpidd[28477]: 2014-10-24 21:21:05 [System] error
> >> Connection qpid.127.0.0.1:5672-127.0.0.1:39182 No
> >> protocol received closing
> >> Oct 24 21:21:05 ccsfat qpidd[28477]: 2014-10-24 21:21:05 [System] error
> >> Connection qpid.127.0.0.1:5672-127.0.0.1:39184 No
> >> protocol received closing
> >> Oct 24 21:21:05 ccsfat qpidd[28477]: 2014-10-24 21:21:05 [System] error
> >> Connection qpid.127.0.0.1:5672-127.0.0.1:39186 No
> >> protocol received closing
> >> Oct 24 21:21:05 ccsfat qpidd[28477]: 2014-10-24 21:21:05 [System] error
> >> Connection qpid.127.0.0.1:5672-127.0.0.1:39188 No
> >> protocol received closing
> >> Oct 24 21:21:06 ccsfat qpidd[28477]: 2014-10-24 21:21:06 [System] error
> >> Connection qpid.127.0.0.1:5672-127.0.0.1:39195 No
> >> protocol received closing
> >>
> >> With client processes it's a little better. Here's the output from one of
> >> the
> >> processes:
> >>
> >> [0x82dd50]:  -> SASL
> >> [0x82dd50]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> >> initial-response=b""]
> >> [0x82dd50]:  <- SASL
> >> [0x82dd50]:0 <- @sasl-mechanisms(64)
> >> [sasl-server-mechanisms=@PN_SYMBOL[:ANONY

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Michael Ivanov]

24.10.14
>> 21:21:04 ALMA Oracle database
>> connected as user "omgr@CCS_APP"\x0a\x00\x00\x00\x00gT\xfc\x18"
>> [0x129d770]:0 <- @flow(19) [next-incoming-id=2,
>> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=0, handle=0,
>> delivery-count=2, link-credit=100, drain=false]
>> [0x129d770]:0 <- @flow(19) [next-incoming-id=3,
>> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=0, handle=0,
>> delivery-count=3, link-credit=100, drain=false]
>> [0x12862d0]:0 <- @open(16)
>> [container-id="e5584c39-5ae9-4fad-ba53-2528475d71ba"]
>> [0x12862d0]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
>> incoming-window=2147483647, outgoing-window=0]
>> [0x12862d0]:0 <- @attach(18) [name="TPRBOX", handle=0, role=false,
>> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40)
>> [address="TPRBOX", durable=0, timeout=0, dynamic=false],
>> target=@target(41) [durable=0, timeout=0, dynamic=false],
>> initial-delivery-count=0]
>> [0x129d770]:0 -> @transfer(20) [handle=0, delivery-id=4,
>> delivery-tag=b"\x04\x00\x00\x00\x00\x00\x00\x00", message-format=0,
>> settled=true, more=false] (253)
>> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR
>> \x00\x00Ss\xd0\x00\x00\x008\x00\x00\x00\x0d@@\xa1\x15amqp://
>> 0.0.0.0/TPRBOX@\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa0\xa5\x08\x00\x00\x00\x00\x00\x00\x00\x8c#\x00\x00\x00\x00\x00\x00
>> !\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00alma\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
>> \x00\x00\x00alma\x00\x13R\xfc\xff\x7f\x00\x00b\xf7F\x999\x00\x00\x00)\x00\x00\x0024.10.14
>> 21:21:04 ALMA apl_start_ora:
>> OK\x0a\x00nected "
>> [0x129d770]:0 <- @flow(19) [next-incoming-id=4,
>> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=0, handle=0,
>> delivery-count=4, link-credit=100, drain=false]
>>
>> Best regards,
>>
>> 24.10.2014 22:36, Rafael Schloming пишет:
>>> You can check out the trunk source code from here:
>>>
>>> http://svn.apache.org/repos/asf/qpid/proton/trunk/
>>>
>>> You should be able to turn on the protocol trace by setting the
>>> PN_TRACE_FRM environment variable to 1, e.g.:
>>>
>>>   export PN_TRACE_FRM=1
>>>   run-client-program
>>>
>>> You will need to do this on the server side as well in order to get the
>>> server's version of the protocol trace.
>>>
>>> --Rafael
>>>
>>>
>>> On Fri, Oct 24, 2014 at 2:31 PM, Michael Ivanov 
>> wrote:
>>>
>>>> Sorry, should I check out the trunk from the repository or can I
>> download
>>>> the new sources tar archive from somewhere? The last version I used I
>> have
>>>> downloaded from
>>>> http://people.apache.org/~rhs/qpid-proton-0.8rc4/qpid-proton-0.8.tar.gz
>>>> If the sources are to be checked out which url should I use?
>>>>
>>>> And pls can you explain me how to turn the proitocol trace on? Or
>> should I
>>>> just tcpdump during exchange?
>>>>
>>>> Best regards,
>>>>
>>>> 24.10.2014 22:24, Rafael Schloming пишет:
>>>>> Hi Michael,
>>>>>
>>>>> I just committed the change Ken suggested to at least fix the abort. Is
>>>>> there any way you could retest with trunk?
>>>>>
>>>>> If the problem still occurs (I expect it will, just not quite so
>> fatally)
>>>>> it would be good to get the protocol trace for both the client and the
>>>>> server and see if that will shed some light on what is going on.
>>>>>
>>>>> --Rafael
>>>>>
>>>>>
>>>>> On Fri, Oct 24, 2014 at 2:00 PM, Michael Ivanov 
>>>> wrote:
>>>>>
>>>>>> I just rebuilt all client processes to use proton 0.8 (it was still
>> 0.7
>>>>>> before)
>>>>>> Error is still the same.
>>>>>>
>>>>>> Best regards,
>>>>>>
>>>>>> 24.10.2014 18:16, Ken Giusti пишет:
>>>>>>> >From the trace, it seems like the broker is receiving a transfer
>> whose
>>>>>> delivery id is out of order.
>>&g

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Rafael Schloming]

00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00alma\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
> \x00\x00\x00alma\x00\x13R\xfc\xff\x7f\x00\x00b\xf7F\x999\x00\x00\x00)\x00\x00\x0024.10.14
> 21:21:04 ALMA apl_start_ora:
> OK\x0a\x00nected "
> [0x129d770]:0 <- @flow(19) [next-incoming-id=4,
> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=0, handle=0,
> delivery-count=4, link-credit=100, drain=false]
>
> Best regards,
>
> 24.10.2014 22:36, Rafael Schloming пишет:
> > You can check out the trunk source code from here:
> >
> > http://svn.apache.org/repos/asf/qpid/proton/trunk/
> >
> > You should be able to turn on the protocol trace by setting the
> > PN_TRACE_FRM environment variable to 1, e.g.:
> >
> >   export PN_TRACE_FRM=1
> >   run-client-program
> >
> > You will need to do this on the server side as well in order to get the
> > server's version of the protocol trace.
> >
> > --Rafael
> >
> >
> > On Fri, Oct 24, 2014 at 2:31 PM, Michael Ivanov 
> wrote:
> >
> >> Sorry, should I check out the trunk from the repository or can I
> download
> >> the new sources tar archive from somewhere? The last version I used I
> have
> >> downloaded from
> >> http://people.apache.org/~rhs/qpid-proton-0.8rc4/qpid-proton-0.8.tar.gz
> >> If the sources are to be checked out which url should I use?
> >>
> >> And pls can you explain me how to turn the proitocol trace on? Or
> should I
> >> just tcpdump during exchange?
> >>
> >> Best regards,
> >>
> >> 24.10.2014 22:24, Rafael Schloming пишет:
> >>> Hi Michael,
> >>>
> >>> I just committed the change Ken suggested to at least fix the abort. Is
> >>> there any way you could retest with trunk?
> >>>
> >>> If the problem still occurs (I expect it will, just not quite so
> fatally)
> >>> it would be good to get the protocol trace for both the client and the
> >>> server and see if that will shed some light on what is going on.
> >>>
> >>> --Rafael
> >>>
> >>>
> >>> On Fri, Oct 24, 2014 at 2:00 PM, Michael Ivanov 
> >> wrote:
> >>>
> >>>> I just rebuilt all client processes to use proton 0.8 (it was still
> 0.7
> >>>> before)
> >>>> Error is still the same.
> >>>>
> >>>> Best regards,
> >>>>
> >>>> 24.10.2014 18:16, Ken Giusti пишет:
> >>>>> >From the trace, it seems like the broker is receiving a transfer
> whose
> >>>> delivery id is out of order.
> >>>>>
> >>>>> This shouldn't cause an abort - likely the result is an untested
> >> failure
> >>>> path, in transport.c:781:
> >>>>>
> >>>>> if (id_present && id != state->id) {
> >>>>>   int err = pn_do_error(transport, "amqp:session:invalid-field",
> >>>>> "sequencing error, expected delivery-id
> %u,
> >>>> got %u",
> >>>>> state->id, id);
> >>>>> > // XXX: this will probably leave delivery buffer state messed
> up
> >>>>>   pn_full_settle(incoming, delivery);
> >>>>>   return err;
> >>>>> }
> >>>>>
> >>>>> It doesn't explain why a transfer is sent out of order by the client,
> >>>> but at least we probably should remove the attempt to
> pn_full_settle(),
> >> and
> >>>> just return the error to fail the connection (assumed - totally
> >> untested).
> >>>>>
> >>>>> -K
> >>>>>
> >>>>> - Original Message -
> >>>>>> From: "Michael Ivanov" 
> >>>>>> To: proton@qpid.apache.org
> >>>>>> Sent: Friday, October 24, 2014 9:38:54 AM
> >>>>>> Subject: Re: VOTE: Release Proton 0.8 RC4 as 0.8 final
> >>>>>>
> >>>>>> Hallo,
> >>>>>>
> >>>>>> I used proton 0.7 and later when I had an error, proton 0.8 RC4 to
> >> build
> >>>>>> qpid-cpp-0.30. In both cases at some time qpi

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Michael Ivanov]

nd the
>>> server and see if that will shed some light on what is going on.
>>>
>>> --Rafael
>>>
>>>
>>> On Fri, Oct 24, 2014 at 2:00 PM, Michael Ivanov 
>> wrote:
>>>
>>>> I just rebuilt all client processes to use proton 0.8 (it was still 0.7
>>>> before)
>>>> Error is still the same.
>>>>
>>>> Best regards,
>>>>
>>>> 24.10.2014 18:16, Ken Giusti пишет:
>>>>> >From the trace, it seems like the broker is receiving a transfer whose
>>>> delivery id is out of order.
>>>>>
>>>>> This shouldn't cause an abort - likely the result is an untested
>> failure
>>>> path, in transport.c:781:
>>>>>
>>>>> if (id_present && id != state->id) {
>>>>>   int err = pn_do_error(transport, "amqp:session:invalid-field",
>>>>> "sequencing error, expected delivery-id %u,
>>>> got %u",
>>>>> state->id, id);
>>>>> > // XXX: this will probably leave delivery buffer state messed up
>>>>>   pn_full_settle(incoming, delivery);
>>>>>   return err;
>>>>> }
>>>>>
>>>>> It doesn't explain why a transfer is sent out of order by the client,
>>>> but at least we probably should remove the attempt to pn_full_settle(),
>> and
>>>> just return the error to fail the connection (assumed - totally
>> untested).
>>>>>
>>>>> -K
>>>>>
>>>>> - Original Message -
>>>>>> From: "Michael Ivanov" 
>>>>>> To: proton@qpid.apache.org
>>>>>> Sent: Friday, October 24, 2014 9:38:54 AM
>>>>>> Subject: Re: VOTE: Release Proton 0.8 RC4 as 0.8 final
>>>>>>
>>>>>> Hallo,
>>>>>>
>>>>>> I used proton 0.7 and later when I had an error, proton 0.8 RC4 to
>> build
>>>>>> qpid-cpp-0.30. In both cases at some time qpidd aborts in proton
>> library
>>>>>> in the following location:
>>>>>>
>>>>>>
>>>>>> #0  0x003999432635 in raise () from /lib64/libc.so.6
>>>>>> #1  0x003999433e15 in abort () from /lib64/libc.so.6
>>>>>> #2  0x00399942b75e in __assert_fail_base () from /lib64/libc.so.6
>>>>>> #3  0x00399942b820 in __assert_fail () from /lib64/libc.so.6
>>>>>> #4  0x7f130a5af37d in pn_full_settle (db=,
>>>>>> delivery=0x7f13001545f0)
>>>>>> at
>>>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:742
>>>>>> #5  0x7f130a5b0cbe in pn_do_transfer (disp=0x1b6dcf0) at
>>>>>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:786
>>>>>> #6  0x7f130a5a94d5 in pni_dispatch_action (disp=0x1b6dcf0,
>>>> frame=...)
>>>>>> at
>>>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:65
>>>>>> #7  pn_dispatch_frame (disp=0x1b6dcf0, frame=...) at
>>>>>>
>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:172
>>>>>> #8  0x7f130a5a9718 in pn_dispatcher_input (disp=0x1b6dcf0,
>>>>>> bytes=0x1b75e10 "", available=0)
>>>>>> at
>>>>>>
>>>>  /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:194
>>>>>> #9  0x7f130a5b2606 in pn_input_read_amqp (io_layer=> optimized
>>>> out>,
>>>>>> bytes=, available=>>>>> optimized out>)
>>>>>> at
>>>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:1145
>>>>>> #10 0x7f130a5ae029 in transport_consume (transport=0x1b6dab0) at
>>>>>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:1064
>>>>>> #11 0x7f130a5ae198 in pn_transport_process (transport=0x1b6dab0,
>>>>>> size=)
>>>>>> at
>>>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:2120
>>>>>> #12 0x7f130a5ae8e0 in pn_transport_input (transport=0x1b6dab0,
>>>>>> bytes=0x1b2a9b6 "eeded\n", available=0)
>>>>>> at
>>>> 

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Rafael Schloming]

You can check out the trunk source code from here:

http://svn.apache.org/repos/asf/qpid/proton/trunk/

You should be able to turn on the protocol trace by setting the
PN_TRACE_FRM environment variable to 1, e.g.:

  export PN_TRACE_FRM=1
  run-client-program

You will need to do this on the server side as well in order to get the
server's version of the protocol trace.

--Rafael


On Fri, Oct 24, 2014 at 2:31 PM, Michael Ivanov  wrote:

> Sorry, should I check out the trunk from the repository or can I download
> the new sources tar archive from somewhere? The last version I used I have
> downloaded from
> http://people.apache.org/~rhs/qpid-proton-0.8rc4/qpid-proton-0.8.tar.gz
> If the sources are to be checked out which url should I use?
>
> And pls can you explain me how to turn the proitocol trace on? Or should I
> just tcpdump during exchange?
>
> Best regards,
>
> 24.10.2014 22:24, Rafael Schloming пишет:
> > Hi Michael,
> >
> > I just committed the change Ken suggested to at least fix the abort. Is
> > there any way you could retest with trunk?
> >
> > If the problem still occurs (I expect it will, just not quite so fatally)
> > it would be good to get the protocol trace for both the client and the
> > server and see if that will shed some light on what is going on.
> >
> > --Rafael
> >
> >
> > On Fri, Oct 24, 2014 at 2:00 PM, Michael Ivanov 
> wrote:
> >
> >> I just rebuilt all client processes to use proton 0.8 (it was still 0.7
> >> before)
> >> Error is still the same.
> >>
> >> Best regards,
> >>
> >> 24.10.2014 18:16, Ken Giusti пишет:
> >>> >From the trace, it seems like the broker is receiving a transfer whose
> >> delivery id is out of order.
> >>>
> >>> This shouldn't cause an abort - likely the result is an untested
> failure
> >> path, in transport.c:781:
> >>>
> >>> if (id_present && id != state->id) {
> >>>   int err = pn_do_error(transport, "amqp:session:invalid-field",
> >>> "sequencing error, expected delivery-id %u,
> >> got %u",
> >>> state->id, id);
> >>> > // XXX: this will probably leave delivery buffer state messed up
> >>>   pn_full_settle(incoming, delivery);
> >>>   return err;
> >>> }
> >>>
> >>> It doesn't explain why a transfer is sent out of order by the client,
> >> but at least we probably should remove the attempt to pn_full_settle(),
> and
> >> just return the error to fail the connection (assumed - totally
> untested).
> >>>
> >>> -K
> >>>
> >>> - Original Message -
> >>>> From: "Michael Ivanov" 
> >>>> To: proton@qpid.apache.org
> >>>> Sent: Friday, October 24, 2014 9:38:54 AM
> >>>> Subject: Re: VOTE: Release Proton 0.8 RC4 as 0.8 final
> >>>>
> >>>> Hallo,
> >>>>
> >>>> I used proton 0.7 and later when I had an error, proton 0.8 RC4 to
> build
> >>>> qpid-cpp-0.30. In both cases at some time qpidd aborts in proton
> library
> >>>> in the following location:
> >>>>
> >>>>
> >>>> #0  0x003999432635 in raise () from /lib64/libc.so.6
> >>>> #1  0x003999433e15 in abort () from /lib64/libc.so.6
> >>>> #2  0x00399942b75e in __assert_fail_base () from /lib64/libc.so.6
> >>>> #3  0x00399942b820 in __assert_fail () from /lib64/libc.so.6
> >>>> #4  0x7f130a5af37d in pn_full_settle (db=,
> >>>> delivery=0x7f13001545f0)
> >>>> at
> >> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:742
> >>>> #5  0x7f130a5b0cbe in pn_do_transfer (disp=0x1b6dcf0) at
> >>>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:786
> >>>> #6  0x7f130a5a94d5 in pni_dispatch_action (disp=0x1b6dcf0,
> >> frame=...)
> >>>> at
> >> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:65
> >>>> #7  pn_dispatch_frame (disp=0x1b6dcf0, frame=...) at
> >>>>
> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:172
> >>>> #8  0x7f130a5a9718 in pn_dispatcher_input (disp=0x1b6dcf0,
> >>>> bytes=0x1b75e10 "", available=0)
> >>>> at
>

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Michael Ivanov]

Sorry, should I check out the trunk from the repository or can I download
the new sources tar archive from somewhere? The last version I used I have
downloaded from 
http://people.apache.org/~rhs/qpid-proton-0.8rc4/qpid-proton-0.8.tar.gz
If the sources are to be checked out which url should I use?

And pls can you explain me how to turn the proitocol trace on? Or should I
just tcpdump during exchange?

Best regards,

24.10.2014 22:24, Rafael Schloming пишет:
> Hi Michael,
> 
> I just committed the change Ken suggested to at least fix the abort. Is
> there any way you could retest with trunk?
> 
> If the problem still occurs (I expect it will, just not quite so fatally)
> it would be good to get the protocol trace for both the client and the
> server and see if that will shed some light on what is going on.
> 
> --Rafael
> 
> 
> On Fri, Oct 24, 2014 at 2:00 PM, Michael Ivanov  wrote:
> 
>> I just rebuilt all client processes to use proton 0.8 (it was still 0.7
>> before)
>> Error is still the same.
>>
>> Best regards,
>>
>> 24.10.2014 18:16, Ken Giusti пишет:
>>> >From the trace, it seems like the broker is receiving a transfer whose
>> delivery id is out of order.
>>>
>>> This shouldn't cause an abort - likely the result is an untested failure
>> path, in transport.c:781:
>>>
>>> if (id_present && id != state->id) {
>>>   int err = pn_do_error(transport, "amqp:session:invalid-field",
>>> "sequencing error, expected delivery-id %u,
>> got %u",
>>> state->id, id);
>>> > // XXX: this will probably leave delivery buffer state messed up
>>>   pn_full_settle(incoming, delivery);
>>>   return err;
>>> }
>>>
>>> It doesn't explain why a transfer is sent out of order by the client,
>> but at least we probably should remove the attempt to pn_full_settle(), and
>> just return the error to fail the connection (assumed - totally untested).
>>>
>>> -K
>>>
>>> - Original Message -
>>>> From: "Michael Ivanov" 
>>>> To: proton@qpid.apache.org
>>>> Sent: Friday, October 24, 2014 9:38:54 AM
>>>> Subject: Re: VOTE: Release Proton 0.8 RC4 as 0.8 final
>>>>
>>>> Hallo,
>>>>
>>>> I used proton 0.7 and later when I had an error, proton 0.8 RC4 to build
>>>> qpid-cpp-0.30. In both cases at some time qpidd aborts in proton library
>>>> in the following location:
>>>>
>>>>
>>>> #0  0x003999432635 in raise () from /lib64/libc.so.6
>>>> #1  0x003999433e15 in abort () from /lib64/libc.so.6
>>>> #2  0x00399942b75e in __assert_fail_base () from /lib64/libc.so.6
>>>> #3  0x00399942b820 in __assert_fail () from /lib64/libc.so.6
>>>> #4  0x7f130a5af37d in pn_full_settle (db=,
>>>> delivery=0x7f13001545f0)
>>>> at
>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:742
>>>> #5  0x7f130a5b0cbe in pn_do_transfer (disp=0x1b6dcf0) at
>>>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:786
>>>> #6  0x7f130a5a94d5 in pni_dispatch_action (disp=0x1b6dcf0,
>> frame=...)
>>>> at
>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:65
>>>> #7  pn_dispatch_frame (disp=0x1b6dcf0, frame=...) at
>>>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:172
>>>> #8  0x7f130a5a9718 in pn_dispatcher_input (disp=0x1b6dcf0,
>>>> bytes=0x1b75e10 "", available=0)
>>>> at
>>>>
>>  /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:194
>>>> #9  0x7f130a5b2606 in pn_input_read_amqp (io_layer=> out>,
>>>> bytes=, available=>>> optimized out>)
>>>> at
>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:1145
>>>> #10 0x7f130a5ae029 in transport_consume (transport=0x1b6dab0) at
>>>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:1064
>>>> #11 0x7f130a5ae198 in pn_transport_process (transport=0x1b6dab0,
>>>> size=)
>>>> at
>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:2120
>>>> #12 0x7f130a5ae8e0 in pn_transport_input (transport=0x1b6dab0,
>>>> bytes=0x1b2a9b6 "eeded\n", available=0)
>>>> at
>&

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Rafael Schloming]

Hi Michael,

I just committed the change Ken suggested to at least fix the abort. Is
there any way you could retest with trunk?

If the problem still occurs (I expect it will, just not quite so fatally)
it would be good to get the protocol trace for both the client and the
server and see if that will shed some light on what is going on.

--Rafael


On Fri, Oct 24, 2014 at 2:00 PM, Michael Ivanov  wrote:

> I just rebuilt all client processes to use proton 0.8 (it was still 0.7
> before)
> Error is still the same.
>
> Best regards,
>
> 24.10.2014 18:16, Ken Giusti пишет:
> >>From the trace, it seems like the broker is receiving a transfer whose
> delivery id is out of order.
> >
> > This shouldn't cause an abort - likely the result is an untested failure
> path, in transport.c:781:
> >
> > if (id_present && id != state->id) {
> >   int err = pn_do_error(transport, "amqp:session:invalid-field",
> > "sequencing error, expected delivery-id %u,
> got %u",
> > state->id, id);
> > > // XXX: this will probably leave delivery buffer state messed up
> >   pn_full_settle(incoming, delivery);
> >   return err;
> > }
> >
> > It doesn't explain why a transfer is sent out of order by the client,
> but at least we probably should remove the attempt to pn_full_settle(), and
> just return the error to fail the connection (assumed - totally untested).
> >
> > -K
> >
> > - Original Message -
> >> From: "Michael Ivanov" 
> >> To: proton@qpid.apache.org
> >> Sent: Friday, October 24, 2014 9:38:54 AM
> >> Subject: Re: VOTE: Release Proton 0.8 RC4 as 0.8 final
> >>
> >> Hallo,
> >>
> >> I used proton 0.7 and later when I had an error, proton 0.8 RC4 to build
> >> qpid-cpp-0.30. In both cases at some time qpidd aborts in proton library
> >> in the following location:
> >>
> >>
> >> #0  0x003999432635 in raise () from /lib64/libc.so.6
> >> #1  0x003999433e15 in abort () from /lib64/libc.so.6
> >> #2  0x00399942b75e in __assert_fail_base () from /lib64/libc.so.6
> >> #3  0x00399942b820 in __assert_fail () from /lib64/libc.so.6
> >> #4  0x7f130a5af37d in pn_full_settle (db=,
> >> delivery=0x7f13001545f0)
> >> at
> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:742
> >> #5  0x7f130a5b0cbe in pn_do_transfer (disp=0x1b6dcf0) at
> >> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:786
> >> #6  0x7f130a5a94d5 in pni_dispatch_action (disp=0x1b6dcf0,
> frame=...)
> >> at
> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:65
> >> #7  pn_dispatch_frame (disp=0x1b6dcf0, frame=...) at
> >> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:172
> >> #8  0x7f130a5a9718 in pn_dispatcher_input (disp=0x1b6dcf0,
> >> bytes=0x1b75e10 "", available=0)
> >> at
> >>
>  /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:194
> >> #9  0x7f130a5b2606 in pn_input_read_amqp (io_layer= out>,
> >> bytes=, available= >> optimized out>)
> >> at
> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:1145
> >> #10 0x7f130a5ae029 in transport_consume (transport=0x1b6dab0) at
> >> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:1064
> >> #11 0x7f130a5ae198 in pn_transport_process (transport=0x1b6dab0,
> >> size=)
> >> at
> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:2120
> >> #12 0x7f130a5ae8e0 in pn_transport_input (transport=0x1b6dab0,
> >> bytes=0x1b2a9b6 "eeded\n", available=0)
> >> at
> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:1039
> >> #13 0x7f130a81c192 in qpid::broker::amqp::Connection::decode
> >> (this=0x1b6c4c8, buffer=0x1b2a880 "", size=310)
> >> at
> /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/broker/amqp/Connection.cpp:119
> >> #14 0x7f130a858c99 in qpid::broker::amqp::Sasl::decode
> (this=0x1b6c470,
> >> buffer=, size=310)
> >> at /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/broker/amqp/Sasl.cpp:49
> >> #15 0x7f130b0e9100 in qpid::sys::AsynchIOHandler::readbuff
> >> (this=0x1b29a90, buff=0x1b6a890)
> >> at /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/sys/AsynchIOHandler.cpp:135
> >> #16 0x7f130b0689e7 in operato

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Michael Ivanov]

I just rebuilt all client processes to use proton 0.8 (it was still 0.7 before)
Error is still the same.

Best regards,

24.10.2014 18:16, Ken Giusti пишет:
>>From the trace, it seems like the broker is receiving a transfer whose 
>>delivery id is out of order.
> 
> This shouldn't cause an abort - likely the result is an untested failure 
> path, in transport.c:781:
> 
> if (id_present && id != state->id) {
>   int err = pn_do_error(transport, "amqp:session:invalid-field",
> "sequencing error, expected delivery-id %u, got 
> %u",
> state->id, id);
> > // XXX: this will probably leave delivery buffer state messed up
>   pn_full_settle(incoming, delivery);
>   return err;
> }
> 
> It doesn't explain why a transfer is sent out of order by the client, but at 
> least we probably should remove the attempt to pn_full_settle(), and just 
> return the error to fail the connection (assumed - totally untested).
> 
> -K
> 
> - Original Message -
>> From: "Michael Ivanov" 
>> To: proton@qpid.apache.org
>> Sent: Friday, October 24, 2014 9:38:54 AM
>> Subject: Re: VOTE: Release Proton 0.8 RC4 as 0.8 final
>>
>> Hallo,
>>
>> I used proton 0.7 and later when I had an error, proton 0.8 RC4 to build
>> qpid-cpp-0.30. In both cases at some time qpidd aborts in proton library
>> in the following location:
>>
>>
>> #0  0x003999432635 in raise () from /lib64/libc.so.6
>> #1  0x003999433e15 in abort () from /lib64/libc.so.6
>> #2  0x00399942b75e in __assert_fail_base () from /lib64/libc.so.6
>> #3  0x00399942b820 in __assert_fail () from /lib64/libc.so.6
>> #4  0x7f130a5af37d in pn_full_settle (db=,
>> delivery=0x7f13001545f0)
>> at /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:742
>> #5  0x7f130a5b0cbe in pn_do_transfer (disp=0x1b6dcf0) at
>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:786
>> #6  0x7f130a5a94d5 in pni_dispatch_action (disp=0x1b6dcf0, frame=...)
>> at /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:65
>> #7  pn_dispatch_frame (disp=0x1b6dcf0, frame=...) at
>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:172
>> #8  0x7f130a5a9718 in pn_dispatcher_input (disp=0x1b6dcf0,
>> bytes=0x1b75e10 "", available=0)
>> at
>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:194
>> #9  0x7f130a5b2606 in pn_input_read_amqp (io_layer=,
>> bytes=, available=> optimized out>)
>> at /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:1145
>> #10 0x7f130a5ae029 in transport_consume (transport=0x1b6dab0) at
>> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:1064
>> #11 0x7f130a5ae198 in pn_transport_process (transport=0x1b6dab0,
>> size=)
>> at /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:2120
>> #12 0x7f130a5ae8e0 in pn_transport_input (transport=0x1b6dab0,
>> bytes=0x1b2a9b6 "eeded\n", available=0)
>> at /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:1039
>> #13 0x7f130a81c192 in qpid::broker::amqp::Connection::decode
>> (this=0x1b6c4c8, buffer=0x1b2a880 "", size=310)
>> at /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/broker/amqp/Connection.cpp:119
>> #14 0x7f130a858c99 in qpid::broker::amqp::Sasl::decode (this=0x1b6c470,
>> buffer=, size=310)
>> at /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/broker/amqp/Sasl.cpp:49
>> #15 0x7f130b0e9100 in qpid::sys::AsynchIOHandler::readbuff
>> (this=0x1b29a90, buff=0x1b6a890)
>> at /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/sys/AsynchIOHandler.cpp:135
>> #16 0x7f130b0689e7 in operator() (this=0x1b29ad0, h=...) at
>> /usr/include/boost/function/function_template.hpp:1013
>> #17 qpid::sys::posix::AsynchIO::readable (this=0x1b29ad0, h=...) at
>> /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/sys/posix/AsynchIO.cpp:452
>> #18 0x7f130b0ed853 in boost::function1> qpid::sys::DispatchHandle&>::operator() (this=,
>> a0=) at
>> /usr/include/boost/function/function_template.hpp:1013
>> #19 0x7f130b0ec991 in qpid::sys::DispatchHandle::processEvent
>> (this=0x1b29ad8, type=qpid::sys::Poller::READABLE)
>> at /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/sys/DispatchHandle.cpp:280
>> #20 0x7f130b08d4f2 in process (this=0x176cc90) at
>> /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/sys/Poller.h:131
>> #21 qpid::sys::Poller::run 

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Ken Giusti]

>From the trace, it seems like the broker is receiving a transfer whose 
>delivery id is out of order.

This shouldn't cause an abort - likely the result is an untested failure path, 
in transport.c:781:

if (id_present && id != state->id) {
  int err = pn_do_error(transport, "amqp:session:invalid-field",
"sequencing error, expected delivery-id %u, got %u",
state->id, id);
> // XXX: this will probably leave delivery buffer state messed up
  pn_full_settle(incoming, delivery);
  return err;
}

It doesn't explain why a transfer is sent out of order by the client, but at 
least we probably should remove the attempt to pn_full_settle(), and just 
return the error to fail the connection (assumed - totally untested).

-K

- Original Message -
> From: "Michael Ivanov" 
> To: proton@qpid.apache.org
> Sent: Friday, October 24, 2014 9:38:54 AM
> Subject: Re: VOTE: Release Proton 0.8 RC4 as 0.8 final
> 
> Hallo,
> 
> I used proton 0.7 and later when I had an error, proton 0.8 RC4 to build
> qpid-cpp-0.30. In both cases at some time qpidd aborts in proton library
> in the following location:
> 
> 
> #0  0x003999432635 in raise () from /lib64/libc.so.6
> #1  0x003999433e15 in abort () from /lib64/libc.so.6
> #2  0x00399942b75e in __assert_fail_base () from /lib64/libc.so.6
> #3  0x00399942b820 in __assert_fail () from /lib64/libc.so.6
> #4  0x7f130a5af37d in pn_full_settle (db=,
> delivery=0x7f13001545f0)
> at /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:742
> #5  0x7f130a5b0cbe in pn_do_transfer (disp=0x1b6dcf0) at
> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:786
> #6  0x7f130a5a94d5 in pni_dispatch_action (disp=0x1b6dcf0, frame=...)
> at /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:65
> #7  pn_dispatch_frame (disp=0x1b6dcf0, frame=...) at
> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:172
> #8  0x7f130a5a9718 in pn_dispatcher_input (disp=0x1b6dcf0,
> bytes=0x1b75e10 "", available=0)
> at
> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:194
> #9  0x7f130a5b2606 in pn_input_read_amqp (io_layer=,
> bytes=, available= optimized out>)
> at /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:1145
> #10 0x7f130a5ae029 in transport_consume (transport=0x1b6dab0) at
> /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:1064
> #11 0x7f130a5ae198 in pn_transport_process (transport=0x1b6dab0,
> size=)
> at /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:2120
> #12 0x7f130a5ae8e0 in pn_transport_input (transport=0x1b6dab0,
> bytes=0x1b2a9b6 "eeded\n", available=0)
> at /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:1039
> #13 0x7f130a81c192 in qpid::broker::amqp::Connection::decode
> (this=0x1b6c4c8, buffer=0x1b2a880 "", size=310)
> at /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/broker/amqp/Connection.cpp:119
> #14 0x7f130a858c99 in qpid::broker::amqp::Sasl::decode (this=0x1b6c470,
> buffer=, size=310)
> at /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/broker/amqp/Sasl.cpp:49
> #15 0x7f130b0e9100 in qpid::sys::AsynchIOHandler::readbuff
> (this=0x1b29a90, buff=0x1b6a890)
> at /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/sys/AsynchIOHandler.cpp:135
> #16 0x7f130b0689e7 in operator() (this=0x1b29ad0, h=...) at
> /usr/include/boost/function/function_template.hpp:1013
> #17 qpid::sys::posix::AsynchIO::readable (this=0x1b29ad0, h=...) at
> /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/sys/posix/AsynchIO.cpp:452
> #18 0x7f130b0ed853 in boost::function1 qpid::sys::DispatchHandle&>::operator() (this=,
> a0=) at
> /usr/include/boost/function/function_template.hpp:1013
> #19 0x7f130b0ec991 in qpid::sys::DispatchHandle::processEvent
> (this=0x1b29ad8, type=qpid::sys::Poller::READABLE)
> at /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/sys/DispatchHandle.cpp:280
> #20 0x7f130b08d4f2 in process (this=0x176cc90) at
> /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/sys/Poller.h:131
> #21 qpid::sys::Poller::run (this=0x176cc90) at
> /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/sys/epoll/EpollPoller.cpp:522
> #22 0x7f130b08240a in qpid::sys::(anonymous namespace)::runRunnable
> (p=)
> at /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/sys/posix/Thread.cpp:35
> #23 0x003999c079d1 in start_thread () from /lib64/libpthread.so.0
> #24 0x0039994e886d in clone () from /lib64/libc.so.6
> 
> I have core file and probably I can try to recreate the situation.
> 
> Best regards,
> 
> 24.10.2014 17:

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Michael Ivanov]

Hallo,

I used proton 0.7 and later when I had an error, proton 0.8 RC4 to build
qpid-cpp-0.30. In both cases at some time qpidd aborts in proton library
in the following location:


#0  0x003999432635 in raise () from /lib64/libc.so.6
#1  0x003999433e15 in abort () from /lib64/libc.so.6
#2  0x00399942b75e in __assert_fail_base () from /lib64/libc.so.6
#3  0x00399942b820 in __assert_fail () from /lib64/libc.so.6
#4  0x7f130a5af37d in pn_full_settle (db=, 
delivery=0x7f13001545f0)
at /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:742
#5  0x7f130a5b0cbe in pn_do_transfer (disp=0x1b6dcf0) at 
/home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:786
#6  0x7f130a5a94d5 in pni_dispatch_action (disp=0x1b6dcf0, frame=...)
at /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:65
#7  pn_dispatch_frame (disp=0x1b6dcf0, frame=...) at 
/home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:172
#8  0x7f130a5a9718 in pn_dispatcher_input (disp=0x1b6dcf0, bytes=0x1b75e10 
"", available=0)
at /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/dispatcher/dispatcher.c:194
#9  0x7f130a5b2606 in pn_input_read_amqp (io_layer=, 
bytes=, available=)
at /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:1145
#10 0x7f130a5ae029 in transport_consume (transport=0x1b6dab0) at
/home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:1064
#11 0x7f130a5ae198 in pn_transport_process (transport=0x1b6dab0, 
size=)
at /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:2120
#12 0x7f130a5ae8e0 in pn_transport_input (transport=0x1b6dab0, 
bytes=0x1b2a9b6 "eeded\n", available=0)
at /home/ksmgr/mq/qpid-proton-0.8/proton-c/src/transport/transport.c:1039
#13 0x7f130a81c192 in qpid::broker::amqp::Connection::decode 
(this=0x1b6c4c8, buffer=0x1b2a880 "", size=310)
at /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/broker/amqp/Connection.cpp:119
#14 0x7f130a858c99 in qpid::broker::amqp::Sasl::decode (this=0x1b6c470, 
buffer=, size=310)
at /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/broker/amqp/Sasl.cpp:49
#15 0x7f130b0e9100 in qpid::sys::AsynchIOHandler::readbuff (this=0x1b29a90, 
buff=0x1b6a890)
at /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/sys/AsynchIOHandler.cpp:135
#16 0x7f130b0689e7 in operator() (this=0x1b29ad0, h=...) at 
/usr/include/boost/function/function_template.hpp:1013
#17 qpid::sys::posix::AsynchIO::readable (this=0x1b29ad0, h=...) at 
/home/ksmgr/mq/qpid-cpp-0.30/src/qpid/sys/posix/AsynchIO.cpp:452
#18 0x7f130b0ed853 in boost::function1::operator() (this=,
a0=) at 
/usr/include/boost/function/function_template.hpp:1013
#19 0x7f130b0ec991 in qpid::sys::DispatchHandle::processEvent 
(this=0x1b29ad8, type=qpid::sys::Poller::READABLE)
at /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/sys/DispatchHandle.cpp:280
#20 0x7f130b08d4f2 in process (this=0x176cc90) at 
/home/ksmgr/mq/qpid-cpp-0.30/src/qpid/sys/Poller.h:131
#21 qpid::sys::Poller::run (this=0x176cc90) at 
/home/ksmgr/mq/qpid-cpp-0.30/src/qpid/sys/epoll/EpollPoller.cpp:522
#22 0x7f130b08240a in qpid::sys::(anonymous namespace)::runRunnable 
(p=)
at /home/ksmgr/mq/qpid-cpp-0.30/src/qpid/sys/posix/Thread.cpp:35
#23 0x003999c079d1 in start_thread () from /lib64/libpthread.so.0
#24 0x0039994e886d in clone () from /lib64/libc.so.6

I have core file and probably I can try to recreate the situation.

Best regards,

24.10.2014 17:05, Timothy Bish пишет:
>  [ X ] Yes, release Proton 0.8 RC4 as 0.8 final.
> 
> Tested Proton-J with ActiveMQ and the new JMS client and found no issues,
> 
> On 10/23/2014 12:21 PM, Rafael Schloming wrote:
>> Hi Everyone,
>>
>> I've put together RC4. This is pretty much the same as RC3 with a number of
>> fixes to disable those SSL versions that are vulnerable to attack.
>>
>> The sources are available here:
>>
>>- http://people.apache.org/~rhs/qpid-proton-0.8rc4/
>>
>> Java binaries are here:
>>
>>- https://repository.apache.org/content/repositories/orgapacheqpid-1020/
>>
>> Changes since RC3:
>>
>>- PROTON-724: make sure to pop any pending output in
>> pn_transport_close_head()
>>- PROTON-720: [Windows IO] fix format specifier to print string
>>- added dispatch utility
>>- fixed error message
>>- fixed Collector.put
>>- PROTON-719 : prevent ssl3 connections in Windows with schannel
>>- PROTON-717: disable SSLv3
>>- PROTON-717: mitigate the CRIME SSL vulnerability
>>- PROTON-716: reject connections using SSLv3 - it is insecure
>>
>> Please check the sources out and register your vote:
>>
>>[   ] Yes, release Proton 0.8 RC4 as 0.8 final.
>>[   ] No, because...
>>
>> --Rafael
>>
> 
> 


-- 
 \   / |   |
 (OvO) |  Mikhail Iwanow   |
 (^^^) |  Voice:   +7 (911) 223-1300   |
  \^/  |  E-mail:  iv...@logit-ag.de   |
  ^ ^  |   |

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Chuck Rolke]

  [ X  ] Yes, release Proton 0.8 RC4 as 0.8 final.

Compiled on Windows Server 2012, Visual Studios 2008, 2010, 2012, 2013.
Ran some tests on a few kits with no issues.

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Timothy Bish]

 [ X ] Yes, release Proton 0.8 RC4 as 0.8 final.

Tested Proton-J with ActiveMQ and the new JMS client and found no issues,

On 10/23/2014 12:21 PM, Rafael Schloming wrote:

Hi Everyone,

I've put together RC4. This is pretty much the same as RC3 with a number of
fixes to disable those SSL versions that are vulnerable to attack.

The sources are available here:

   - http://people.apache.org/~rhs/qpid-proton-0.8rc4/

Java binaries are here:

   - https://repository.apache.org/content/repositories/orgapacheqpid-1020/

Changes since RC3:

   - PROTON-724: make sure to pop any pending output in
pn_transport_close_head()
   - PROTON-720: [Windows IO] fix format specifier to print string
   - added dispatch utility
   - fixed error message
   - fixed Collector.put
   - PROTON-719 : prevent ssl3 connections in Windows with schannel
   - PROTON-717: disable SSLv3
   - PROTON-717: mitigate the CRIME SSL vulnerability
   - PROTON-716: reject connections using SSLv3 - it is insecure

Please check the sources out and register your vote:

   [   ] Yes, release Proton 0.8 RC4 as 0.8 final.
   [   ] No, because...

--Rafael




--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Robbie Gemmell]

 [ X ] Yes, release Proton 0.8 RC4 as 0.8 final.

I ran the C and Java build+tests, tried out the Java binaries with the JMS
client build+tests, all seemed fine.

Robbie

On 23 October 2014 17:21, Rafael Schloming  wrote:

> Hi Everyone,
>
> I've put together RC4. This is pretty much the same as RC3 with a number of
> fixes to disable those SSL versions that are vulnerable to attack.
>
> The sources are available here:
>
>   - http://people.apache.org/~rhs/qpid-proton-0.8rc4/
>
> Java binaries are here:
>
>   - https://repository.apache.org/content/repositories/orgapacheqpid-1020/
>
> Changes since RC3:
>
>   - PROTON-724: make sure to pop any pending output in
> pn_transport_close_head()
>   - PROTON-720: [Windows IO] fix format specifier to print string
>   - added dispatch utility
>   - fixed error message
>   - fixed Collector.put
>   - PROTON-719 : prevent ssl3 connections in Windows with schannel
>   - PROTON-717: disable SSLv3
>   - PROTON-717: mitigate the CRIME SSL vulnerability
>   - PROTON-716: reject connections using SSLv3 - it is insecure
>
> Please check the sources out and register your vote:
>
>   [   ] Yes, release Proton 0.8 RC4 as 0.8 final.
>   [   ] No, because...
>
> --Rafael
>

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Clebert Suconic]

+1 (non binding I guess)


> On Oct 23, 2014, at 12:21 PM, Rafael Schloming  wrote:
> 
> Hi Everyone,
> 
> I've put together RC4. This is pretty much the same as RC3 with a number of
> fixes to disable those SSL versions that are vulnerable to attack.
> 
> The sources are available here:
> 
>  - http://people.apache.org/~rhs/qpid-proton-0.8rc4/
> 
> Java binaries are here:
> 
>  - https://repository.apache.org/content/repositories/orgapacheqpid-1020/
> 
> Changes since RC3:
> 
>  - PROTON-724: make sure to pop any pending output in
> pn_transport_close_head()
>  - PROTON-720: [Windows IO] fix format specifier to print string
>  - added dispatch utility
>  - fixed error message
>  - fixed Collector.put
>  - PROTON-719 : prevent ssl3 connections in Windows with schannel
>  - PROTON-717: disable SSLv3
>  - PROTON-717: mitigate the CRIME SSL vulnerability
>  - PROTON-716: reject connections using SSLv3 - it is insecure
> 
> Please check the sources out and register your vote:
> 
>  [   ] Yes, release Proton 0.8 RC4 as 0.8 final.
>  [   ] No, because...
> 
> --Rafael

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Alan Conway]

  [ X ] Yes, release Proton 0.8 RC4 as 0.8 final.

Passes dispatch tests

On Thu, 2014-10-23 at 12:21 -0400, Rafael Schloming wrote:
> Hi Everyone,
> 
> I've put together RC4. This is pretty much the same as RC3 with a number of
> fixes to disable those SSL versions that are vulnerable to attack.
> 
> The sources are available here:
> 
>   - http://people.apache.org/~rhs/qpid-proton-0.8rc4/
> 
> Java binaries are here:
> 
>   - https://repository.apache.org/content/repositories/orgapacheqpid-1020/
> 
> Changes since RC3:
> 
>   - PROTON-724: make sure to pop any pending output in
> pn_transport_close_head()
>   - PROTON-720: [Windows IO] fix format specifier to print string
>   - added dispatch utility
>   - fixed error message
>   - fixed Collector.put
>   - PROTON-719 : prevent ssl3 connections in Windows with schannel
>   - PROTON-717: disable SSLv3
>   - PROTON-717: mitigate the CRIME SSL vulnerability
>   - PROTON-716: reject connections using SSLv3 - it is insecure
> 
> Please check the sources out and register your vote:
> 
>   [   ] Yes, release Proton 0.8 RC4 as 0.8 final.
>   [   ] No, because...
> 
> --Rafael

Re: VOTE: Release Proton 0.8 RC4 as 0.8 final

[Ken Giusti]

   [X] Yes, release Proton 0.8 RC4 as 0.8 final.

make test on Fedora19 and Centos6
make install on Centos6
verified against pyngus (trunk) and oslo.messaging (trunk)
verified sslv3 is rejected


- Original Message -
> From: "Rafael Schloming" 
> To: proton@qpid.apache.org
> Sent: Thursday, October 23, 2014 12:21:32 PM
> Subject: VOTE: Release Proton 0.8 RC4 as 0.8 final
> 
> Hi Everyone,
> 
> I've put together RC4. This is pretty much the same as RC3 with a number of
> fixes to disable those SSL versions that are vulnerable to attack.
> 
> The sources are available here:
> 
>   - http://people.apache.org/~rhs/qpid-proton-0.8rc4/
> 
> Java binaries are here:
> 
>   - https://repository.apache.org/content/repositories/orgapacheqpid-1020/
> 
> Changes since RC3:
> 
>   - PROTON-724: make sure to pop any pending output in
> pn_transport_close_head()
>   - PROTON-720: [Windows IO] fix format specifier to print string
>   - added dispatch utility
>   - fixed error message
>   - fixed Collector.put
>   - PROTON-719 : prevent ssl3 connections in Windows with schannel
>   - PROTON-717: disable SSLv3
>   - PROTON-717: mitigate the CRIME SSL vulnerability
>   - PROTON-716: reject connections using SSLv3 - it is insecure
> 
> Please check the sources out and register your vote:
> 
>   [   ] Yes, release Proton 0.8 RC4 as 0.8 final.
>   [   ] No, because...
> 
> --Rafael
> 

-- 
-K

VOTE: Release Proton 0.8 RC4 as 0.8 final

[Rafael Schloming]

Hi Everyone,

I've put together RC4. This is pretty much the same as RC3 with a number of
fixes to disable those SSL versions that are vulnerable to attack.

The sources are available here:

  - http://people.apache.org/~rhs/qpid-proton-0.8rc4/

Java binaries are here:

  - https://repository.apache.org/content/repositories/orgapacheqpid-1020/

Changes since RC3:

  - PROTON-724: make sure to pop any pending output in
pn_transport_close_head()
  - PROTON-720: [Windows IO] fix format specifier to print string
  - added dispatch utility
  - fixed error message
  - fixed Collector.put
  - PROTON-719 : prevent ssl3 connections in Windows with schannel
  - PROTON-717: disable SSLv3
  - PROTON-717: mitigate the CRIME SSL vulnerability
  - PROTON-716: reject connections using SSLv3 - it is insecure

Please check the sources out and register your vote:

  [   ] Yes, release Proton 0.8 RC4 as 0.8 final.
  [   ] No, because...

--Rafael

Re: [RESULT] [VOTE]: Release Proton 0.7 RC4 as 0.7 final

[Rafael Schloming]

Oops, bumped the send key a little early there.

The vote passes with 5 (4 binding) +1 votes and zero -1 votes. I will
follow up when the release is posted.

--Rafael


On Fri, Apr 25, 2014 at 11:04 AM, Rafael Schloming  wrote:

>
>
>
> On Tue, Apr 22, 2014 at 7:12 AM, Rafael Schloming wrote:
>
>> Hi Everyone,
>>
>> I haven't heard of any issues in RC4, so I'm going to put this to a
>> formal vote now:
>>
>> Source artifacts are here:
>>
>>   - http://people.apache.org/~rhs/qpid-proton-0.7rc4/
>>
>> Java binaries are here:
>>
>>  - https://repository.apache.org/content/repositories/orgapacheqpid-1004/
>>
>> Please review and register your vote:
>>
>>   [ ] Yes, release 0.7 RC4 as 0.7 final
>>   [ ] No, 0.7 RC4 as the following issues...
>>
>>
>> Thanks,
>>
>> --Rafael
>>
>>
>

[RESULT] [VOTE]: Release Proton 0.7 RC4 as 0.7 final

[Rafael Schloming]

On Tue, Apr 22, 2014 at 7:12 AM, Rafael Schloming  wrote:

> Hi Everyone,
>
> I haven't heard of any issues in RC4, so I'm going to put this to a formal
> vote now:
>
> Source artifacts are here:
>
>   - http://people.apache.org/~rhs/qpid-proton-0.7rc4/
>
> Java binaries are here:
>
>  - https://repository.apache.org/content/repositories/orgapacheqpid-1004/
>
> Please review and register your vote:
>
>   [ ] Yes, release 0.7 RC4 as 0.7 final
>   [ ] No, 0.7 RC4 as the following issues...
>
>
> Thanks,
>
> --Rafael
>
>

Re: [VOTE]: Release Proton 0.7 RC4 as 0.7 final

[Bozo Dragojevic]

fwiw,

  [X] Yes, release 0.7 RC4 as 0.7 final
  [ ] No, 0.7 RC4 as the following issues...

Bozzo

On 22. 04. 14 13:12, Rafael Schloming wrote:

Hi Everyone,

I haven't heard of any issues in RC4, so I'm going to put this to a formal
vote now:

Source artifacts are here:

   - http://people.apache.org/~rhs/qpid-proton-0.7rc4/

Java binaries are here:

  - https://repository.apache.org/content/repositories/orgapacheqpid-1004/

Please review and register your vote:

   [ ] Yes, release 0.7 RC4 as 0.7 final
   [ ] No, 0.7 RC4 as the following issues...


Thanks,

--Rafael

Re: [VOTE]: Release Proton 0.7 RC4 as 0.7 final

[Ken Giusti]

  [X] Yes, release 0.7 RC4 as 0.7 final
  [ ] No, 0.7 RC4 as the following issues...

- Original Message -
> From: "Robbie Gemmell" 
> To: proton@qpid.apache.org
> Sent: Tuesday, April 22, 2014 11:04:04 AM
> Subject: Re: [VOTE]: Release Proton 0.7 RC4 as 0.7 final
> 
> +1
> 
> Robbie
> On 22 Apr 2014 12:13, "Rafael Schloming"  wrote:
> 
> > Hi Everyone,
> >
> > I haven't heard of any issues in RC4, so I'm going to put this to a formal
> > vote now:
> >
> > Source artifacts are here:
> >
> >   - http://people.apache.org/~rhs/qpid-proton-0.7rc4/
> >
> > Java binaries are here:
> >
> >  - https://repository.apache.org/content/repositories/orgapacheqpid-1004/
> >
> > Please review and register your vote:
> >
> >   [ ] Yes, release 0.7 RC4 as 0.7 final
> >   [ ] No, 0.7 RC4 as the following issues...
> >
> >
> > Thanks,
> >
> > --Rafael
> >
> 

-- 
-K

Re: [VOTE]: Release Proton 0.7 RC4 as 0.7 final

[Robbie Gemmell]

+1

Robbie
On 22 Apr 2014 12:13, "Rafael Schloming"  wrote:

> Hi Everyone,
>
> I haven't heard of any issues in RC4, so I'm going to put this to a formal
> vote now:
>
> Source artifacts are here:
>
>   - http://people.apache.org/~rhs/qpid-proton-0.7rc4/
>
> Java binaries are here:
>
>  - https://repository.apache.org/content/repositories/orgapacheqpid-1004/
>
> Please review and register your vote:
>
>   [ ] Yes, release 0.7 RC4 as 0.7 final
>   [ ] No, 0.7 RC4 as the following issues...
>
>
> Thanks,
>
> --Rafael
>

Re: [VOTE]: Release Proton 0.7 RC4 as 0.7 final

[Ted Ross]

+1

On 04/22/2014 07:12 AM, Rafael Schloming wrote:
> Hi Everyone,
> 
> I haven't heard of any issues in RC4, so I'm going to put this to a formal
> vote now:
> 
> Source artifacts are here:
> 
>   - http://people.apache.org/~rhs/qpid-proton-0.7rc4/
> 
> Java binaries are here:
> 
>  - https://repository.apache.org/content/repositories/orgapacheqpid-1004/
> 
> Please review and register your vote:
> 
>   [ ] Yes, release 0.7 RC4 as 0.7 final
>   [ ] No, 0.7 RC4 as the following issues...
> 
> 
> Thanks,
> 
> --Rafael
> 

Re: [VOTE]: Release Proton 0.7 RC4 as 0.7 final

[Fraser Adams]

   [X] Yes, release 0.7 RC4 as 0.7 final
   [ ] No, 0.7 RC4 as the following issues...


Regards,
Frase

[VOTE]: Release Proton 0.7 RC4 as 0.7 final

[Rafael Schloming]

Hi Everyone,

I haven't heard of any issues in RC4, so I'm going to put this to a formal
vote now:

Source artifacts are here:

  - http://people.apache.org/~rhs/qpid-proton-0.7rc4/

Java binaries are here:

 - https://repository.apache.org/content/repositories/orgapacheqpid-1004/

Please review and register your vote:

  [ ] Yes, release 0.7 RC4 as 0.7 final
  [ ] No, 0.7 RC4 as the following issues...


Thanks,

--Rafael

Proton 0.7 RC4

[Rafael Schloming]

Hi Everyone,

I've posted 0.7 RC4 in the usual places. Source artifacts are here:

  - http://people.apache.org/~rhs/qpid-proton-0.7rc4/

Java binaries are here:

 - https://repository.apache.org/content/repositories/orgapacheqpid-1004/

Changes from RC3 are:

 - PROTON-550 (missing dependency checks)
 - PROTON-554 (compatibility bug with older swig versions)
 - PROTON-560.(SSL bug triggered by large messages)

I'm hoping this will be the last one, so please check it out and if I don't
hear anything bad I will call for a vote soon.

--Rafael

Re: [VOTE] 0.2 RC4

[Hiram Chirino]

Yay!  Congrats.


On Tue, Nov 6, 2012 at 4:06 AM, Rafael Schloming  wrote:

> FYI 0.2 is now live:
>
>   http://qpid.apache.org/proton/download.html
>
> --Rafael
>



-- 

**

*Hiram Chirino*

*Engineering | Red Hat, Inc.*

*hchir...@redhat.com  | fusesource.com | redhat.com*

*skype: hiramchirino | twitter: @hiramchirino
*

*blog: Hiram Chirino's Bit Mojo *

Re: [VOTE] 0.2 RC4

[Rafael Schloming]

FYI 0.2 is now live:

  http://qpid.apache.org/proton/download.html

--Rafael

Re: [VOTE] 0.2 RC4

[Darryl L. Pierce]

On Mon, Nov 05, 2012 at 10:37:34PM +0100, Rafael Schloming wrote:
> On Mon, Nov 5, 2012 at 6:08 PM, Robbie Gemmell 
> wrote:
> 
> > Surely its going to be in /dist/qpid/proton since its a sub project?
> >
> 
> Oops, I misread the post. It will be exactly where 0.1 is except it will
> say 0.2 instead:
> 
>   http://www.apache.org/dist/qpid/proton/0.1/qpid-proton-c-0.1.tar.gz

Cool. I'll update the specfile appropriately.

-- 
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/



pgpiKVIHZpCb5.pgp
Description: PGP signature

Re: [VOTE] 0.2 RC4

[Rafael Schloming]

On Mon, Nov 5, 2012 at 6:08 PM, Robbie Gemmell wrote:

> Surely its going to be in /dist/qpid/proton since its a sub project?
>

Oops, I misread the post. It will be exactly where 0.1 is except it will
say 0.2 instead:

  http://www.apache.org/dist/qpid/proton/0.1/qpid-proton-c-0.1.tar.gz

--Rafael


>
> Robbie
>
> On 5 November 2012 16:11, Rafael Schloming  wrote:
>
> > On Mon, Nov 5, 2012 at 3:54 PM, Darryl L. Pierce 
> > wrote
> > >
> > > Will the final, official URL for the source be:
> > >
> > > http://www.apache.org/dist/proton/$VER/qpid-proton-c-$VER.tar.gz
> > >
> > > ? I'd like to clean up another rpmlint error where it doesn't like a
> > > non-URI value for the source.
> >
> >
> > Yes, with the caveat that I believe we (qpid) are encouraged to switch
> over
> > to using svnpubsub for publishing releases at some point. I don't know
> > if/how this will impact the convention for future releases beyond that
> > point.
> >
> > --Rafael
> >
>

Re: [VOTE] 0.2 RC4

[Robbie Gemmell]

Surely its going to be in /dist/qpid/proton since its a sub project?

Robbie

On 5 November 2012 16:11, Rafael Schloming  wrote:

> On Mon, Nov 5, 2012 at 3:54 PM, Darryl L. Pierce 
> wrote
> >
> > Will the final, official URL for the source be:
> >
> > http://www.apache.org/dist/proton/$VER/qpid-proton-c-$VER.tar.gz
> >
> > ? I'd like to clean up another rpmlint error where it doesn't like a
> > non-URI value for the source.
>
>
> Yes, with the caveat that I believe we (qpid) are encouraged to switch over
> to using svnpubsub for publishing releases at some point. I don't know
> if/how this will impact the convention for future releases beyond that
> point.
>
> --Rafael
>

Re: [VOTE] 0.2 RC4

[Rafael Schloming]

On Mon, Nov 5, 2012 at 3:54 PM, Darryl L. Pierce  wrote
>
> Will the final, official URL for the source be:
>
> http://www.apache.org/dist/proton/$VER/qpid-proton-c-$VER.tar.gz
>
> ? I'd like to clean up another rpmlint error where it doesn't like a
> non-URI value for the source.


Yes, with the caveat that I believe we (qpid) are encouraged to switch over
to using svnpubsub for publishing releases at some point. I don't know
if/how this will impact the convention for future releases beyond that
point.

--Rafael

Re: [VOTE] 0.2 RC4

[Rajith Attapattu]

[x] Ship it. Reviewed the C code change with Rafi.

Rajith

On Mon, Nov 5, 2012 at 7:29 AM, Rob Godfrey  wrote:
> [X] Ship it! (Release RC4 as 0.2)
>
> Tested java and reviewed C change.
>
> -- Rob
>
> On 5 November 2012 13:19, Rafael Schloming  wrote:
>
>> Posted here: http://people.apache.org/~rhs/qpid-proton-0.2rc4/
>>
>> [ ] Ship it! (Release RC4 as 0.2)
>> [ ] No (We need another RC because...)
>>
>> The only difference between RC3 and RC4 for proton-c is a one line change
>> in engine.c that ensures that pn_transport_output will not fail to produce
>> output under particular conditions despite there being output to produce.
>> There was also a public accessor added in proton-j. Both of these are very
>> small and sufficiently isolated changes that they shouldn't impact any
>> testing that has been done on RC3. I've attached the total diff in case
>> anyone wants to check it out. I'm hoping we can still get enough votes to
>> do a release tonight so please have a look and give it your +1 if it checks
>> out.
>>
>> --Rafael
>>

Re: [VOTE] 0.2 RC4

[Darryl L. Pierce]

On Mon, Nov 05, 2012 at 07:19:30AM -0500, Rafael Schloming wrote:
> Posted here: http://people.apache.org/~rhs/qpid-proton-0.2rc4/
> 
> [X] Ship it! (Release RC4 as 0.2)
> [ ] No (We need another RC because...)
> 
> The only difference between RC3 and RC4 for proton-c is a one line change
> in engine.c that ensures that pn_transport_output will not fail to produce
> output under particular conditions despite there being output to produce.
> There was also a public accessor added in proton-j. Both of these are very
> small and sufficiently isolated changes that they shouldn't impact any
> testing that has been done on RC3. I've attached the total diff in case
> anyone wants to check it out. I'm hoping we can still get enough votes to
> do a release tonight so please have a look and give it your +1 if it checks
> out.

Will the final, official URL for the source be:

http://www.apache.org/dist/proton/$VER/qpid-proton-c-$VER.tar.gz

? I'd like to clean up another rpmlint error where it doesn't like a
non-URI value for the source.

-- 
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/



pgprHYchqOaf1.pgp
Description: PGP signature

Re: [VOTE] 0.2 RC4

[Rob Godfrey]

[X] Ship it! (Release RC4 as 0.2)

Tested java and reviewed C change.

-- Rob

On 5 November 2012 13:19, Rafael Schloming  wrote:

> Posted here: http://people.apache.org/~rhs/qpid-proton-0.2rc4/
>
> [ ] Ship it! (Release RC4 as 0.2)
> [ ] No (We need another RC because...)
>
> The only difference between RC3 and RC4 for proton-c is a one line change
> in engine.c that ensures that pn_transport_output will not fail to produce
> output under particular conditions despite there being output to produce.
> There was also a public accessor added in proton-j. Both of these are very
> small and sufficiently isolated changes that they shouldn't impact any
> testing that has been done on RC3. I've attached the total diff in case
> anyone wants to check it out. I'm hoping we can still get enough votes to
> do a release tonight so please have a look and give it your +1 if it checks
> out.
>
> --Rafael
>

[VOTE] 0.2 RC4

[Rafael Schloming]

Posted here: http://people.apache.org/~rhs/qpid-proton-0.2rc4/

[ ] Ship it! (Release RC4 as 0.2)
[ ] No (We need another RC because...)

The only difference between RC3 and RC4 for proton-c is a one line change
in engine.c that ensures that pn_transport_output will not fail to produce
output under particular conditions despite there being output to produce.
There was also a public accessor added in proton-j. Both of these are very
small and sufficiently isolated changes that they shouldn't impact any
testing that has been done on RC3. I've attached the total diff in case
anyone wants to check it out. I'm hoping we can still get enough votes to
do a release tonight so please have a look and give it your +1 if it checks
out.

--Rafael

Re: RC4

[Rafael Schloming]

Ok, I'm -1ing this one because ken's ssl fix didn't make it in. Sorry for
the churn. RC5 will be up shortly with ken's ssl fix in it.

--Rafael

On Thu, Oct 25, 2012 at 1:42 PM, Rafael Schloming  wrote:

> I've posted an RC4 here:
>
>   http://people.apache.org/~rhs/qpid-proton-0.1rc4/
>
> I believe both the koji issue and the decimal64 issue should be fixed now.
>
> The full changelog from the previous RC is here:
>
> 
> r1402224 | rhs | 2012-10-25 13:29:14 -0400 (Thu, 25 Oct 2012) | 1 line
>
> gracefully skip ssl tests when ssl is not built
> 
> r1402223 | mcpierce | 2012-10-25 13:16:49 -0400 (Thu, 25 Oct 2012) | 1 line
>
> NO-JIRA: Removes the path from the usage filename displayed for proton.
> 
> r1402221 | rhs | 2012-10-25 13:09:48 -0400 (Thu, 25 Oct 2012) | 1 line
>
> fixed swig interface typedefs
> 
> r1402217 | rgodfrey | 2012-10-25 13:00:37 -0400 (Thu, 25 Oct 2012) | 1 line
>
> PROTON-103 : Implement SASL in proton-j
> 
> r1402184 | kgiusti | 2012-10-25 11:01:06 -0400 (Thu, 25 Oct 2012) | 1 line
>
> NO-JIRA: fix warnings for swig code on older linux
> 
> r1402141 | kgiusti | 2012-10-25 09:11:29 -0400 (Thu, 25 Oct 2012) | 1 line
>
> NO-JIRA: fix macro name collision
> 
> r1402100 | rhs | 2012-10-25 06:57:27 -0400 (Thu, 25 Oct 2012) | 1 line
>
> don't ignore the return value of write
> 
> r1402079 | rhs | 2012-10-25 06:12:46 -0400 (Thu, 25 Oct 2012) | 1 line
>
> tweaked the README language
> 
> r1401959 | rajith | 2012-10-24 22:55:17 -0400 (Wed, 24 Oct 2012) | 2 lines
>
> PROTON-66 We now register for WRITE_OP if we are unable to write to the
> channel. As soon we are successful in writing we deregister the WRITE_OP.
>
>

RC4

[Rafael Schloming]

I've posted an RC4 here:

  http://people.apache.org/~rhs/qpid-proton-0.1rc4/

I believe both the koji issue and the decimal64 issue should be fixed now.

The full changelog from the previous RC is here:


r1402224 | rhs | 2012-10-25 13:29:14 -0400 (Thu, 25 Oct 2012) | 1 line

gracefully skip ssl tests when ssl is not built

r1402223 | mcpierce | 2012-10-25 13:16:49 -0400 (Thu, 25 Oct 2012) | 1 line

NO-JIRA: Removes the path from the usage filename displayed for proton.

r1402221 | rhs | 2012-10-25 13:09:48 -0400 (Thu, 25 Oct 2012) | 1 line

fixed swig interface typedefs

r1402217 | rgodfrey | 2012-10-25 13:00:37 -0400 (Thu, 25 Oct 2012) | 1 line

PROTON-103 : Implement SASL in proton-j

r1402184 | kgiusti | 2012-10-25 11:01:06 -0400 (Thu, 25 Oct 2012) | 1 line

NO-JIRA: fix warnings for swig code on older linux

r1402141 | kgiusti | 2012-10-25 09:11:29 -0400 (Thu, 25 Oct 2012) | 1 line

NO-JIRA: fix macro name collision

r1402100 | rhs | 2012-10-25 06:57:27 -0400 (Thu, 25 Oct 2012) | 1 line

don't ignore the return value of write

r1402079 | rhs | 2012-10-25 06:12:46 -0400 (Thu, 25 Oct 2012) | 1 line

tweaked the README language

r1401959 | rajith | 2012-10-24 22:55:17 -0400 (Wed, 24 Oct 2012) | 2 lines

PROTON-66 We now register for WRITE_OP if we are unable to write to the
channel. As soon we are successful in writing we deregister the WRITE_OP.