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,
ed=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\x0
0, 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 tu
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)
t;
>> 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 t
t; 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,
> >&g
vanov
>> 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
27;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
> >
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"
>>>> T
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, Oct
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&q
m: "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
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
[ 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.
[ 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 version
[ 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 RC
+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:
>
> - ht
[ 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.
>
> 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 a
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.apach
20 matches
Mail list logo
