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

+1 And a separate +1 to Rob's suggestion. -Ted On 03/30/2016 06:30 AM, Rob Godfrey wrote: +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-mai

Re: Issues with Qpid dispatch make

Hi Paul, Which version did you download and on what platform are you attempting to build it? -Ted On 02/01/2016 05:45 PM, Paul Flores wrote: Hi, Downloaded qpid_dispatch. Have run into issues with Building C object src/CMakeFiles/qpid-dispatch.dir/compose.c.o at container.h ( at lines 17

[jira] [Resolved] (PROTON-510) hostname field in the Open command is not set

[ https://issues.apache.org/jira/browse/PROTON-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved PROTON-510. - Resolution: Fixed This is working properly as of 0.11. I assume it was fixed much earlier but I haven&#

[jira] [Resolved] (PROTON-485) Make SASL authentication optional

[ https://issues.apache.org/jira/browse/PROTON-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved PROTON-485. - Resolution: Fixed Fix Version/s: 0.10 > Make SASL authentication optio

[jira] [Updated] (PROTON-1088) Add convenience functions to obtain the client certificate fingerprint, subject subfields

[ https://issues.apache.org/jira/browse/PROTON-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-1088: - Priority: Major (was: Minor) > Add convenience functions to obtain the client certificate fingerpr

[jira] [Updated] (PROTON-1088) Add convenience functions to obtain the client certificate fingerprint, subject subfields

[ https://issues.apache.org/jira/browse/PROTON-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-1088: - Assignee: Ganesh Murthy > Add convenience functions to obtain the client certificate fingerpr

[jira] [Updated] (PROTON-1088) Add convenience functions to obtain the client certificate fingerprint, subject subfields

[ https://issues.apache.org/jira/browse/PROTON-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-1088: - Fix Version/s: 0.12.0 > Add convenience functions to obtain the client certificate fingerpr

Re: [VOTE] Release Qpid Proton 0.11.1

+1 I tested proton-c against qpid dispatch on Fedora 20. -Ted On 12/15/2015 02:32 PM, Robbie Gemmell wrote: Hi all, I have put up an RC for 0.11.1, please test it and vote accordingly. The release archive and sig/checksums can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/prot

[jira] [Commented] (PROTON-989) Multi-threaded creation of outgoing connections can crash inside the Cyrus SASL library

[ https://issues.apache.org/jira/browse/PROTON-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15031842#comment-15031842 ] Ted Ross commented on PROTON-989: - Dispatch has worked around this problem by usi

Re: Proton 0.11.0 release update - Beta is available

I installed the 0.11.0 beta, ran the test suite, built Dispatch from master against it, and ran the Dispatch test suite. I also ran the six-node dispatch-router scenario. There were no build or test issues. -Ted On 10/28/2015 06:49 AM, Justin Ross wrote: Hi, everyone. The beta is now avai

Re: proton 0.10 and swiftmq router

It looks like SwiftMQ is configured to require SASL authentication. If you supply authentication credentials (even "anonymous"), I believe this will work. -Ted On 10/02/2015 09:05 AM, Michael Ivanov wrote: Hallo, I am trying to run proton 0.10 client with SwiftMQ router and I'm getting the

[jira] [Commented] (PROTON-1008) Using a blank mech_list disables authentication

[ https://issues.apache.org/jira/browse/PROTON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935189#comment-14935189 ] Ted Ross commented on PROTON-1008: -- Is it ever sensible to not use SASL? Are t

[jira] [Created] (PROTON-1008) Using a blank mech_list disables authentication

Ted Ross created PROTON-1008: Summary: Using a blank mech_list disables authentication Key: PROTON-1008 URL: https://issues.apache.org/jira/browse/PROTON-1008 Project: Qpid Proton Issue Type

[jira] [Created] (PROTON-1004) Inconsistency in container.create_sender

Ted Ross created PROTON-1004: Summary: Inconsistency in container.create_sender Key: PROTON-1004 URL: https://issues.apache.org/jira/browse/PROTON-1004 Project: Qpid Proton Issue Type: Bug

Re: Bug in proton interop suite??

I don't think this is a valid data sequence. Literally, it is a binary sequence of seven octets where the internal encoding of a string is coincidental. Binary is not a compound type and does not contain sub-fields. -Ted On 09/08/2015 05:36 PM, aconway wrote: I'm doing some interop work on

[jira] [Created] (PROTON-989) Multi-threaded creation of outgoing connections can crash inside the Cyrus SASL library

Ted Ross created PROTON-989: --- Summary: Multi-threaded creation of outgoing connections can crash inside the Cyrus SASL library Key: PROTON-989 URL: https://issues.apache.org/jira/browse/PROTON-989 Project

Re: [VOTE] Release Qpid Proton 0.10 (RC3)

an issue and it can be identified, I'm sure it will be joined by others once a larger group of folks can actually get there hands on a release, and I'll happilly cut a 0.10.1 to address them if fixes are available. +1 Robbie On 13 August 2015 at 20:05, Ted Ross wrote: I ran the t

Re: [VOTE] Release Qpid Proton 0.10 (RC3)

I ran the tests under Ubuntu 14.04 (for amd64) running an x86_64 Linux kernel (using Docker). All of the tests, including the SSL tests pass. -Ted On 08/13/2015 09:56 AM, Robbie Gemmell wrote: I have run up a fresh Ubuntu 14.04.3 install didn't see any issues (once I figured out what packages

Re: [VOTE] Release Qpid Proton 0.10 (RC3)

+1 I tested proton-c against Dispatch Router. It all looks good. -Ted On 08/11/2015 04:08 PM, Robbie Gemmell wrote: Hi all, I have put up a third cut for 0.10, please test it and vote accordingly. Since RC2 there have been fixes for PROTON-978, PROTON-975, and PROTON-899. The release archi

[jira] [Updated] (PROTON-978) Framing errors after SASL exchange when max-frame-size is configured

[ https://issues.apache.org/jira/browse/PROTON-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-978: Attachment: commit-34b4c6d Proposed patch that fixes the problem. > Framing errors after SASL excha

[jira] [Updated] (PROTON-978) Framing errors after SASL exchange when max-frame-size is configured

[ https://issues.apache.org/jira/browse/PROTON-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-978: Attachment: commit-0d2ef9f Test update to detect the issue. > Framing errors after SASL exchange when

[jira] [Created] (PROTON-978) Framing errors after SASL exchange when max-frame-size is configured

Ted Ross created PROTON-978: --- Summary: Framing errors after SASL exchange when max-frame-size is configured Key: PROTON-978 URL: https://issues.apache.org/jira/browse/PROTON-978 Project: Qpid Proton

Re: [VOTE] Release Qpid Proton 0.10 (RC2)

-1 unfortunately. I've been testing against Dispatch and I'm seeing lots of timeouts on the tests. It turns out that pn_read_frame is used to parse text that is not a frame header. It's actually the AMQP header so it interprets the string "AMQP" as the frame length. Now that we're testing

[jira] [Created] (PROTON-970) SASL options for setting path and name should not be transport-specific

Ted Ross created PROTON-970: --- Summary: SASL options for setting path and name should not be transport-specific Key: PROTON-970 URL: https://issues.apache.org/jira/browse/PROTON-970 Project: Qpid Proton

[jira] [Created] (PROTON-969) Cyrus SASL module calls sasl_server_init once for every incoming connection

Ted Ross created PROTON-969: --- Summary: Cyrus SASL module calls sasl_server_init once for every incoming connection Key: PROTON-969 URL: https://issues.apache.org/jira/browse/PROTON-969 Project: Qpid Proton

[jira] [Updated] (PROTON-950) SASL PLAIN over cleartext should be supported

[ https://issues.apache.org/jira/browse/PROTON-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-950: Priority: Blocker (was: Major) > SASL PLAIN over cleartext should be suppor

[jira] [Commented] (PROTON-950) SASL PLAIN over cleartext should be supported

[ https://issues.apache.org/jira/browse/PROTON-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14630019#comment-14630019 ] Ted Ross commented on PROTON-950: - That makes two of us. I've updated it ac

[jira] [Updated] (PROTON-950) SASL PLAIN over cleartext should be supported

[ https://issues.apache.org/jira/browse/PROTON-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-950: Assignee: Andrew Stitcher > SASL PLAIN over cleartext should be suppor

[jira] [Created] (PROTON-950) SASL PLAIN over cleartext should be supported

Ted Ross created PROTON-950: --- Summary: SASL PLAIN over cleartext should be supported Key: PROTON-950 URL: https://issues.apache.org/jira/browse/PROTON-950 Project: Qpid Proton Issue Type: Bug

[jira] [Created] (PROTON-943) Bump library (.so) major version for proton-c libraries

Ted Ross created PROTON-943: --- Summary: Bump library (.so) major version for proton-c libraries Key: PROTON-943 URL: https://issues.apache.org/jira/browse/PROTON-943 Project: Qpid Proton Issue Type

Re: New python tox tests failing on fedora 22, Python 2.7.10/3.4.2

I had a similar error, not sure if it was exactly the same. I discovered that I was missing the python3-devel package. Once python3-devel was installed and I did a completely clean build, the problems went away. -Ted On 07/10/2015 10:01 AM, aconway wrote: Anyone seeing errors like this? I

[GitHub] qpid-proton pull request: Fix 2 Code Analysis warnings and a reall...

Github user ted-ross commented on the pull request: https://github.com/apache/qpid-proton/pull/39#issuecomment-118902728 I'd like to see this pull request move forward. On Dan's points above: 1) I agree with Andrew that using __LINE__ as an error code should be

Re: AMQP 1.0 and Shared Subscriptions

On 05/06/2015 10:05 AM, Ken Giusti wrote: Bump this up. I'm essentially in the same boat. The olso.messaging library in Openstack has introduced a feature called 'consumer pools' which is essentially the same pattern: a set of subscribers to a topic can belong to a pool. Each distinct pool

Re: [VOTE]: Release Proton 0.9.1-rc1 as 0.9.1

+1 On 04/29/2015 03:34 PM, Rafael Schloming wrote: Hi Everyone, I've put out an RC for 0.9.1 in the usual places. Source artifacts are here: https://people.apache.org/~rhs/qpid-proton-0.9.1-rc1/ Java binaries are here: https://repository.apache.org/content/repositories/orgapacheqpid

Re: 0.10 release time frame?

+1 I'd like to see an official release with the SASL updates as soon as practical. -Ted On 04/30/2015 09:37 PM, Rafael Schloming wrote: I'd like to see one fairly soon. I'm currently working through a few sasl-related interop issues between proton-c and proton-j, but once that is done and g

Re: [RESULT] [VOTE]: Proton 0.9-rc-3

Rafael, Do you have an ETA for the final bits? We're anxious to build some downstream packages. -Ted On 03/22/2015 02:44 PM, Rafael Schloming wrote: This vote passes with 8 binding +1's and no other votes. I will push the final bits soon. --Rafael On Tue, Mar 17, 2015 at 9:42 AM, Rafael S

Re: [VOTE]: Proton 0.9-rc-3

[ X ] Yes, release Proton 0.9-rc-3 as 0.9 final On 03/16/2015 04:42 PM, Rafael Schloming wrote: Hi Everyone, Here's a quick respin of 0.9-rc-3. The only changes from rc-2 are exactly those two mentioned on the rc-2 vote thread. I've included them at the end for reference. You can find the sour

Re: I think that's a blocker...

On 02/25/2015 11:52 AM, Rafael Schloming wrote: On Wed, Feb 25, 2015 at 10:49 AM, Ted Ross wrote: Would it be safe to assume that any operations on driver->io are not thread safe? Dispatch is a multi-threaded application. It looks to me as though io->error is a resource shared acro

Re: I think that's a blocker...

Would it be safe to assume that any operations on driver->io are not thread safe? Dispatch is a multi-threaded application. It looks to me as though io->error is a resource shared across the threads in an unsafe way. -Ted On 02/25/2015 08:55 AM, Rafael Schloming wrote: This isn't necessari

[jira] [Updated] (PROTON-825) BlockingReceiver.receive() uses 100% CPU.

[ https://issues.apache.org/jira/browse/PROTON-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-825: Assignee: Alan Conway (was: Ted Ross) > BlockingReceiver.receive() uses 100%

[jira] [Updated] (PROTON-817) BlockingConnection doesn't pass options down in create_sender or create_receiver

[ https://issues.apache.org/jira/browse/PROTON-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-817: Attachment: PROTON-817.patch > BlockingConnection doesn't pass options down in create_s

[jira] [Created] (PROTON-817) BlockingConnection doesn't pass options down in create_sender or create_receiver

Ted Ross created PROTON-817: --- Summary: BlockingConnection doesn't pass options down in create_sender or create_receiver Key: PROTON-817 URL: https://issues.apache.org/jira/browse/PROTON-817 Project:

[jira] [Updated] (PROTON-816) Add access to dynamic-node-properties in termini

[ https://issues.apache.org/jira/browse/PROTON-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-816: Attachment: PROTON-816.patch > Add access to dynamic-node-properties in term

[jira] [Created] (PROTON-816) Add access to dynamic-node-properties in termini

Ted Ross created PROTON-816: --- Summary: Add access to dynamic-node-properties in termini Key: PROTON-816 URL: https://issues.apache.org/jira/browse/PROTON-816 Project: Qpid Proton Issue Type: New

Re: reactor examples

Rafael, I'm a bit confused by this push. How does this set of examples relate to the examples Gordon has been developing in examples/engine/py? They are both "reactor" APIs with very similar structure yet they appear to be completely different and unrelated. Yours uses Reactor, on_delivery

[jira] [Updated] (PROTON-756) add a new/simpler setup.py for python bindings

[ https://issues.apache.org/jira/browse/PROTON-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-756: Priority: Blocker (was: Major) > add a new/simpler setup.py for python bindi

[jira] [Commented] (PROTON-764) Driver is multi-thread-unsafe when connections are closed uncleanly

[ https://issues.apache.org/jira/browse/PROTON-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236076#comment-14236076 ] Ted Ross commented on PROTON-764: - I've lowered the severity of this to minor.

[jira] [Updated] (PROTON-764) Driver is multi-thread-unsafe when connections are closed uncleanly

[ https://issues.apache.org/jira/browse/PROTON-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-764: Fix Version/s: (was: 0.9) > Driver is multi-thread-unsafe when connections are closed unclea

[jira] [Updated] (PROTON-764) Driver is multi-thread-unsafe when connections are closed uncleanly

[ https://issues.apache.org/jira/browse/PROTON-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-764: Priority: Minor (was: Major) > Driver is multi-thread-unsafe when connections are closed unclea

[jira] [Updated] (PROTON-764) Driver is multi-thread-unsafe when connections are closed uncleanly

[ https://issues.apache.org/jira/browse/PROTON-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-764: Priority: Major (was: Blocker) > Driver is multi-thread-unsafe when connections are closed unclea

[jira] [Created] (PROTON-764) Driver is multi-thread-unsafe when connections are closed uncleanly

Ted Ross created PROTON-764: --- Summary: Driver is multi-thread-unsafe when connections are closed uncleanly Key: PROTON-764 URL: https://issues.apache.org/jira/browse/PROTON-764 Project: Qpid Proton

Re: [VOTE]: migrate the proton repo to use git

[ X ] Yes, migrate the proton repo over to git. On 10/30/2014 06:59 AM, Rafael Schloming wrote: > Hi Everyone, > > I'm planning on updating the release script for 0.9 to automate the last > few details of the release process and to do proper branching. Given that > the release script must make us

Re: VOTE: Release Proton 0.8 RC5 as 0.8 final

[ X ] Yes, release Proton 0.8 RC5 as 0.8 final I tested 0.8 against the Dispatch trunk. On 10/27/2014 09:51 PM, Rafael Schloming wrote: > Hi Everyone, > > Sorry for the delay, there seemed to be some kind of Nexus outage today, so > I was unable to generate the java binaries until just now. > >

Re: Intro to proton

Hi Jake, You are trying to run Proton (AMQP 1.0) against a broker that only talks AMQP 0-10. You need to make sure that the broker is loading the "amqp.so" module so it can support the 1.0 protocol. qpidd --load-module amqp.so If you are building the broker from source, you need to make sure Pr

[jira] [Updated] (PROTON-548) Proton-C driver and URL Parsers don't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-548: Fix Version/s: 0.8 > Proton-C driver and URL Parsers don't support AF_INE

[jira] [Updated] (PROTON-548) Proton-C driver and URL Parsers don't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-548: Assignee: Cliff Jansen > Proton-C driver and URL Parsers don't support AF_INE

[jira] [Updated] (PROTON-643) Malloc result used without testing for null

[ https://issues.apache.org/jira/browse/PROTON-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-643: Fix Version/s: 0.8 > Malloc result used without testing for n

Re: Proton Performance Pictures (1 of 2)

On 09/03/2014 11:35 AM, Michael Goulish wrote: > > > > > - Original Message - >> On 09/03/2014 08:51 AM, Michael Goulish wrote: >>> That point is where I seem to find the best performance on my >>> system: 123,500 messages per second received. ( i.e. 247,000 >>> transfers per second

Re: proton engine performance: two strong credit management effects

On 08/27/2014 03:05 PM, Andrew Stitcher wrote: > On Wed, 2014-08-27 at 14:55 -0400, Andrew Stitcher wrote: >> ... >> Of this only applies under the exact circumstances of these tests, until >> we have more data points. I'd suspect it must also depend on the message >> size too. >> > > Just to re

Re: proton engine performance: two strong credit management effects

On 08/27/2014 02:55 PM, Andrew Stitcher wrote: > On Wed, 2014-08-27 at 13:39 -0400, Michael Goulish wrote: >> >> conclusion >> = >> >> >> Using the proton engine interface (in C) I am seeing two >> aspects of credit management that ca

[jira] [Commented] (PROTON-642) SASL Servers need to be able to optionally handle clients that don't use SASL

[ https://issues.apache.org/jira/browse/PROTON-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087749#comment-14087749 ] Ted Ross commented on PROTON-642: - Commit 1616245 from [~tedross] in branch 'pro

[jira] [Updated] (PROTON-485) Make SASL authentication optional

[ https://issues.apache.org/jira/browse/PROTON-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-485: Attachment: (was: PROTON-485.patch) > Make SASL authentication optio

[jira] [Commented] (PROTON-485) Make SASL authentication optional

[ https://issues.apache.org/jira/browse/PROTON-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087748#comment-14087748 ] Ted Ross commented on PROTON-485: - PROTON-642 was opened as a place to track the fix

[jira] [Created] (PROTON-642) SASL Servers need to be able to optionally handle clients that don't use SASL

Ted Ross created PROTON-642: --- Summary: SASL Servers need to be able to optionally handle clients that don't use SASL Key: PROTON-642 URL: https://issues.apache.org/jira/browse/PROTON-642 Project:

[jira] [Updated] (PROTON-485) Make SASL authentication optional

[ https://issues.apache.org/jira/browse/PROTON-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-485: Assignee: (was: Ted Ross) > Make SASL authentication optio

[jira] [Updated] (PROTON-485) Make SASL authentication optional

[ https://issues.apache.org/jira/browse/PROTON-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-485: Fix Version/s: (was: 0.8) > Make SASL authentication optio

[jira] [Resolved] (PROTON-485) Make SASL authentication optional

[ https://issues.apache.org/jira/browse/PROTON-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved PROTON-485. - Resolution: Fixed > Make SASL authentication optio

[jira] [Assigned] (PROTON-485) Make SASL authentication optional

[ https://issues.apache.org/jira/browse/PROTON-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned PROTON-485: --- Assignee: Ted Ross > Make SASL authentication optio

[jira] [Updated] (PROTON-485) Make SASL authentication optional

[ https://issues.apache.org/jira/browse/PROTON-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-485: Attachment: PROTON-485.patch Updated patch... Adds a method to sasl called "allow_skip" tha

[jira] [Updated] (PROTON-485) Make SASL authentication optional

[ https://issues.apache.org/jira/browse/PROTON-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-485: Attachment: (was: PROTON-485.patch) > Make SASL authentication optio

[jira] [Updated] (PROTON-485) Make SASL authentication optional

[ https://issues.apache.org/jira/browse/PROTON-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-485: Attachment: PROTON-485.patch The attached patch allows the server to gracefully handle a client that

[jira] [Commented] (PROTON-485) Make SASL authentication optional

[ https://issues.apache.org/jira/browse/PROTON-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084585#comment-14084585 ] Ted Ross commented on PROTON-485: - The SASL transport layer should handle a peer

[jira] [Updated] (PROTON-485) Make SASL authentication optional

[ https://issues.apache.org/jira/browse/PROTON-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-485: Fix Version/s: 0.8 > Make SASL authentication optio

Re: landing events branch

Another heads-up... I've updated dispatch-router to use the newly landed events in Proton. If you are building dispatch from source, you will need the latest Proton trunk. -Ted On 07/10/2014 12:41 PM, Rafael Schloming wrote: > Hi Everyone, > > I wanted to give people a quick heads up. I would l

[jira] [Reopened] (PROTON-548) Proton-C driver and URL Parsers don't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reopened PROTON-548: - I'm re-opening this issue so we can track this as it is implemented also for Windows. > Proton-

[jira] [Updated] (PROTON-548) Proton-C driver and URL Parsers don't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-548: Assignee: (was: Ted Ross) > Proton-C driver and URL Parsers don't support AF_INE

[jira] [Created] (PROTON-586) Driver spins when a listener accepts a socket while FDs are all in use

Ted Ross created PROTON-586: --- Summary: Driver spins when a listener accepts a socket while FDs are all in use Key: PROTON-586 URL: https://issues.apache.org/jira/browse/PROTON-586 Project: Qpid Proton

[jira] [Commented] (PROTON-567) Segmentation fault

[ https://issues.apache.org/jira/browse/PROTON-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978257#comment-13978257 ] Ted Ross commented on PROTON-567: - If you could provide a small reproducer for other

[jira] [Commented] (PROTON-567) Segmentation fault

[ https://issues.apache.org/jira/browse/PROTON-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978094#comment-13978094 ] Ted Ross commented on PROTON-567: - It looks like some form of memory mismanagement.

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

+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://repo

Re: new team working with AMQP and Apache Qpid Proton

Rob and team, Thanks for the introduction and welcome to the project. The mission of Qpid Proton is to encourage adoption of AMQP and to make it as easy as possible to integrate AMQP into anything and everything. As such, I think your goals are in alignment with the project's goals. I'll address

[jira] [Resolved] (PROTON-548) Proton-C driver and URL Parsers don't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved PROTON-548. - Resolution: Fixed Assignee: Ted Ross > Proton-C driver and URL Parsers don't support

[jira] [Updated] (PROTON-548) Proton-C driver and URL Parsers don't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-548: Attachment: (was: PROTON-548.patch) > Proton-C driver and URL Parsers don't support AF_INE

[jira] [Updated] (PROTON-548) Proton-C driver doesn't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-548: Component/s: proton-j > Proton-C driver doesn't support AF_INE

[jira] [Updated] (PROTON-548) Proton-C driver and URL Parsers don't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-548: Summary: Proton-C driver and URL Parsers don't support AF_INET6 (IPv6) (was: Proton-C driver do

[jira] [Updated] (PROTON-548) Proton-C driver doesn't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-548: Description: The proton-c driver hard-codes its sockets to AF_INET, rather than using the address family

[jira] [Updated] (PROTON-548) Proton-C driver doesn't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-548: Attachment: PROTON-548.patch Proposed patch. > Proton-C driver doesn't support AF_INE

[jira] [Updated] (PROTON-548) Proton-C driver doesn't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-548: Attachment: (was: PROTON-548.patch) > Proton-C driver doesn't support AF_INE

[jira] [Issue Comment Deleted] (PROTON-548) Proton-C driver doesn't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-548: Comment: was deleted (was: Proposed fix. I've tested this with Dispatch and have verified that al

[jira] [Updated] (PROTON-548) Proton-C driver doesn't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-548: Attachment: PROTON-548.patch Proposed fix. I've tested this with Dispatch and have verified that a

[jira] [Created] (PROTON-548) Proton-C driver doesn't support AF_INET6 (IPv6)

Ted Ross created PROTON-548: --- Summary: Proton-C driver doesn't support AF_INET6 (IPv6) Key: PROTON-548 URL: https://issues.apache.org/jira/browse/PROTON-548 Project: Qpid Proton Issue Type

[jira] [Created] (PROTON-541) Problems with multi-frame deliveries

Ted Ross created PROTON-541: --- Summary: Problems with multi-frame deliveries Key: PROTON-541 URL: https://issues.apache.org/jira/browse/PROTON-541 Project: Qpid Proton Issue Type: Bug

Re: Anonymous Producers

You have the option of leaving the target of a producer link empty and putting the destination in the "to" field of each message sent on the link. -Ted On 03/20/2014 11:36 PM, Clebert Suconic wrote: A common JMS feature is to have a Producer being anonymous and define the address only when th

Re: Proton 0.7 RC1

I tested this RC standalone and against Dispatch trunk. Everything worked as I expected. One note on the README: I tested on a stripped down Fedora 20 image and I had to install two additional packages to those listed in the README: - rubygem-minitest - maven -Ted On 03/14/2014 04

Re: Source/Target Question

Based on a discussion with Gordon, I'm not going to use source vs. target to infer any intent on the part of the peer node. I am, however, still interested in the answer to the question. -Ted On 02/21/2014 03:02 PM, Ted Ross wrote: I'm working on a feature for Dispatch Router that

Source/Target Question

I'm working on a feature for Dispatch Router that will allow it to intermediate between clients and brokers. This raises a question about how Proton Messenger handles targets and sources in links. Consider a subscriber using Messenger: from proton import Messenger M = Messenger()

Re: error when building proton

There's one other thing to be careful of... Once CMake determines that it's not there, it will not reconsider after you've installed the dependency. Make sure you delete your whole build directory and re-configure. -Ted On 02/05/2014 12:02 PM, Roberto Pagliari wrote: Hi Alan, I have uuid-d

[jira] [Created] (PROTON-510) hostname field in the Open command is not set

Ted Ross created PROTON-510: --- Summary: hostname field in the Open command is not set Key: PROTON-510 URL: https://issues.apache.org/jira/browse/PROTON-510 Project: Qpid Proton Issue Type: Bug

Re: Qpid Proton messenger on 32 bit linux

I haven't had a change to try it yet. I think we typically use "-m32 -march=i686" -Ted On 01/29/2014 09:56 AM, serega wrote: The attached example is a send.c slightly modified send.c example. It works in 64 bit environment, but crashe

Re: Qpid Proton messenger on 32 bit linux

I routinely run tests using Messenger in a 32-bit Linux environment and I've never had a problem with it. Are you building on a 64-bit machine or in a complete 32-bit environment? -Ted On 01/27/2014 03:43 PM, serega wrote: Does the messenger work on 32 bit linux? I build the 32 bit messenger

  1   2   3   >