Re: [NOTICE] the proton@ mailing list is being merged into the users/dev lists

On 18 April 2016 at 12:34, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > On 18 April 2016 at 11:42, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: >> The proton@q.a.o mailing list will merged into the users/dev lists, as >> you may already be aware from re

Re: [NOTICE] the proton@ mailing list is being merged into the users/dev lists

On 18 April 2016 at 11:42, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > The proton@q.a.o mailing list will merged into the users/dev lists, as > you may already be aware from recent threads. > > As part of this, around 50 subscribers to proton@ who are not also >

[NOTICE] the proton@ mailing list is being merged into the users/dev lists

The proton@q.a.o mailing list will merged into the users/dev lists, as you may already be aware from recent threads. As part of this, around 50 subscribers to proton@ who are not also currently subscribed to users@ will be subscribed to the users@ list. The proton@ list will then be retired and

[RESULT] [VOTE] Release Qpid Proton 0.12.2

There were 5 binding +1 votes, and no other votes received. The vote has passed. I will add the archives to the dist release repo and release the maven staging repo shortly. The website will be updated later after the artifacts have had time to sync to the mirrors and maven central. Robbie

[jira] [Commented] (PROTON-1177) [proton-j] Source and Target interfaces are incomplete and confusing

[ https://issues.apache.org/jira/browse/PROTON-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15242959#comment-15242959 ] Robbie Gemmell commented on PROTON-1177: Having more of a think about this, it probably resulted

[jira] [Created] (PROTON-1177) [proton-j] Source and Target interfaces are incomplete and confusing

Robbie Gemmell created PROTON-1177: -- Summary: [proton-j] Source and Target interfaces are incomplete and confusing Key: PROTON-1177 URL: https://issues.apache.org/jira/browse/PROTON-1177 Project

Re: [VOTE] Release Qpid Proton 0.12.2

On 14 April 2016 at 18:28, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > Hi all, > > I have put up an RC for 0.12.2, please test it and vote accordingly. > > The source release archive and sig/checksums can be grabbed from: > https://dist.apache.org/repos/dist/de

[VOTE] Release Qpid Proton 0.12.2

Hi all, I have put up an RC for 0.12.2, please test it and vote accordingly. The source release archive and sig/checksums can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton/0.12.2-rc1/ Maven artifacts for the Java bits can be found in a temporary staging repo at:

Re: Proton 0.12.2 release

Quinn <fquinn...@gmail.com> wrote: > Hi Robbie, > > Would appreciate if someone could take a look at this one: > https://issues.apache.org/jira/browse/PROTON-1169 > > Cheers, > Frank > > On Wed, Apr 13, 2016 at 3:11 PM, Robbie Gemmell <robbie.gemm...@gmail.co

Proton 0.12.2 release

Hi folks, I'd like to do a 0.12.2 release to incorporate a proton-j fix for https://issues.apache.org/jira/browse/PROTON-1171. If all goes well with feedback on that change I would propose to spin a release candidate in the next day or so. If you have any targetted bug fixes you would like to

[jira] [Updated] (PROTON-1171) [proton-j] transport SSL wrapper does not flush all decoded bytes to the underlying input

[ https://issues.apache.org/jira/browse/PROTON-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1171: --- Fix Version/s: 0.12.2 > [proton-j] transport SSL wrapper does not flush all decoded by

[jira] [Updated] (PROTON-1171) [proton-j] transport SSL wrapper does not flush all decoded bytes to the underlying input

[ https://issues.apache.org/jira/browse/PROTON-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1171: --- Affects Version/s: 0.12.1 > [proton-j] transport SSL wrapper does not flush all deco

[jira] [Assigned] (PROTON-1171) [proton-j] transport SSL wrapper does not flush all decoded bytes to the underlying input

[ https://issues.apache.org/jira/browse/PROTON-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned PROTON-1171: -- Assignee: Robbie Gemmell > [proton-j] transport SSL wrapper does not flush

[jira] [Updated] (PROTON-1171) [proton-j] transport SSL wrapper does not flush all decoded bytes to the underlying input

[ https://issues.apache.org/jira/browse/PROTON-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1171: --- Summary: [proton-j] transport SSL wrapper does not flush all decoded bytes to the underlying

Re: Proton-j Reactor - Receiver

N-1171). > > Thanks a lot for the Wonderful Collaboration! > Sree > > From: Robbie Gemmell<mailto:robbie.gemm...@gmail.com> > Sent: Thursday, April 7, 2016 3:52 AM > To: proton@qpid.apache.org<mailto:proton@qpid.apache.org> > Cc: SeongJoon Kwak (SJ)<mail

[jira] [Updated] (PROTON-1168) 2-way Authentication via Certificates Fails in Proton-J

[ https://issues.apache.org/jira/browse/PROTON-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1168: --- Attachment: ssl_logs1.tar.gz Attaching ssl_logs1.tar.gz with console logs from the broker

Re: Proton-j Reactor - Receiver

mpty. Here’s the pull request - https://github.com/apache/qpid-proton/pull/73 > > Pl. let me know if we need to do more to fix this issue comprehensively. > > Thx! > Sree > > From: Robbie Gemmell<mailto:robbie.gemm...@gmail.com> > Sent: Thursday, March 31, 2016 9:19 AM

Re: Amqp-ConnProp: user-agent

; > reuse those … > > Thx! > Sree > > From: Robbie Gemmell<mailto:robbie.gemm...@gmail.com> > Sent: Tuesday, April 5, 2016 10:14 AM > To: proton@qpid.apache.org<mailto:proton@qpid.apache.org> > Subject: Re: Amqp-ConnProp: user-agent > > Many of the Qpid

Re: Amqp-ConnProp: user-agent

Many of the Qpid components advertise "product" and "version" connection properties containing strings with the appropriate details. Those [Symbol] keys were chosen because they happened to be names specified in the older AMQP 0-x specs, and so matched what some of the components were already

[jira] [Updated] (PROTON-1168) 2-way Authentication via Certificates Fails in Proton-J

[ https://issues.apache.org/jira/browse/PROTON-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1168: --- Attachment: PROTON-1168_reactor_ssl.patch I posted the following reply on the users list

[RESULT] [VOTE] merge the proton mailing list into the users/dev lists

There were 13 binding +1 votes received and another 2 from users, with no other votes received. The vote has passed. I'll chat with infra in the days ahead about how things proceed. Robbie

Re: Proton-j Reactor - Receiver

On 31 March 2016 at 04:32, Garlapati Sreeram Kumar wrote: > Hello All! > > I am using Proton-J reactor API (Version 0.12.0) for receiving AMQP Messages > (from Microsoft Azure Event Hubs): >

Re: [VOTE] merge the proton mailing list into the users/dev lists

: > +1 > > Additionally it might make sense to write a paragraph somewhere on > suggestions for best practice on mailing the list (like including > components / languages in use in the title or the body of the e-mail :-) ). > > -- Rob > > On 30 March 2016 at 11:25, Robbie

[VOTE] merge the proton mailing list into the users/dev lists

Hello folks, Many moons ago, a seperate mailing list was established for Proton, back when it was purely a protocol engine other components would use. Its scope has since expanded beyond that and the separate mailing list has I feel been an increasing source of confusion and hassle of late more

Re: Proton-j: SendLink flow control

On 25 March 2016 at 19:06, Garlapati Sreeram Kumar wrote: > Hello All! > > We are using the Proton-J 0.12.0 Amqp library – and built Event Hubs Java > Amqp Client on Reactor framework - > https://github.com/Azure/azure-event-hubs/tree/master/java. > > Please validate my

Re: SASL

Hi Kai, As Gordon noted, proton can be used in different ways. In the case where it is used purely as an AMQP protocol engine with e.g TLS being provided by the external IO being used with it, getting the Principal would currently fall to that code rather than proton. That is how proton-j

Re: Proton-J Reactor sending delay

applications using the Reactor do suffer > a bit of a blow in performance because of this. > > Thanks, > -Andrew > > -Original Message- > From: Robbie Gemmell [mailto:robbie.gemm...@gmail.com] > Sent: Monday, February 15, 2016 3:47 AM > To: d...@qpid.apache.org; proton@qp

Re: Proton-J Reactor sending delay

3 seconds is quite a long time to wait between calling send and the >> action actually being performed, and applications using the Reactor do >> suffer a bit of a blow in performance because of this. >> >> Thanks, >> -Andrew >> >> -Original Mess

[jira] [Created] (PROTON-1146) [proton-j] fixes for issues identified by Coverity

Robbie Gemmell created PROTON-1146: -- Summary: [proton-j] fixes for issues identified by Coverity Key: PROTON-1146 URL: https://issues.apache.org/jira/browse/PROTON-1146 Project: Qpid Proton

Re: How does one setup a topic using qpid-config tyo satisfy QPID JMS requirements?

The topic config in the jndi.properties file is just an example, only the queue is used by the code for the examples. But to answer the question, one model of a topic in qpidd would be to create an exchange of that name, of either topic or fanout type. Robbie On 22 February 2016 at 17:47,

Re: Help?!: Qpid JMS 0.6.0 HelloWorld example issue

Glad to hear you got past the issue with your jndi config. Jakub's mail covers your question on qpid-config. Note you can also have the broker auto-create queues as needed using the CLI option I mentioned in your recent thread on the users list. As an aside, the current release of the client has

[jira] [Commented] (PROTON-1136) [proton-j] handle the case when pipelined SASL and OPEN frames are sent for ANONYMOUS login

[ https://issues.apache.org/jira/browse/PROTON-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15150804#comment-15150804 ] Robbie Gemmell commented on PROTON-1136: Your comment essentially exactly represents my thinking

[jira] [Updated] (PROTON-1135) [proton-c] dont pipeline SASL and OPEN frames for ANONYMOUS logins by default

[ https://issues.apache.org/jira/browse/PROTON-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1135: --- Description: Dispatch router (which uses Proton-c) currently sends pipelined SASL and OPEN

[jira] [Updated] (PROTON-1136) [proton-j] handle the case when pipelined SASL and OPEN frames are sent for ANONYMOUS login

[ https://issues.apache.org/jira/browse/PROTON-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1136: --- Description: Currently Proton-J is unable to handle pipelined SASL and OPEN frames

[jira] [Created] (PROTON-1137) [proton-j] SaslSniffer throws exception if given less than 8 bytes.

Robbie Gemmell created PROTON-1137: -- Summary: [proton-j] SaslSniffer throws exception if given less than 8 bytes. Key: PROTON-1137 URL: https://issues.apache.org/jira/browse/PROTON-1137 Project

Re: Proton-J Reactor sending delay

On 13 February 2016 at 00:28, Andrew Buckley wrote: > I'm using the reactor with Proton-J and have noticed that there is a 2-4 > second delay between when I call send() on a particular link and when that > transfer frame actually goes out. Is this expected behavior? If so,

Re: proton-j reactor socket error recovery

On 13 February 2016 at 08:59, Garlapati Sreeram Kumar wrote: > Hello All! > > Question on reactor framework expected behavior: > - I am implementing an AmqpClient (for Azure EventHubs) and using > reactor.connection(connxnHandler) to get a new out-bound connection and then >

[jira] [Updated] (PROTON-1125) c++: core dump on empty address in link options

[ https://issues.apache.org/jira/browse/PROTON-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1125: --- Affects Version/s: (was: 0.12.0) Fix Version/s: (was: 0.12.1

[jira] [Resolved] (PROTON-1125) c++: core dump on empty address in link options

[ https://issues.apache.org/jira/browse/PROTON-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-1125. Resolution: Fixed > c++: core dump on empty address in link opti

[jira] [Commented] (PROTON-1094) c++: refactor and documentation of type conversions

[ https://issues.apache.org/jira/browse/PROTON-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142506#comment-15142506 ] Robbie Gemmell commented on PROTON-1094: [~aconway] what is the status on this? Done? Bump

[jira] [Commented] (PROTON-1071) EventInjector hangs on Windows

[ https://issues.apache.org/jira/browse/PROTON-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142508#comment-15142508 ] Robbie Gemmell commented on PROTON-1071: [~cliffjansen] what is the status on this? Done? Bump

[jira] [Commented] (PROTON-1063) ruby: ruby reactor holds GVL in process

[ https://issues.apache.org/jira/browse/PROTON-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142511#comment-15142511 ] Robbie Gemmell commented on PROTON-1063: [~aconway] what is the status on this? Done? Bump

[jira] [Commented] (PROTON-1064) ruby: add ConnectionEngine alterntive integration style

[ https://issues.apache.org/jira/browse/PROTON-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142510#comment-15142510 ] Robbie Gemmell commented on PROTON-1064: [~aconway] what is the status on this? Done? Bump

[jira] [Commented] (PROTON-1046) C++ multi-threaded broker example

[ https://issues.apache.org/jira/browse/PROTON-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142512#comment-15142512 ] Robbie Gemmell commented on PROTON-1046: [~aconway] what is the status on this? Done? Bump

Re: [VOTE] Release RC 3 as Qpid Proton 0.12.0

Thanks, saved me sending that :) Robbie On 10 February 2016 at 15:35, Rob Godfrey wrote: > To be pedantic, only PMC members votes are officially considered binding > [1], and votes from committers who are not on the PMC are not... However in > general as a community we

Re: [VOTE] Release RC 3 as Qpid Proton 0.12.0

On 10 February 2016 at 14:04, Justin Ross wrote: > Hi, everyone. RC 2 had some embedded build output, which this RC removes. > Apart from that removal, it has the same content as RC 2. > > The proposed release artifacts: > >

Re: [VOTE] Release RC 2 as Qpid Proton 0.12.0

On 9 February 2016 at 14:11, Justin Ross wrote: > The artifacts proposed for release: > > https://dist.apache.org/repos/dist/dev/qpid/proton/0.12.0-rc2/ > > Please indicate your vote below. If you favor releasing the 0.12.0 RC 2 > bits as 0.12.0 GA, vote +1. If you

Re: [VOTE] Release RC 2 as Qpid Proton 0.12.0

On 10 February 2016 at 10:36, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > On 9 February 2016 at 14:11, Justin Ross <justin.r...@gmail.com> wrote: >> The artifacts proposed for release: >> >> https://dist.apache.org/repos/dist/dev/qpid/proton/0.12.0-rc2

Re: Best practices using proton-j Reactor

Hi Sree, I'm not too familiar with the Reactor bits, I've never used them beyong the send/recv examples, but I'll try to answer what I can. Perhaps other folks can chime in if they know more (even if based on knowledge of the proton-c reactor). Responses inline. On 3 February 2016 at 20:05,

Re: [VOTE] Release Qpid Proton 0.12.0

On 3 February 2016 at 15:10, Justin Ross wrote: > The artifacts proposed for release: > > https://dist.apache.org/repos/dist/dev/qpid/proton/0.12.0-rc/ > > Please indicate your vote below. If you favor releasing the 0.12.0 RC bits > as 0.12.0 GA, vote +1. If you have

[jira] [Commented] (PROTON-1050) 0.12.0 release tasks

[ https://issues.apache.org/jira/browse/PROTON-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15132459#comment-15132459 ] Robbie Gemmell commented on PROTON-1050: I think we should probably mention something somwhere

[jira] [Updated] (PROTON-1125) c++: core dump on empty address in link options

[ https://issues.apache.org/jira/browse/PROTON-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1125: --- Affects Version/s: 0.12.0 Fix Version/s: (was: 0.12.0

[jira] [Comment Edited] (PROTON-1070) validate the Open frame having been received before other frames

[ https://issues.apache.org/jira/browse/PROTON-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112292#comment-15112292 ] Robbie Gemmell edited comment on PROTON-1070 at 2/2/16 10:56 AM

Re: JIRA 515 and release 0.12.0

Andrew/Alan/Any-other-C-inclined-folks, can you look at this? I know a large sticking point is likely to be that we probably have no easy way to test things on OpenVMS, but as it seems quite contained (though perhaps not in the desired style?) I think approaching it on a 'if it doesn't break

[jira] [Updated] (PROTON-968) [proton-j] validate local/remote channel-max is adhered to

[ https://issues.apache.org/jira/browse/PROTON-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-968: -- Affects Version/s: (was: 0.10) 0.12.0 Fix Version/s

Re: Proton-J and WebSocket support

On 29 January 2016 at 07:01, Clemens Vasters wrote: > It appears that Proton-J doesn't implement the WebSocket protocol binding, > yet. (I may also not be looking in the right places) > > Is that on the backlog for some time in the nearer future? > > Thank you > Clemens >

[jira] [Updated] (PROTON-1091) [Python binding] AMQP null type not sent on wire according to AMQP specification

[ https://issues.apache.org/jira/browse/PROTON-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1091: --- Fix Version/s: (was: 0.12.0) 0.13.0 > [Python binding] AMQP null t

[jira] [Updated] (PROTON-985) Modify pn_transport_tick to explicitly use a monotonic clock, not wall clock time

[ https://issues.apache.org/jira/browse/PROTON-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-985: -- Fix Version/s: (was: 0.12.0) 0.13.0 > Modify pn_transport_t

[jira] [Updated] (PROTON-1114) [proton-j] the transport should not emit other frames after the Close frame has been sent

[ https://issues.apache.org/jira/browse/PROTON-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1114: --- Affects Version/s: (was: 0.12.0) 0.11.1 Fix Version/s

[jira] [Updated] (PROTON-1113) tidy up some descriptive detail around running the python tests

[ https://issues.apache.org/jira/browse/PROTON-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1113: --- Fix Version/s: (was: 0.13.0) 0.12.0 Description: Merged to 0.12

Re: Request for inclusion in 0.12.0

9, 2016 at 9:21 AM, Andrew Stitcher <astitc...@redhat.com> > wrote: > >> I've approved both of these for inclusion (in the JIRAs). >> >> Andrew >> >> On Thu, 2016-01-28 at 11:04 +, Robbie Gemmell wrote: >> > Hi Justin, >> > >> >

Re: RFI: PROTON-1055 (SASL Plain authentication can fail on some brokers)

On 27 January 2016 at 21:09, Andrew Stitcher wrote: > This [1] is really an interop bug, but I suspect it will be annoying to > anyone using earlier versions of ActiveMQ. > > The fix is pretty small and seems low risk to me. > > Andrew > > [1]

[jira] [Commented] (PROTON-1055) Username sent twice during SASL AUTH

[ https://issues.apache.org/jira/browse/PROTON-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121361#comment-15121361 ] Robbie Gemmell commented on PROTON-1055: The change looks good to me, and I think it should

Request for inclusion in 0.12.0

Hi Justin, I'd like to request the following for inclusion in 0.12.0: Stop the proton-j transport from erroneously emitting various frame types after a Close was sent. https://issues.apache.org/jira/browse/PROTON-1114 https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=bcd08cc Some

[jira] [Created] (PROTON-1113) tidy up some descriptive detail around running the python tests

Robbie Gemmell created PROTON-1113: -- Summary: tidy up some descriptive detail around running the python tests Key: PROTON-1113 URL: https://issues.apache.org/jira/browse/PROTON-1113 Project: Qpid

[jira] [Resolved] (PROTON-1114) [proton-j] the transport should not emit other frames after the Close frame has been sent

[ https://issues.apache.org/jira/browse/PROTON-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-1114. Resolution: Fixed > [proton-j] the transport should not emit other frames after the Cl

[jira] [Resolved] (PROTON-1113) tidy up some descriptive detail around running the python tests

[ https://issues.apache.org/jira/browse/PROTON-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-1113. Resolution: Fixed > tidy up some descriptive detail around running the python te

[jira] [Commented] (PROTON-1111) Fix warnings during make doc

[ https://issues.apache.org/jira/browse/PROTON-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119426#comment-15119426 ] Robbie Gemmell commented on PROTON-: I remember asking [~gsim] about warnings in the doc

[jira] [Created] (PROTON-1110) [proton-j] allow suppressing the synthentic flow event when sending transfers

Robbie Gemmell created PROTON-1110: -- Summary: [proton-j] allow suppressing the synthentic flow event when sending transfers Key: PROTON-1110 URL: https://issues.apache.org/jira/browse/PROTON-1110

[jira] [Updated] (PROTON-1107) [proton-j] only create the attachments Record on a Delivery if it actually gets used

[ https://issues.apache.org/jira/browse/PROTON-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1107: --- Fix Version/s: (was: 0.13.0) 0.12.0 > [proton-j] only cre

[jira] [Updated] (PROTON-1110) [proton-j] allow suppressing the synthentic flow event when sending transfers

[ https://issues.apache.org/jira/browse/PROTON-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1110: --- Fix Version/s: (was: 0.12.0) 0.13.0 > [proton-j] allow suppress

[jira] [Updated] (PROTON-1107) [proton-j] only create the attachments Record on a Delivery if it actually gets used

[ https://issues.apache.org/jira/browse/PROTON-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1107: --- Fix Version/s: (was: 0.12.0) 0.13.0 > [proton-j] only cre

[jira] [Updated] (PROTON-1110) [proton-j] allow suppressing the synthentic flow event when sending transfers

[ https://issues.apache.org/jira/browse/PROTON-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1110: --- Affects Version/s: 0.12.0 > [proton-j] allow suppressing the synthentic flow event w

Request for inclusion in 0.12.0 beta

Hi Justin, I see you have created the 0.12.x branch, but before you actually spin the beta, could I request the following... The latest commit on https://issues.apache.org/jira/browse/PROTON-1100 didnt make the branch. https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=6422e24 Also

[jira] [Commented] (PROTON-1100) [proton-j] the transport should not emit other frames before the Open frame has been sent

[ https://issues.apache.org/jira/browse/PROTON-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117262#comment-15117262 ] Robbie Gemmell commented on PROTON-1100: The last commit above on master has now been merged

[jira] [Updated] (PROTON-1110) [proton-j] allow suppressing the synthentic flow event when sending transfers

[ https://issues.apache.org/jira/browse/PROTON-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1110: --- Affects Version/s: (was: 0.12.0) Fix Version/s: (was: 0.13.0

[jira] [Resolved] (PROTON-1110) [proton-j] allow suppressing the synthentic flow event when sending transfers

[ https://issues.apache.org/jira/browse/PROTON-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-1110. Resolution: Fixed > [proton-j] allow suppressing the synthentic flow event when send

Re: Request for inclusion in 0.12.0 beta

Great, thanks Justin. Both changes are now picked onto the 0.12.x branch. Robbie On 26 January 2016 at 14:16, Justin Ross <justin.r...@gmail.com> wrote: > Thanks, Robbie. Both are approved. > > > On Tue, Jan 26, 2016 at 6:10 AM, Robbie Gemmell <robbie.gemm...@gmail.com>

[jira] [Created] (PROTON-1107) [proton-j] only create the attachments Record on a Delivery if it actually gets used

Robbie Gemmell created PROTON-1107: -- Summary: [proton-j] only create the attachments Record on a Delivery if it actually gets used Key: PROTON-1107 URL: https://issues.apache.org/jira/browse/PROTON-1107

[jira] [Resolved] (PROTON-1107) [proton-j] only create the attachments Record on a Delivery if it actually gets used

[ https://issues.apache.org/jira/browse/PROTON-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-1107. Resolution: Fixed > [proton-j] only create the attachments Record on a Deliv

cpp binding failing builds in CI (WAS: [2/2] qpid-proton git commit: PROTON-1062: c++: proton::connection_engine with client and server examples.)

On 24 January 2016 at 07:19, wrote: > PROTON-1062: c++: proton::connection_engine with client and server examples. > > Easier to use proton::connction_engine: > - inherit and override io_read, io_write, io_close to provide IO > functionality. > - processing logic

[jira] [Created] (PROTON-1105) enable EventImpl#getTransport() to succeed in more situations

Robbie Gemmell created PROTON-1105: -- Summary: enable EventImpl#getTransport() to succeed in more situations Key: PROTON-1105 URL: https://issues.apache.org/jira/browse/PROTON-1105 Project: Qpid

[jira] [Resolved] (PROTON-1105) enable EventImpl#getTransport() to succeed in more situations

[ https://issues.apache.org/jira/browse/PROTON-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-1105. Resolution: Fixed > enable EventImpl#getTransport() to succeed in more situati

[jira] [Updated] (PROTON-1070) validate the Open frame having been received before other frames

[ https://issues.apache.org/jira/browse/PROTON-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1070: --- Description: I recently saw an odd test failure while making changes to some other code

[jira] [Updated] (PROTON-1070) validate the Open frame having been received before other frames

[ https://issues.apache.org/jira/browse/PROTON-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1070: --- Affects Version/s: (was: 0.11.0) 0.12.0 > validate the Open fr

[jira] [Resolved] (PROTON-1100) [proton-j] the transport should not emit other frames before the Open frame has been sent

[ https://issues.apache.org/jira/browse/PROTON-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-1100. Resolution: Fixed > [proton-j] the transport should not emit other frames before the O

[jira] [Updated] (PROTON-1017) Engine does not handle UNINITALIZED/CLOSED sessions

[ https://issues.apache.org/jira/browse/PROTON-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1017: --- Attachment: PROTON-1017-WIP.patch Attaching a WIP patch. Isn't complete as its a fairly

Re: Include PROTON-1096 in the release Proton-0.12

Fear not Sreeram, the change will be included in 0.12. The 0.12 alpha was cut from master mainly to serve as a heads up the release process is going to get under way, and help tease out any obvious issues before a 0.12.x branch is created to progress the release via a beta and any subsequent

[jira] [Created] (PROTON-1100) [proton-j] the transport should not emit other frames before the Open frame has been sent

Robbie Gemmell created PROTON-1100: -- Summary: [proton-j] the transport should not emit other frames before the Open frame has been sent Key: PROTON-1100 URL: https://issues.apache.org/jira/browse/PROTON-1100

[jira] [Updated] (PROTON-259) engine operations do not check if the endpoint is already closed

[ https://issues.apache.org/jira/browse/PROTON-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-259: -- Assignee: (was: Philip Harvey) Component/s: (was: proton-j) Summary

[jira] [Resolved] (PROTON-713) TransportImpl#setChannelMax does not enforce legal value range, may cause unexpected results

[ https://issues.apache.org/jira/browse/PROTON-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-713. --- Resolution: Fixed Fix Version/s: 0.12.0 The behaviour was already changed somewhat

[jira] [Assigned] (PROTON-713) TransportImpl#setChannelMax does not enforce legal value range, may cause unexpected results

[ https://issues.apache.org/jira/browse/PROTON-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned PROTON-713: - Assignee: Robbie Gemmell > TransportImpl#setChannelMax does not enforce legal va

Re: Please update appveyor.yml version [Was: Proton 0.12.0 release update - Alpha is available]

Can I suggest a more basic change of simply removing the release version from the Appveyor job id? None of the other CI jobs have that, and given it has been wrong for around 5 months it doesn't seem particularly noted by most folks. The branch name could still be there as it is now, which in

[jira] [Reopened] (PROTON-1096) [proton-j] enable set/get of MessageFormat on the Delivery being sent/received

[ https://issues.apache.org/jira/browse/PROTON-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reopened PROTON-1096: Reopening. While I was expanding the changes proposed in the PR to cover received Deliveries

[jira] [Resolved] (PROTON-1096) [proton-j] enable set/get of MessageFormat on the Delivery being sent/received

[ https://issues.apache.org/jira/browse/PROTON-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-1096. Resolution: Fixed > [proton-j] enable set/get of MessageFormat on the Delivery be

Re: Android client / ServiceBus

On 19 January 2016 at 15:15, tourili wrote: > Any hint from some experimented with this topic PLEASE > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/Android-client-ServiceBus-tp7636619p7636821.html > Sent from the Apache Qpid Proton mailing

Re: Please update appveyor.yml version [Was: Proton 0.12.0 release update - Alpha is available]

On 19 January 2016 at 15:25, Andrew Stitcher <astitc...@redhat.com> wrote: > On Tue, 2016-01-19 at 10:39 +0000, Robbie Gemmell wrote: >> Can I suggest a more basic change of simply removing the release >> version from the Appveyor job id? >> >> None of the other CI

[jira] [Closed] (PROTON-635) PN_TRANSPORT events not generated in enough places

[ https://issues.apache.org/jira/browse/PROTON-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed PROTON-635. - Fully closing issue since it is marked with a released fix-version. > PN_TRANSPORT eve

[jira] [Commented] (PROTON-1098) Add support for one or More Data Sections in AmqpMessage

[ https://issues.apache.org/jira/browse/PROTON-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098238#comment-15098238 ] Robbie Gemmell commented on PROTON-1098: Commented on the PR but forgot to mention the JIRA key

[jira] [Resolved] (PROTON-1096) [proton-j] enable set/get of MessageFormat on the Delivery being sent/received

[ https://issues.apache.org/jira/browse/PROTON-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-1096. Resolution: Fixed Fix Version/s: 0.12.0 > [proton-j] enable set/

  1   2   3   4   5   6   >