onnection.
>
> --Rafael
>
>
> On Fri, Feb 7, 2014 at 8:26 AM, Ken Giusti wrote:
>
> > Thanks Tomáš - I agree with a single per-messenger timeout approach.
> >
> >
> > - Original Message -
> > > From: "Tomáš Šoltys"
> >
[
https://issues.apache.org/jira/browse/PROTON-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894504#comment-13894504
]
Ken Giusti commented on PROTON-512:
---
As suggested by Tomas, I agree that it would
new JIRA as you suggested.
> https://issues.apache.org/jira/browse/PROTON-512
>
> My idea is that there would be one global idle timeout for whole messenger
> and this timeout will be used for all connections.
>
> Regards,
> Tomas
>
>
> 2013-11-11 Ken Giusti :
>
&g
Actually, I seem to remember ubunutu providing uuid in the e2fsprogs package.
Struck me as odd at the time...
- Original Message -
> From: "Justin Ross"
> To: proton@qpid.apache.org
> Sent: Wednesday, February 5, 2014 12:08:48 PM
> Subject: Re: error when building proton
>
> Watch out.
Ken Giusti created PROTON-507:
-
Summary: [proton-c] Idle time out should advertise half the actual
timeout period.
Key: PROTON-507
URL: https://issues.apache.org/jira/browse/PROTON-507
Project: Qpid
Ken Giusti created PROTON-500:
-
Summary: [proton-c] Enable valgrind on C unit tests
Key: PROTON-500
URL: https://issues.apache.org/jira/browse/PROTON-500
Project: Qpid Proton
Issue Type: Test
Just FYI: I changed the VALGRIND environment variable used by the proton
testbed to be compatible with the way the QPID testbed uses it:
https://issues.apache.org/jira/browse/PROTON-498
Shouldn't cause any problems, but if you do start seeing "command not found"
errors after updating your repo
Ken Giusti created PROTON-498:
-
Summary: Set VALGRIND environment variable to be compatible with
the QPID build
Key: PROTON-498
URL: https://issues.apache.org/jira/browse/PROTON-498
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882918#comment-13882918
]
Ken Giusti commented on PROTON-496:
---
True, but shouldn't Messenger be a &quo
[
https://issues.apache.org/jira/browse/PROTON-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated PROTON-496:
--
Priority: Trivial (was: Major)
> [Messenger] Messenger fails to send "end"
[
https://issues.apache.org/jira/browse/PROTON-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated PROTON-496:
--
Issue Type: Improvement (was: Bug)
> [Messenger] Messenger fails to send "end"
[
https://issues.apache.org/jira/browse/PROTON-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti reassigned PROTON-496:
-
Assignee: Ken Giusti
> [Messenger] Messenger fails to send "end"
Ken Giusti created PROTON-496:
-
Summary: [Messenger] Messenger fails to send "end" on shutdown.
Key: PROTON-496
URL: https://issues.apache.org/jira/browse/PROTON-496
Project: Qpid Proton
Hi Saggi
Sounds like you need to handle all the socket i/o directly, rather than having
Proton do it "under the covers", right?
To do this, you'll need to avoid using the Driver and Connector and Listener
classes from the Python binding - these classes perform all socket management
and I/O, fo
Ken Giusti created PROTON-490:
-
Summary: [proton-c] Python binding fails to link with Python 3
libraries
Key: PROTON-490
URL: https://issues.apache.org/jira/browse/PROTON-490
Project: Qpid Proton
Hey Rafi -
This model is exactly what I've been looking for. When it comes to using the
engine, I've found myself needing the same boilerplate code across different
implementation languages. It would really be nice to have this stuff in the
engine, where it can be utilized by all.
Just FYI,
Ken Giusti created PROTON-489:
-
Summary: [proton-c] Segfault when freeing endpoints out-of-order.
Key: PROTON-489
URL: https://issues.apache.org/jira/browse/PROTON-489
Project: Qpid Proton
Issue
[
https://issues.apache.org/jira/browse/PROTON-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated PROTON-487:
--
Attachment: proton-487.patch
This patch removes the reference cycle so objects can be garbage
Ken Giusti created PROTON-487:
-
Summary: [proton-c] Python binding leaks endpoint and delivery
objects
Key: PROTON-487
URL: https://issues.apache.org/jira/browse/PROTON-487
Project: Qpid Proton
[X] Yes, release 0.6 RC3 as 0.6 final
[ ] No, 0.6 RC3 has the following issues...
Built, unit test, install, and soak tests all worked fine on my Centos 5.10
i686 VM.
The only troubling bit with this release is that my messenger benchmark [1]
showed a bit of a degrade in small message latency
Sorry for top-posting. I'm trying to understand the consequences of what you
are proposing.
First, as I understand it, there are two separate test suites in the proton
tree: one written in Java - containing 19 tests as you point out - and a much
larger one written in python. Each test suite e
[
https://issues.apache.org/jira/browse/PROTON-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved PROTON-481.
---
Resolution: Fixed
> [python] link name is not availa
Ken Giusti created PROTON-481:
-
Summary: [python] link name is not available
Key: PROTON-481
URL: https://issues.apache.org/jira/browse/PROTON-481
Project: Qpid Proton
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PROTON-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti reassigned PROTON-481:
-
Assignee: Ken Giusti
> [python] link name is not availa
[
https://issues.apache.org/jira/browse/PROTON-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved PROTON-477.
---
Resolution: Fixed
> [python] Proton wrapper API does not enforce SASL or SSL singleton patt
Ken Giusti created PROTON-477:
-
Summary: [python] Proton wrapper API does not enforce SASL or SSL
singleton pattern
Key: PROTON-477
URL: https://issues.apache.org/jira/browse/PROTON-477
Project: Qpid
- Original Message -
> From: "Rafael Schloming"
> To: proton@qpid.apache.org
> Cc: us...@qpid.apache.org
> Sent: Wednesday, December 11, 2013 9:43:59 AM
> Subject: Re: Python wrapper - SASL and SSL class API
>
> On Wed, Dec 11, 2013 at 9:35 AM, Ken G
Hi all - just wanted to get some opinions on $Subject:
While I was trying to implement a fix for
https://issues.apache.org/jira/browse/PROTON-476 I found that the lifecycle
model for the python SASL and SSL objects differs for the C engine. I think
the python wrapper's impl is buggy.
In the
[
https://issues.apache.org/jira/browse/PROTON-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved PROTON-475.
---
Resolution: Fixed
> [python] Proton wrapper API's use of time values is inco
Ken Giusti created PROTON-476:
-
Summary: Support a user-context for SASL and SSL objects.
Key: PROTON-476
URL: https://issues.apache.org/jira/browse/PROTON-476
Project: Qpid Proton
Issue Type
Ken Giusti created PROTON-475:
-
Summary: [python] Proton wrapper API's use of time values is
inconsistent
Key: PROTON-475
URL: https://issues.apache.org/jira/browse/PROTON-475
Project: Qpid P
[
https://issues.apache.org/jira/browse/PROTON-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated PROTON-200:
--
Component/s: proton-c
Summary: Credit distribution by messenger is not balanced across all
> >
> > Key: PROTON-200
> > URL: https://issues.apache.org/jira/browse/PROTON-200
> > Project: Qpid Proton
> > Issue Type: Bug
> > Components: proton-j
> >Affects Versions: 0.3
> >
[
https://issues.apache.org/jira/browse/PROTON-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved PROTON-200.
---
Resolution: Fixed
> [Proton-c] Credit distribution by messenger is not balanced across all li
Ken Giusti created PROTON-462:
-
Summary: Documentation: Add doxygen overview file for Proton C API
Key: PROTON-462
URL: https://issues.apache.org/jira/browse/PROTON-462
Project: Qpid Proton
Ken Giusti created PROTON-453:
-
Summary: OpenSSL libraries are not Valgrind clean
Key: PROTON-453
URL: https://issues.apache.org/jira/browse/PROTON-453
Project: Qpid Proton
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PROTON-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved PROTON-449.
---
Resolution: Fixed
Fix Version/s: 0.6
> Unit tests fail if proton is built without Open
t
>
No - not at present. Messenger doesn't give the application access to the
transport since Messenger hides all that connection-related stuff.
I'd recommend opening a JIRA requesting this feature so we won't forget about
it.
https://issues.apache.org/jira/browse/PROTON
[
https://issues.apache.org/jira/browse/PROTON-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved PROTON-444.
---
Resolution: Fixed
> Java Messenger needs internal st
Hi Tomas,
The C implementation of proton allows you to set an idle time out for a
connection as described in the AMQP 1.0 spec. This value is used to generate
"null" frames (ie. frames with no bodies) on idle connections as to not expire
the timeout. The connection will be dropped if the loc
Ken Giusti created PROTON-449:
-
Summary: Unit tests fail if proton is built without OpenSSL.
Key: PROTON-449
URL: https://issues.apache.org/jira/browse/PROTON-449
Project: Qpid Proton
Issue Type
[
https://issues.apache.org/jira/browse/PROTON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti reassigned PROTON-401:
-
Assignee: Rafael H. Schloming (was: Ken Giusti)
For Rafi's consideration.
> Orderi
[
https://issues.apache.org/jira/browse/PROTON-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved PROTON-446.
---
Resolution: Fixed
Fix Version/s: 0.6
> [SSL] when certificate validation fails,
Ken Giusti created PROTON-446:
-
Summary: [SSL] when certificate validation fails, the connection
is not cleanly closed.
Key: PROTON-446
URL: https://issues.apache.org/jira/browse/PROTON-446
Project: Qpid
[
https://issues.apache.org/jira/browse/PROTON-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti closed PROTON-426.
-
See QPID-5251
> [Messenger] messenger has no ability to dynamically create queues/topics on
>
Hi Rafi,
I'd like to get PROTON-200 finished for 0.6, which involves porting the
algorithm in the C implementation of Messenger to the Java implementation.
This port is dependent on PROTON-444, so I'd like to include that in 0.6 also.
Ok?
-K
- Original Message -
> From: "Rafael Schlo
Ken Giusti created PROTON-444:
-
Summary: Java Messenger needs internal store.
Key: PROTON-444
URL: https://issues.apache.org/jira/browse/PROTON-444
Project: Qpid Proton
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/PROTON-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated PROTON-200:
--
Fix Version/s: 0.6
> [Proton-c] Credit distribution by messenger is not balanced across all li
[
https://issues.apache.org/jira/browse/PROTON-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated PROTON-200:
--
Component/s: (was: proton-c)
proton-j
> [Proton-c] Credit distribution
[
https://issues.apache.org/jira/browse/PROTON-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti reassigned PROTON-302:
-
Assignee: Ken Giusti (was: Rafael H. Schloming)
> Messenger does not verify the hostname in
[
https://issues.apache.org/jira/browse/PROTON-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti reopened PROTON-200:
---
Java Messenger is missing this functionality.
> [Proton-c] Credit distribution by messenger is
[
https://issues.apache.org/jira/browse/PROTON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781811#comment-13781811
]
Ken Giusti commented on PROTON-401:
---
I see your point - I'll update the P
Ken Giusti created PROTON-426:
-
Summary: [Messenger] messenger has no ability to dynamically
create queues/topics on qpidd
Key: PROTON-426
URL: https://issues.apache.org/jira/browse/PROTON-426
Project
Ken Giusti created PROTON-425:
-
Summary: [Messenger] messenger can only browse qpidd's queues
Key: PROTON-425
URL: https://issues.apache.org/jira/browse/PROTON-425
Project: Qpid Proton
Ken Giusti created PROTON-410:
-
Summary: Remove driver dependencies in Messenger to allow the
application to manage I/O
Key: PROTON-410
URL: https://issues.apache.org/jira/browse/PROTON-410
Project: Qpid
[
https://issues.apache.org/jira/browse/PROTON-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746513#comment-13746513
]
Ken Giusti commented on PROTON-375:
---
Reviewboard link:
https://reviews.apache.o
[
https://issues.apache.org/jira/browse/PROTON-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti reassigned PROTON-375:
-
Assignee: Ken Giusti
> Engine does not indicate when a link has completed drain
[
https://issues.apache.org/jira/browse/PROTON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti reassigned PROTON-401:
-
Assignee: Ken Giusti
> Ordering issue prevents credit drain from working prope
[
https://issues.apache.org/jira/browse/PROTON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746509#comment-13746509
]
Ken Giusti commented on PROTON-401:
---
Reviewboard link:
https://reviews.apache.o
[
https://issues.apache.org/jira/browse/PROTON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated PROTON-401:
--
Attachment: drain-hack.patch
Attached drain-hack.patch.
This is a hack I've used to work aroun
[
https://issues.apache.org/jira/browse/PROTON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated PROTON-401:
--
Attachment: drain-error.patch
A python test that highlights the problem.
Turn on frame tracing first
Ken Giusti created PROTON-401:
-
Summary: Ordering issue prevents credit drain from working properly
Key: PROTON-401
URL: https://issues.apache.org/jira/browse/PROTON-401
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved PROTON-396.
---
Resolution: Fixed
Fix Version/s: 0.5
Applied Hiram's patch.
>
[
https://issues.apache.org/jira/browse/PROTON-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti reassigned PROTON-302:
-
Assignee: Ken Giusti (was: Rafael H. Schloming)
> Messenger does not verify the hostname
[
https://issues.apache.org/jira/browse/PROTON-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti reassigned PROTON-396:
-
Assignee: Ken Giusti
> Proton Messenger should configure the SNI headers on it&#x
[
https://issues.apache.org/jira/browse/PROTON-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated PROTON-394:
--
Attachment: fleabag.patch
The fleabag.patch adds a python engine test that will throw an exception
Ken Giusti created PROTON-394:
-
Summary: Exhausting credit on a link can affect other links using
the same session.
Key: PROTON-394
URL: https://issues.apache.org/jira/browse/PROTON-394
Project: Qpid
Ken Giusti created PROTON-388:
-
Summary: Messenger lacks trace/debug logging
Key: PROTON-388
URL: https://issues.apache.org/jira/browse/PROTON-388
Project: Qpid Proton
Issue Type: New Feature
We are planning on creating an 0.5 branch at some point, correct?
I ask as we've branched all preceding releases - I'd expect the same for 0.5.
thanks,
-K
- Original Message -
> From: "Rafael Schloming"
> To: proton@qpid.apache.org
> Sent: Tuesday, August 6, 2013 6:38:11 AM
> Subject:
[
https://issues.apache.org/jira/browse/PROTON-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved PROTON-387.
---
Resolution: Fixed
> Linked list utility code leaves dangling pointers in removed n
Ken Giusti created PROTON-387:
-
Summary: Linked list utility code leaves dangling pointers in
removed node.
Key: PROTON-387
URL: https://issues.apache.org/jira/browse/PROTON-387
Project: Qpid Proton
Ken Giusti created PROTON-375:
-
Summary: Engine does not indicate when a link has completed
draining.
Key: PROTON-375
URL: https://issues.apache.org/jira/browse/PROTON-375
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti reassigned PROTON-350:
-
Assignee: Ken Giusti
> Messenger - pn_messenger_recv( -1 ) does not flow control send
H Yarek,
You're correct- the PHP bindings have not been kept up to date with the C API.
I've opened a bug report to track this:
https://issues.apache.org/jira/browse/PROTON-365
-K
- Original Message -
> From: "Yarek Tyshchenko"
> To: proton@qpid.apache.org
> Sent: Thursday, July 25,
Ken Giusti created PROTON-365:
-
Summary: PHP bindings are missing the disposition API calls
Key: PROTON-365
URL: https://issues.apache.org/jira/browse/PROTON-365
Project: Qpid Proton
Issue Type
Hi,
>From your output it appears that the SWIG tool is not available on your system:
-- SWIG was not found. Please specify Swig executable location
swig is used to generate the PHP bindings, so you'll need to install swig, then
re-run cmake to re-generate your makefiles.
For more info on swi
[
https://issues.apache.org/jira/browse/PROTON-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated PROTON-350:
--
Attachment: test-recv.py
Run test-recv.py and send messages to it. The number of messages queued
Ken Giusti created PROTON-350:
-
Summary: Messenger - pn_messenger_recv( -1 ) does not flow control
senders
Key: PROTON-350
URL: https://issues.apache.org/jira/browse/PROTON-350
Project: Qpid Proton
Hi Rafi, see inline:
- Original Message -
> From: "Rafael Schloming"
> To: proton@qpid.apache.org
> Sent: Wednesday, July 10, 2013 12:38:21 PM
> Subject: Re: Q: how to drain a link (via the engine api)
>
> On Wed, Jul 10, 2013 at 11:59 AM, Ken Giusti wrote:
Hi,
AMQP 1.0 defines a way to force a sending link to exhaust its credit via a
drain flag in the Flow frame (see the flow control section in the spec).
Hate to admit my ignorance, but how does one properly drain a link using the
Proton engine api?
>From what I can tell (using the proton-c api
[
https://issues.apache.org/jira/browse/PROTON-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved PROTON-81.
--
Resolution: Fixed
> Expose send/receive settle mo
[
https://issues.apache.org/jira/browse/PROTON-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved PROTON-139.
---
Resolution: Fixed
> Can't set distribution-mode on
[
https://issues.apache.org/jira/browse/PROTON-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved PROTON-277.
---
Resolution: Fixed
> dynamic flag on source/target is not handled correc
[
https://issues.apache.org/jira/browse/PROTON-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti reassigned PROTON-81:
Assignee: Ken Giusti
> Expose send/receive settle mo
[
https://issues.apache.org/jira/browse/PROTON-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti reassigned PROTON-277:
-
Assignee: Ken Giusti
> dynamic flag on source/target is not handled correc
Ken Giusti created PROTON-345:
-
Summary: Need a Java version of the msgr-send/msgr-recv tools
Key: PROTON-345
URL: https://issues.apache.org/jira/browse/PROTON-345
Project: Qpid Proton
Issue
Ken Giusti created PROTON-344:
-
Summary: Need Ruby version of msgr-send/msgr-recv tools
Key: PROTON-344
URL: https://issues.apache.org/jira/browse/PROTON-344
Project: Qpid Proton
Issue Type
[
https://issues.apache.org/jira/browse/PROTON-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti reassigned PROTON-139:
-
Assignee: Ken Giusti (was: Rafael H. Schloming)
> Can't set distribution-mode on
[
https://issues.apache.org/jira/browse/PROTON-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti reassigned PROTON-158:
-
Assignee: Ken Giusti
> detach with invalid handle causes segfa
[
https://issues.apache.org/jira/browse/PROTON-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689425#comment-13689425
]
Ken Giusti commented on PROTON-109:
---
Review board for proton-c patch:
h
Excellent news - good to hear, thanks!
- Original Message -
> From: "atarutin"
> To: proton@qpid.apache.org
> Sent: Wednesday, June 12, 2013 6:29:15 AM
> Subject: Re: Does Messenger API supports SSL?
>
> Ken, thank you for help. Your answers made me think about problems with
> properly s
The server isn't following through with the rest of the handshake, but I can't
tell why from the dump, sorry.
When you do this (run openssl s_client), does the broker log anything?
BTW, what version OpenSSL are you running on the client side? "openssl
version" will give you that.
thanks,
-
It doesn't appear that an SSL handshake is being done. Can you add a '-debug'
to get a raw trace of the protocol? Is the server responding at all?
For example, when I run openssl s_client against my server, I see the
certificate exchange. I would expect the same for your server - you should s
Hi,
Although I've never seen this error before, I suspect that the server requires
some stronger level of encryption than the client is providing. This may
depend on several factors, including what ciphers your server and your OpenSSL
library support (client).
You may want to try the openss
Ken Giusti created PROTON-309:
-
Summary: Messenger crashes if given a message that lacks a "to"
address
Key: PROTON-309
URL: https://issues.apache.org/jira/browse/PROTON-309
Project: Q
Ken Giusti created PROTON-303:
-
Summary: Need an easy to use Map handling API
Key: PROTON-303
URL: https://issues.apache.org/jira/browse/PROTON-303
Project: Qpid Proton
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/PROTON-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved PROTON-301.
---
Resolution: Won't Fix
Not feasible due to the overwhelming number of valgrind errors produced b
[
https://issues.apache.org/jira/browse/PROTON-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642906#comment-13642906
]
Ken Giusti commented on PROTON-301:
---
I'm giving up on this. While I still thi
[
https://issues.apache.org/jira/browse/PROTON-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640515#comment-13640515
]
Ken Giusti commented on PROTON-302:
---
To fix this:
In messenger::pn_transport_co
Ken Giusti created PROTON-302:
-
Summary: Messenger does not verify the hostname in the peer's SSL
certificate.
Key: PROTON-302
URL: https://issues.apache.org/jira/browse/PROTON-302
Project: Qpid P
301 - 400 of 602 matches
Mail list logo
