Re: svn commit: r1504829 - /qpid/proton/trunk/proton-j/contrib/proton-hawtdispatch/src/main/java/org/apache/qpid/proton/hawtdispatch/impl/AmqpTransport.java

e all appearances to the contrary. The JIRAs are still open btw :) Robbie On 24 July 2013 13:12, Ted Ross wrote: Ack. You are quite right. My apologies for making you do work that I should have done myself. -Ted On 07/23/2013 03:32 PM, Robbie Gemmell wrote: This really shouldn't h

[jira] [Created] (PROTON-429) pn_bytes(size_t size, char *start) needs a const on the 'start' argument

Ted Ross created PROTON-429: --- Summary: pn_bytes(size_t size, char *start) needs a const on the 'start' argument Key: PROTON-429 URL: https://issues.apache.org/jira/browse/PROTON-429 Project: Q

[jira] [Updated] (PROTON-111) Support an idle time-out threshold.

[ https://issues.apache.org/jira/browse/PROTON-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-111: Assignee: Rafael H. Schloming > Support an idle time-out thresh

[jira] [Created] (PROTON-439) Support for dynamic reply-to address in Messenger

Ted Ross created PROTON-439: --- Summary: Support for dynamic reply-to address in Messenger Key: PROTON-439 URL: https://issues.apache.org/jira/browse/PROTON-439 Project: Qpid Proton Issue Type: New

[jira] [Comment Edited] (PROTON-439) Support for dynamic reply-to address in Messenger

[ https://issues.apache.org/jira/browse/PROTON-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790364#comment-13790364 ] Ted Ross edited comment on PROTON-439 at 10/9/13 2:0

[jira] [Commented] (PROTON-439) Support for dynamic reply-to address in Messenger

[ https://issues.apache.org/jira/browse/PROTON-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790364#comment-13790364 ] Ted Ross commented on PROTON-439: - Here's a proposed algorithm assuming Ken&#x

[jira] [Updated] (PROTON-439) Support for dynamic reply-to address in Messenger

[ https://issues.apache.org/jira/browse/PROTON-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-439: Fix Version/s: 0.6 > Support for dynamic reply-to address in Messen

[jira] [Created] (PROTON-441) Provide hooks for alternative sources of Messenger routes

Ted Ross created PROTON-441: --- Summary: Provide hooks for alternative sources of Messenger routes Key: PROTON-441 URL: https://issues.apache.org/jira/browse/PROTON-441 Project: Qpid Proton Issue

[jira] [Updated] (PROTON-439) Support for dynamic reply-to address in Messenger

[ https://issues.apache.org/jira/browse/PROTON-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-439: Assignee: Rafael H. Schloming > Support for dynamic reply-to address in Messen

[jira] [Updated] (PROTON-323) Regression: Messenger sends "null" in disposition state after accept

[ https://issues.apache.org/jira/browse/PROTON-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-323: Assignee: Rafael H. Schloming > Regression: Messenger sends "null" in disposition state

[jira] [Reopened] (PROTON-401) Ordering issue prevents credit drain from working properly

[ https://issues.apache.org/jira/browse/PROTON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reopened PROTON-401: - I don't believe the proposed solution really works. An intermediary with many outgoing links will

[jira] [Commented] (PROTON-401) Ordering issue prevents credit drain from working properly

[ https://issues.apache.org/jira/browse/PROTON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812823#comment-13812823 ] Ted Ross commented on PROTON-401: - I propose that proton consider the 'drained&

[jira] [Updated] (PROTON-401) Ordering issue prevents credit drain from working properly

[ https://issues.apache.org/jira/browse/PROTON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-401: Affects Version/s: (was: 0.4) 0.5 > Ordering issue prevents credit drain f

[jira] [Updated] (PROTON-401) Ordering issue prevents credit drain from working properly

[ https://issues.apache.org/jira/browse/PROTON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-401: Fix Version/s: 0.6 > Ordering issue prevents credit drain from working prope

[jira] [Commented] (PROTON-401) Ordering issue prevents credit drain from working properly

[ https://issues.apache.org/jira/browse/PROTON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812836#comment-13812836 ] Ted Ross commented on PROTON-401: - To put the proposal in the context of Rafi's

[jira] [Commented] (PROTON-401) Ordering issue prevents credit drain from working properly

[ https://issues.apache.org/jira/browse/PROTON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812951#comment-13812951 ] Ted Ross commented on PROTON-401: - That works for me. I just don't want to &

[jira] [Commented] (PROTON-401) Ordering issue prevents credit drain from working properly

[ https://issues.apache.org/jira/browse/PROTON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812978#comment-13812978 ] Ted Ross commented on PROTON-401: - My code only calls pn_link_drained once when

[jira] [Commented] (PROTON-401) Ordering issue prevents credit drain from working properly

[ https://issues.apache.org/jira/browse/PROTON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814034#comment-13814034 ] Ted Ross commented on PROTON-401: - If there is a way for the Engine user to determine

[jira] [Resolved] (PROTON-401) Ordering issue prevents credit drain from working properly

[ https://issues.apache.org/jira/browse/PROTON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved PROTON-401. - Resolution: Fixed The problem has been solved by using the pn_link_get_drain() query to determine when

[jira] [Created] (PROTON-466) Driver - Optimization causes hangs in cleanly closed connections

Ted Ross created PROTON-466: --- Summary: Driver - Optimization causes hangs in cleanly closed connections Key: PROTON-466 URL: https://issues.apache.org/jira/browse/PROTON-466 Project: Qpid Proton

[jira] [Updated] (PROTON-466) Driver - Optimization causes hangs in cleanly closed connections

[ https://issues.apache.org/jira/browse/PROTON-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-466: Attachment: PROTON-446.patch Patch that fixes the problem. > Driver - Optimization causes hangs

[jira] [Resolved] (PROTON-466) Driver - Optimization causes hangs in cleanly closed connections

[ https://issues.apache.org/jira/browse/PROTON-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved PROTON-466. - Resolution: Fixed > Driver - Optimization causes hangs in cleanly closed connecti

[jira] [Commented] (PROTON-439) Support for dynamic reply-to address in Messenger

[ https://issues.apache.org/jira/browse/PROTON-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837747#comment-13837747 ] Ted Ross commented on PROTON-439: - As of the last commit (1547100), this feature work

[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

[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

[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] [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] [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: (was: PROTON-548.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: 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: 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 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: 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: Attachment: (was: PROTON-548.patch) > Proton-C driver and URL Parsers don't support AF_INE

[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] [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.

[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] [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] [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] [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

[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: Attachment: PROTON-485.patch The attached patch allows the server to gracefully handle a client that

[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 Updated patch... Adds a method to sasl called "allow_skip" tha

[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] [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] [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] [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] [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: 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] [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-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

[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-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] [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

[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] [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: Fix Version/s: (was: 0.9) > Driver is multi-thread-unsafe when connections are closed unclea

[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-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] [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

[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-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-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] [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] [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

[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] [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] [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: Priority: Blocker (was: Major) > SASL PLAIN over cleartext should be suppor

[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] [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-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

[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-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

[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

[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] [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] [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

[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

[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: - Priority: Major (was: Minor) > Add convenience functions to obtain the client certificate fingerpr

[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] [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] [Created] (PROTON-6) Missing const on functions returning char*

Ted Ross created PROTON-6: - Summary: Missing const on functions returning char* Key: PROTON-6 URL: https://issues.apache.org/jira/browse/PROTON-6 Project: Qpid Proton Issue Type: Bug

[jira] [Created] (PROTON-11) Messenger parses addresses incorrectly.

Ted Ross created PROTON-11: -- Summary: Messenger parses addresses incorrectly. Key: PROTON-11 URL: https://issues.apache.org/jira/browse/PROTON-11 Project: Qpid Proton Issue Type: Bug

[jira] [Resolved] (PROTON-11) Messenger parses addresses incorrectly.

[ https://issues.apache.org/jira/browse/PROTON-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved PROTON-11. Resolution: Fixed Fixed in commit r1381306. > Messenger parses addresses incorrec

[jira] [Created] (PROTON-12) Delivery structure uses malloc/free for every delivery (delivery tag)

Ted Ross created PROTON-12: -- Summary: Delivery structure uses malloc/free for every delivery (delivery tag) Key: PROTON-12 URL: https://issues.apache.org/jira/browse/PROTON-12 Project: Qpid Proton

[jira] [Created] (PROTON-18) Add application context field to pn_connection_t

Ted Ross created PROTON-18: -- Summary: Add application context field to pn_connection_t Key: PROTON-18 URL: https://issues.apache.org/jira/browse/PROTON-18 Project: Qpid Proton Issue Type

[jira] [Updated] (PROTON-18) Add application context field to pn_connection_t

[ https://issues.apache.org/jira/browse/PROTON-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-18: --- Attachment: PROTON-18.patch > Add application context field to pn_connectio

[jira] [Commented] (PROTON-18) Add application context field to pn_connection_t

[ https://issues.apache.org/jira/browse/PROTON-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450845#comment-13450845 ] Ted Ross commented on PROTON-18: Patch attached. Note that I added only set/get met

[jira] [Created] (PROTON-24) Context fields are needed in link and session

Ted Ross created PROTON-24: -- Summary: Context fields are needed in link and session Key: PROTON-24 URL: https://issues.apache.org/jira/browse/PROTON-24 Project: Qpid Proton Issue Type: Improvement

[jira] [Updated] (PROTON-24) Context fields are needed in link and session

[ https://issues.apache.org/jira/browse/PROTON-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated PROTON-24: --- Attachment: proton.diff Proposed patch > Context fields are needed in link and sess

[jira] [Created] (PROTON-25) Connection doesn't transistion to PN_REMOTE_CLOSED when socket is closed.

Ted Ross created PROTON-25: -- Summary: Connection doesn't transistion to PN_REMOTE_CLOSED when socket is closed. Key: PROTON-25 URL: https://issues.apache.org/jira/browse/PROTON-25 Project: Qpid P

[jira] [Resolved] (PROTON-24) Context fields are needed in link and session

[ https://issues.apache.org/jira/browse/PROTON-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved PROTON-24. Resolution: Fixed > Context fields are needed in link and sess

[jira] [Created] (PROTON-30) The driver cannot be cleanly used in a multi-threaded application due to pn_driver_wait

Ted Ross created PROTON-30: -- Summary: The driver cannot be cleanly used in a multi-threaded application due to pn_driver_wait Key: PROTON-30 URL: https://issues.apache.org/jira/browse/PROTON-30 Project

[jira] [Commented] (PROTON-30) The driver cannot be cleanly used in a multi-threaded application due to pn_driver_wait

[ https://issues.apache.org/jira/browse/PROTON-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458230#comment-13458230 ] Ted Ross commented on PROTON-30: I'm committing a temporary solution to th

<    1   2   3   >