[jira] [Updated] (PROTON-168) Support for building on OS X

[ https://issues.apache.org/jira/browse/PROTON-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-168: - Attachment: SO_NOSIGPIPE.patch Attaching patch that sets the SO_NOSIGPIPE socket option when on O

PROTON - amqp 1.0 support

Hi, I'm trying to use the optional amqp 1.0 support for qpid within cmake, but I get the following message in debug mode: CMake Error at src/amqp.cmake:38 (message): Qpid proton not found, required for amqp 1.0 support. I have the environment system variables - PROTON_HOME and PROJECT_SOU

[jira] [Updated] (PROTON-168) Support for building on OS X

[ https://issues.apache.org/jira/browse/PROTON-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-168: - Attachment: nowerror.patch and here's a patch to disable -Werror on OSX > Suppor

[jira] [Updated] (PROTON-168) Support for building on OS X

[ https://issues.apache.org/jira/browse/PROTON-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-168: - Attachment: clock.patch Here's a patch that incorporates Mr Goldstein's OS X clock handling. Wou

[jira] [Commented] (PROTON-168) Support for building on OS X

[ https://issues.apache.org/jira/browse/PROTON-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505967#comment-13505967 ] Andrew Stitcher commented on PROTON-168: Cool - that's the effect I was expecting

[jira] [Commented] (PROTON-168) Support for building on OS X

[ https://issues.apache.org/jira/browse/PROTON-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505963#comment-13505963 ] Hiram Chirino commented on PROTON-168: -- Running cmake on OS X now results in: - Loo

[jira] [Commented] (PROTON-168) Support for building on OS X

[ https://issues.apache.org/jira/browse/PROTON-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505960#comment-13505960 ] Andrew Stitcher commented on PROTON-168: Note that the patch attached here doesn't

[jira] [Commented] (PROTON-168) Support for building on OS X

[ https://issues.apache.org/jira/browse/PROTON-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505958#comment-13505958 ] Andrew Stitcher commented on PROTON-168: I've made a couple of changes to the sour

[jira] [Resolved] (PROTON-22) Add optional module that provides HawtDispatch integration.

[ https://issues.apache.org/jira/browse/PROTON-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved PROTON-22. Resolution: Fixed Fix Version/s: 0.3 > Add optional module that provides HawtDispatch integration

[jira] [Resolved] (PROTON-65) Provide a AMQP 1.0 Message to JMS Message mapping logic/module

[ https://issues.apache.org/jira/browse/PROTON-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved PROTON-65. Resolution: Fixed Fix Version/s: 0.3 > Provide a AMQP 1.0 Message to JMS Message mapping logic/mo

amqp redirect scenario details

Over the last few weeks we have created a number of JIRAs related to SSL resumption and redirects etc. All of these allude to some master redirect scenario but the scenario itself perhaps wasn't clear. Hopefully this note should give folks some more context as to the motivation and details for this

Re: Unexpected behaviour in test ssl.py - possible bug?

Hi Ken, Thanks for looking into it. I've raised https://issues.apache.org/jira/browse/PROTON-171 and assigned it to you. Phil On Nov 28, 2012 6:19 PM, "Ken Giusti" wrote: > Hi Phil, > > I think you've uncovered a bug - definitely raise a jira and assign it to > me. > > Now that you mention it,

[jira] [Updated] (PROTON-171) after connection close, proton-c SSL decryption fails when left-over bytes passed to input()

[ https://issues.apache.org/jira/browse/PROTON-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Harvey updated PROTON-171: - Description: We've been working on the Java SSL implementation and are seeing a test fail agains

[jira] [Created] (PROTON-171) after connection close, proton-c SSL decryption fails when left-over bytes passed to input()

Philip Harvey created PROTON-171: Summary: after connection close, proton-c SSL decryption fails when left-over bytes passed to input() Key: PROTON-171 URL: https://issues.apache.org/jira/browse/PROTON-171

[jira] [Assigned] (PROTON-171) after connection close, proton-c SSL decryption fails when left-over bytes passed to input()

[ https://issues.apache.org/jira/browse/PROTON-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Harvey reassigned PROTON-171: Assignee: Ken Giusti > after connection close, proton-c SSL decryption fails when left-

[jira] [Commented] (PROTON-164) Messenger not handling connection errors properly

[ https://issues.apache.org/jira/browse/PROTON-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505782#comment-13505782 ] Rafael H. Schloming commented on PROTON-164: Is there a way for me to reproduc

Re: Unexpected behaviour in test ssl.py - possible bug?

Hi Phil, I think you've uncovered a bug - definitely raise a jira and assign it to me. Now that you mention it, I'm surprised that the original version of pump() worked properly - seems like it would risk discarding any output not consumed by the input handler.Your changes to pump() should

[jira] [Assigned] (PROTON-160) Allow open.hostname to be configured independently of network hostname

[ https://issues.apache.org/jira/browse/PROTON-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming reassigned PROTON-160: -- Assignee: Rafael H. Schloming > Allow open.hostname to be configured indepe

[jira] [Commented] (PROTON-160) Allow open.hostname to be configured independently of network hostname

[ https://issues.apache.org/jira/browse/PROTON-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505715#comment-13505715 ] Rafael H. Schloming commented on PROTON-160: Ok, thanks for wading through my

[jira] [Commented] (PROTON-160) Allow open.hostname to be configured independently of network hostname

[ https://issues.apache.org/jira/browse/PROTON-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505706#comment-13505706 ] Affan Dar commented on PROTON-160: -- I think the assumption behind option (1) was that add

Unexpected behaviour in test ssl.py - possible bug?

Hi, We've been working on the Java SSL implementation and are seeing a test fail against proton-c but that works against proton-j. We're not sure if the problem is in proton-c, or in our modified test, and are hoping someone who knows about proton-c's SSL implementation can give a view on this be

[jira] [Updated] (PROTON-170) generated pkg config file doesn't actually include paths if a different install location is used

[ https://issues.apache.org/jira/browse/PROTON-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated PROTON-170: -- Attachment: PROTON-170.patch This alters the template for the pkgconfig file such that the correct (at

[jira] [Assigned] (PROTON-170) generated pkg config file doesn't actually include paths if a different install location is used

[ https://issues.apache.org/jira/browse/PROTON-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned PROTON-170: - Assignee: Andrew Stitcher Andrew, requesting review from someone more expert in cmake and pkgconf

[jira] [Created] (PROTON-170) generated pkg config file doesn't actually include paths if a different install location is used

Gordon Sim created PROTON-170: - Summary: generated pkg config file doesn't actually include paths if a different install location is used Key: PROTON-170 URL: https://issues.apache.org/jira/browse/PROTON-170

[jira] [Comment Edited] (PROTON-154) link attach, detach, attach sequence on single session does not result in a new link for the 2nd attach

[ https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505576#comment-13505576 ] Hiram Chirino edited comment on PROTON-154 at 11/28/12 3:50 PM:

[jira] [Commented] (PROTON-154) link attach, detach, attach sequence on single session does not result in a new link for the 2nd attach

[ https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505576#comment-13505576 ] Hiram Chirino commented on PROTON-154: -- Hi Rafael, that's a different issue. See PRO

[jira] [Assigned] (PROTON-169) Provide examples using web application frameworks

[ https://issues.apache.org/jira/browse/PROTON-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce reassigned PROTON-169: --- Assignee: Darryl L. Pierce > Provide examples using web application frameworks >

[jira] [Created] (PROTON-169) Provide examples using web application frameworks

Darryl L. Pierce created PROTON-169: --- Summary: Provide examples using web application frameworks Key: PROTON-169 URL: https://issues.apache.org/jira/browse/PROTON-169 Project: Qpid Proton I

[jira] [Commented] (PROTON-154) link attach, detach, attach sequence on single session does not result in a new link for the 2nd attach

[ https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505485#comment-13505485 ] Rafael H. Schloming commented on PROTON-154: I'm a little confused by the clos

[jira] [Commented] (PROTON-160) Allow open.hostname to be configured independently of network hostname

[ https://issues.apache.org/jira/browse/PROTON-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505441#comment-13505441 ] Rafael H. Schloming commented on PROTON-160: I was assuming auto-redirect was

[jira] [Commented] (PROTON-160) Allow open.hostname to be configured independently of network hostname

[ https://issues.apache.org/jira/browse/PROTON-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505408#comment-13505408 ] Gordon Sim commented on PROTON-160: --- I greatly prefer option (3) as outlined at the end

[jira] [Updated] (PROTON-154) link attach, detach, attach sequence on single session does not result in a new link for the 2nd attach

[ https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-154: - Attachment: PROTON-154-test.patch Attaching test case to demonstrates the error.

[jira] [Updated] (PROTON-154) link attach, detach, attach sequence on single session does not result in a new link for the 2nd attach

[ https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-154: - Component/s: proton-c > link attach, detach, attach sequence on single session does not resul

[jira] [Commented] (PROTON-154) link attach, detach, attach sequence on single session does not result in a new link for the 2nd attach

[ https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505388#comment-13505388 ] Hiram Chirino commented on PROTON-154: -- Python test case also verifies that this bug