[jira] [Created] (DISPATCH-1318) edge_router system test failing - timeout with n_sent too big
Chuck Rolke created DISPATCH-1318:
-
Summary: edge_router system test failing - timeout with n_sent too
big
Key: DISPATCH-1318
URL: https://issues.apache.org/jira/browse/DISPATCH-1318
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.6.0
Reporter: Chuck Rolke
Assignee: Chuck Rolke
{quote}{{0:
==}}
{{50: FAIL: test_22_mobile_address_edge_sender_two_interior_receivers
(system_tests_edge_router.RouterTest)}}
{{50: --}}
{{50: Traceback (most recent call last):}}
{{50: File "/home/chug/git/qpid-dispatch/tests/system_tests_edge_router.py",
line 451, in test_22_mobile_address_edge_sender_two_interior_receivers}}
{{50: self.assertEqual(None, test.error)}}
{{50: AssertionError: None != 'Timeout Expired - n_sent=350 n_rcvd=300 [36
chars]t_22'}}
{{50: }}
{{50: --}}
{{50: Ran 48 tests in 84.066s}}
{{50: }}
{{50: FAILED (failures=1)}}
{{1/1 Test #50: system_tests_edge_router .***Failed 84.37 sec}}{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1309) Various crashes in 1.6 release
[
https://issues.apache.org/jira/browse/DISPATCH-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815668#comment-16815668
]
ASF subversion and git services commented on DISPATCH-1309:
---
Commit 67e8ef6f10a4a3b2f92f39aa63f9aa0f5180 in qpid-dispatch's branch
refs/heads/master from Ted Ross
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=67e8ef6 ]
DISPATCH-1309 - Convert the delivery->link pointer to a safe pointer.
> Various crashes in 1.6 release
> --
>
> Key: DISPATCH-1309
> URL: https://issues.apache.org/jira/browse/DISPATCH-1309
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.6.0
> Environment: System 'unused':(
> Fedora 5.0.3-200.fc29.x86_64,
> Python 2.7.15,
> Proton master @ eab1f.
> System 'taj':(
> Fedora 4.18.16-200.fc28.x86_64,
> Python 3.6.6,
> Proton master @ 68b38
>Reporter: Chuck Rolke
>Priority: Major
> Attachments: DISPATCH-1309-backtraces.txt,
> DISPATCH-1309-gen_configs_linear.py
>
>
> qpid-dispatch master @ 51244, which is very close to the 1.6 release, has
> various crashes.
> The test network is 12 routers spread over two systems. (Configuration
> generator to be attached.) Four interior routers are in linear arrangement
> with A and C on one system ('unused'), and B and D on the other system
> ('taj'). Each system then attaches four edge routers, one to each interior
> router.
> Running lightweight tests, like proton cpp simple_send and simple_recv to
> ports on INTA and INTB interior routers leads to a crash on INTC. The crashes
> typically look like reuse of structures after they have been freed (addresses
> are 0x). Other crashes hint of general memory corruption
> (crashes in malloc.c).
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2017) [go] fix proton-c version check
[ https://issues.apache.org/jira/browse/PROTON-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815626#comment-16815626 ] ASF subversion and git services commented on PROTON-2017: - Commit 49ded1fb5a458cd73391b2af739231bfa4dad354 in qpid-proton's branch refs/heads/0.27.x from Alan Conway [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=49ded1f ] PROTON-2017: [go] fix proton-c version check (cherry picked from commit ae3af505020b76c0027d068cc4139857d5521135) > [go] fix proton-c version check > --- > > Key: PROTON-2017 > URL: https://issues.apache.org/jira/browse/PROTON-2017 > Project: Qpid Proton > Issue Type: Bug >Affects Versions: proton-c-0.27.0 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Major > Fix For: proton-c-0.27.1 > > > amqp/version.go checks for proton-c library version >= 0.10, it works with > all subsequent versions. > in the 0.27 release this was modified to 0.27 which breaks the go binding > with existing proton-c installations. > Fix on master and go1 release branch. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2018) [c] Test SSL without python bindings
[ https://issues.apache.org/jira/browse/PROTON-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815628#comment-16815628 ] ASF subversion and git services commented on PROTON-2018: - Commit 1b2c2ec755d7cba9f7f94cde76bd11d59f146b24 in qpid-proton's branch refs/heads/0.27.x from Andrew Stitcher [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=1b2c2ec ] PROTON-2018: [c] Introduce some ssl protocol tests (cherry picked from commit 2e7b4027ae63471b95d0f2a829a798d3329b395a) > [c] Test SSL without python bindings > > > Key: PROTON-2018 > URL: https://issues.apache.org/jira/browse/PROTON-2018 > Project: Qpid Proton > Issue Type: Task >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.27.1, proton-c-0.28.0 > > > Much of the testing of the proton-c API is only possible using the Python > binding. It would be much better if every area of the API could be tested > using tests that onyl require C. > The only testing for SSL connections and data transfer is via the Python > binding and it would be vastly preferable to be able to do this purely in C. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2014) [c] Example broker can silently use anonymous ciphers when misconfigured
[
https://issues.apache.org/jira/browse/PROTON-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815629#comment-16815629
]
ASF subversion and git services commented on PROTON-2014:
-
Commit 4aea0fd8502f5e9af7f22fd60645eeec07bce0b2 in qpid-proton's branch
refs/heads/0.27.x from Andrew Stitcher
[ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=4aea0fd ]
PROTON-2014: [c] Ensure SSL mutual authentication
(cherry picked from commit 97c7733f07712665f3d08091c82c393e4c3adbf7)
> [c] Example broker can silently use anonymous ciphers when misconfigured
>
>
> Key: PROTON-2014
> URL: https://issues.apache.org/jira/browse/PROTON-2014
> Project: Qpid Proton
> Issue Type: Bug
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.27.1, proton-c-0.28.0
>
>
> The example broker does not check the return value from
> {color:#2e3436}pn_ssl_domain_set_credentials(){color} and if given a bad
> certificate will allow anonymous ciphers without even displaying an error
> message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2006) Service Bus example doesnt work
[
https://issues.apache.org/jira/browse/PROTON-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815631#comment-16815631
]
ASF subversion and git services commented on PROTON-2006:
-
Commit 37e6a68de7dce46dcec13ca00415bb169934b747 in qpid-proton's branch
refs/heads/0.27.x from Andrew Stitcher
[ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=37e6a68 ]
PROTON-2006: [C++] Fixed up service bus example to work
- Connection options needed fixing
-- You can't put user/password in the connection url anymore
-- Need to turn SSL on and ensure SASL mech is PLAIN
- Misuse of scheduling stopped the application exiting when finished
(cherry picked from commit eab1fef19b4e58a8b79408f29e10fe36b07a3b83)
> Service Bus example doesnt work
> ---
>
> Key: PROTON-2006
> URL: https://issues.apache.org/jira/browse/PROTON-2006
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding, examples
>Affects Versions: proton-c-0.27.0
>Reporter: Oskar Christensson
>Assignee: Andrew Stitcher
>Priority: Minor
> Fix For: proton-c-0.27.1, proton-c-0.28.0
>
>
>
> {code:java}
> amqp:connection:framing-error: SASL header mismatch: Insufficient data to
> determine protocol [''] (connection aborted){code}
> We're trying to get a C++ connection to Azure Service Bus using AMQP with
> QPID proton, and trying out the examples under qpid-proton/cpp/examples it
> fails.
> Steps to reproduce:
> # Clone qpid-proton
> # Follow installation and make README
> # Create new Service Bus Namespace in azure
> # Create new Service Bus Queue in Azure with Sessions enabled
> # Create a policy with all permissions
> # `./service_bus -n .servicebus.windows.net -p -k
> -e
> Expected results:
> It should work according to the docs in the cpp/examples/service_bus.cpp docs
> Actual results:
> {code:java}
> amqp:connection:framing-error: SASL header mismatch: Insufficient data to
> determine protocol [''] (connection aborted){code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2027) Proactor connection wake after memory freed when using pn_proactor_disconnect().
[ https://issues.apache.org/jira/browse/PROTON-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815633#comment-16815633 ] ASF subversion and git services commented on PROTON-2027: - Commit 8a84224cc79377b09bed59a33d1d11b641b45505 in qpid-proton's branch refs/heads/0.27.x from Clifford Jansen [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=8a84224 ] PROTON-2027: Test case with two closing connection contexts competing with a third context in pn_proactor_disconnect(). (cherry picked from commit f973528912b3b74e8d1e50317429e202e9f51ec4) > Proactor connection wake after memory freed when using > pn_proactor_disconnect(). > > > Key: PROTON-2027 > URL: https://issues.apache.org/jira/browse/PROTON-2027 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.27.0 >Reporter: Cliff Jansen >Assignee: Cliff Jansen >Priority: Major > Fix For: proton-c-0.27.1, proton-c-0.28.0 > > > The normal cleanup procedure for epoll and win_iocp proactors waits for all > async activity to complete before freeing memory. > pn_proactor_disconnect can't actually force a close so it launches a separate > async activity piggy-backed on the internal wake mechanism of any connections > to be closed. > If the disconnect is happening at the same time as a separate thread doing a > normal close, a new wake can result after concluding there are none left. > The solution is to mark the connection as "already awake" before entering the > cleanup code so new wakes are no-ops. The libuv proactor doesn't need this > as the disconnect function is managed within libuv and never competes with > the normal close operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2014) [c] Example broker can silently use anonymous ciphers when misconfigured
[
https://issues.apache.org/jira/browse/PROTON-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815630#comment-16815630
]
ASF subversion and git services commented on PROTON-2014:
-
Commit 2d3ba8aadc6657410a9e9f020c4d371cb41cd41b in qpid-proton's branch
refs/heads/0.27.x from Andrew Stitcher
[ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=2d3ba8a ]
PROTON-2014: [c] Fix example broker to warn when it fails to set up ssl
- Also make send-ssl tell you the remote peer
(cherry picked from commit 159fac1f90d9b1ace1138d510176e7a5da54e9e9)
> [c] Example broker can silently use anonymous ciphers when misconfigured
>
>
> Key: PROTON-2014
> URL: https://issues.apache.org/jira/browse/PROTON-2014
> Project: Qpid Proton
> Issue Type: Bug
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.27.1, proton-c-0.28.0
>
>
> The example broker does not check the return value from
> {color:#2e3436}pn_ssl_domain_set_credentials(){color} and if given a bad
> certificate will allow anonymous ciphers without even displaying an error
> message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2027) Proactor connection wake after memory freed when using pn_proactor_disconnect().
[ https://issues.apache.org/jira/browse/PROTON-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815632#comment-16815632 ] ASF subversion and git services commented on PROTON-2027: - Commit fdeddad3767dac5022df7dc966be6681293c173e in qpid-proton's branch refs/heads/0.27.x from Clifford Jansen [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=fdeddad ] PROTON-2027: Make disconnect work like other wake mechanisms (eg. pn_connection_wake) and check for closing status. Count disconnects correctly for competing closes. (cherry picked from commit d4a6971af2c64b7d9e8aa31a1e807690d4f26a7e) > Proactor connection wake after memory freed when using > pn_proactor_disconnect(). > > > Key: PROTON-2027 > URL: https://issues.apache.org/jira/browse/PROTON-2027 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.27.0 >Reporter: Cliff Jansen >Assignee: Cliff Jansen >Priority: Major > Fix For: proton-c-0.27.1, proton-c-0.28.0 > > > The normal cleanup procedure for epoll and win_iocp proactors waits for all > async activity to complete before freeing memory. > pn_proactor_disconnect can't actually force a close so it launches a separate > async activity piggy-backed on the internal wake mechanism of any connections > to be closed. > If the disconnect is happening at the same time as a separate thread doing a > normal close, a new wake can result after concluding there are none left. > The solution is to mark the connection as "already awake" before entering the > cleanup code so new wakes are no-ops. The libuv proactor doesn't need this > as the disconnect function is managed within libuv and never competes with > the normal close operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2027) Proactor connection wake after memory freed when using pn_proactor_disconnect().
[ https://issues.apache.org/jira/browse/PROTON-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815634#comment-16815634 ] ASF subversion and git services commented on PROTON-2027: - Commit 1b490b30954616e7c135929153b20337666a84b7 in qpid-proton's branch refs/heads/0.27.x from Clifford Jansen [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=1b490b3 ] PROTON-2027: use make_work instead of lambda for wider platform coverage (cherry picked from commit 5b6ed8e166c47922ee94502ac30a7d5c235a4406) > Proactor connection wake after memory freed when using > pn_proactor_disconnect(). > > > Key: PROTON-2027 > URL: https://issues.apache.org/jira/browse/PROTON-2027 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.27.0 >Reporter: Cliff Jansen >Assignee: Cliff Jansen >Priority: Major > Fix For: proton-c-0.27.1, proton-c-0.28.0 > > > The normal cleanup procedure for epoll and win_iocp proactors waits for all > async activity to complete before freeing memory. > pn_proactor_disconnect can't actually force a close so it launches a separate > async activity piggy-backed on the internal wake mechanism of any connections > to be closed. > If the disconnect is happening at the same time as a separate thread doing a > normal close, a new wake can result after concluding there are none left. > The solution is to mark the connection as "already awake" before entering the > cleanup code so new wakes are no-ops. The libuv proactor doesn't need this > as the disconnect function is managed within libuv and never competes with > the normal close operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2004) libressl compatibility
[ https://issues.apache.org/jira/browse/PROTON-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815627#comment-16815627 ] ASF subversion and git services commented on PROTON-2004: - Commit 3b6de8f825ca1829815735edd88056a072d7acbe in qpid-proton's branch refs/heads/0.27.x from Andrew Stitcher [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=3b6de8f ] PROTON-2004: [c] Allow Proton to compile with libressl (cherry picked from commit 87898b3d71aea5bfd9e4157d6da04071e1461339) > libressl compatibility > -- > > Key: PROTON-2004 > URL: https://issues.apache.org/jira/browse/PROTON-2004 > Project: Qpid Proton > Issue Type: Bug >Reporter: Matthew Weber >Priority: Minor > Fix For: proton-c-0.27.1, proton-c-0.28.0 > > > Similar to > [FreeRDP/FreeRDP#5049](https://github.com/FreeRDP/FreeRDP/issues/5049) > libressl has `#define OPENSSL_VERSION_NUMBER ` defined the same as > openssl 1.1.x which results in SSL_CTX_set_security_level() getting used. > This patch prevents SSL_CTX__security_level() from being used with > libressl. > > https://github.com/apache/qpid-proton/pull/175 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2027) Proactor connection wake after memory freed when using pn_proactor_disconnect().
[ https://issues.apache.org/jira/browse/PROTON-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2027: --- Fix Version/s: proton-c-0.27.1 > Proactor connection wake after memory freed when using > pn_proactor_disconnect(). > > > Key: PROTON-2027 > URL: https://issues.apache.org/jira/browse/PROTON-2027 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.27.0 >Reporter: Cliff Jansen >Assignee: Cliff Jansen >Priority: Major > Fix For: proton-c-0.27.1, proton-c-0.28.0 > > > The normal cleanup procedure for epoll and win_iocp proactors waits for all > async activity to complete before freeing memory. > pn_proactor_disconnect can't actually force a close so it launches a separate > async activity piggy-backed on the internal wake mechanism of any connections > to be closed. > If the disconnect is happening at the same time as a separate thread doing a > normal close, a new wake can result after concluding there are none left. > The solution is to mark the connection as "already awake" before entering the > cleanup code so new wakes are no-ops. The libuv proactor doesn't need this > as the disconnect function is managed within libuv and never competes with > the normal close operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2006) Service Bus example doesnt work
[
https://issues.apache.org/jira/browse/PROTON-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell reassigned PROTON-2006:
--
Assignee: Andrew Stitcher
Affects Version/s: (was: proton-c-0.28.0)
proton-c-0.27.0
Priority: Minor (was: Major)
Fix Version/s: proton-c-0.27.1
Summary: Service Bus example doesnt work (was: Qpid Proton
cannot connect to Azure Service Bus 'amqp:connection:framing-error')
> Service Bus example doesnt work
> ---
>
> Key: PROTON-2006
> URL: https://issues.apache.org/jira/browse/PROTON-2006
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding, examples
>Affects Versions: proton-c-0.27.0
>Reporter: Oskar Christensson
>Assignee: Andrew Stitcher
>Priority: Minor
> Fix For: proton-c-0.27.1, proton-c-0.28.0
>
>
>
> {code:java}
> amqp:connection:framing-error: SASL header mismatch: Insufficient data to
> determine protocol [''] (connection aborted){code}
> We're trying to get a C++ connection to Azure Service Bus using AMQP with
> QPID proton, and trying out the examples under qpid-proton/cpp/examples it
> fails.
> Steps to reproduce:
> # Clone qpid-proton
> # Follow installation and make README
> # Create new Service Bus Namespace in azure
> # Create new Service Bus Queue in Azure with Sessions enabled
> # Create a policy with all permissions
> # `./service_bus -n .servicebus.windows.net -p -k
> -e
> Expected results:
> It should work according to the docs in the cpp/examples/service_bus.cpp docs
> Actual results:
> {code:java}
> amqp:connection:framing-error: SASL header mismatch: Insufficient data to
> determine protocol [''] (connection aborted){code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2014) [c] Example broker can silently use anonymous ciphers when misconfigured
[
https://issues.apache.org/jira/browse/PROTON-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-2014:
---
Fix Version/s: proton-c-0.27.1
> [c] Example broker can silently use anonymous ciphers when misconfigured
>
>
> Key: PROTON-2014
> URL: https://issues.apache.org/jira/browse/PROTON-2014
> Project: Qpid Proton
> Issue Type: Bug
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.27.1, proton-c-0.28.0
>
>
> The example broker does not check the return value from
> {color:#2e3436}pn_ssl_domain_set_credentials(){color} and if given a bad
> certificate will allow anonymous ciphers without even displaying an error
> message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2018) [c] Test SSL without python bindings
[ https://issues.apache.org/jira/browse/PROTON-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-2018. Resolution: Fixed Fix Version/s: proton-c-0.27.1 > [c] Test SSL without python bindings > > > Key: PROTON-2018 > URL: https://issues.apache.org/jira/browse/PROTON-2018 > Project: Qpid Proton > Issue Type: Task >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.27.1, proton-c-0.28.0 > > > Much of the testing of the proton-c API is only possible using the Python > binding. It would be much better if every area of the API could be tested > using tests that onyl require C. > The only testing for SSL connections and data transfer is via the Python > binding and it would be vastly preferable to be able to do this purely in C. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2004) libressl compatibility
[ https://issues.apache.org/jira/browse/PROTON-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-2004. Resolution: Fixed Fix Version/s: proton-c-0.28.0 proton-c-0.27.1 > libressl compatibility > -- > > Key: PROTON-2004 > URL: https://issues.apache.org/jira/browse/PROTON-2004 > Project: Qpid Proton > Issue Type: Bug >Reporter: Matthew Weber >Priority: Minor > Fix For: proton-c-0.27.1, proton-c-0.28.0 > > > Similar to > [FreeRDP/FreeRDP#5049](https://github.com/FreeRDP/FreeRDP/issues/5049) > libressl has `#define OPENSSL_VERSION_NUMBER ` defined the same as > openssl 1.1.x which results in SSL_CTX_set_security_level() getting used. > This patch prevents SSL_CTX__security_level() from being used with > libressl. > > https://github.com/apache/qpid-proton/pull/175 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2017) [go] fix proton-c version check
[ https://issues.apache.org/jira/browse/PROTON-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2017: --- Fix Version/s: (was: proton-c-0.27.0) proton-c-0.27.1 > [go] fix proton-c version check > --- > > Key: PROTON-2017 > URL: https://issues.apache.org/jira/browse/PROTON-2017 > Project: Qpid Proton > Issue Type: Bug >Affects Versions: proton-c-0.27.0 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Major > Fix For: proton-c-0.27.1 > > > amqp/version.go checks for proton-c library version >= 0.10, it works with > all subsequent versions. > in the 0.27 release this was modified to 0.27 which breaks the go binding > with existing proton-c installations. > Fix on master and go1 release branch. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2010) [python] JSON connection config: comments and SASL mechs don't work
[ https://issues.apache.org/jira/browse/PROTON-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-2010. Resolution: Fixed > [python] JSON connection config: comments and SASL mechs don't work > --- > > Key: PROTON-2010 > URL: https://issues.apache.org/jira/browse/PROTON-2010 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: proton-c-0.27.1, proton-c-0.28.0 > > > If the JSON connection config file contains C/C++-style comments, or a list > of SASL mechanisms, then the client errors. > The JSON specification does not allow for comments. However, the connection > config file specifies that c/c++ comments may be embedded within the JSON. A > comment eliminator needs to be used before the JSON is loaded. > The call to pn_sasl_allowed_mechs() requires a const char* space-separated > list of SASL mechs. The python does not correctly handle this case, as it is > passing the mechs as a Python list of strings. A single string containing a > mech instead of a list in the JSON should also be handled. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2010) [python] JSON connection config: comments and SASL mechs don't work
[ https://issues.apache.org/jira/browse/PROTON-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2010: --- Fix Version/s: proton-c-0.28.0 proton-c-0.27.1 > [python] JSON connection config: comments and SASL mechs don't work > --- > > Key: PROTON-2010 > URL: https://issues.apache.org/jira/browse/PROTON-2010 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: proton-c-0.27.1, proton-c-0.28.0 > > > If the JSON connection config file contains C/C++-style comments, or a list > of SASL mechanisms, then the client errors. > The JSON specification does not allow for comments. However, the connection > config file specifies that c/c++ comments may be embedded within the JSON. A > comment eliminator needs to be used before the JSON is loaded. > The call to pn_sasl_allowed_mechs() requires a const char* space-separated > list of SASL mechs. The python does not correctly handle this case, as it is > passing the mechs as a Python list of strings. A single string containing a > mech instead of a list in the JSON should also be handled. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1989) TLS Configuration does not support TLSv1_3 in OpenSSL v1.1.1
[ https://issues.apache.org/jira/browse/PROTON-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1989: --- Fix Version/s: proton-c-0.27.1 > TLS Configuration does not support TLSv1_3 in OpenSSL v1.1.1 > > > Key: PROTON-1989 > URL: https://issues.apache.org/jira/browse/PROTON-1989 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.26.0 > Environment: Fedora 29, Python 2.7.15, OpenSSL 1.1.1 FIPS 11 Sep 2018 >Reporter: Chuck Rolke >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.27.1, proton-c-0.28.0 > > > OpenSSL 1.1.1 adds protocol version TLSv1_3. The current config interface has > no way to enable or disable that version. This was predicted in PROTON-1670. > The ssl self test tests the customer interface nicely but does not test that > the requested TLS versions used by the domain are enforced or not. > Qpid-dispatch has a self test that exercises actual connections > [https://github.com/apache/qpid-dispatch/blob/master/tests/system_tests_ssl.py] > and it is failing with OpenSSL v1.1.1. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2018) [c] Test SSL without python bindings
[ https://issues.apache.org/jira/browse/PROTON-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2018: --- Issue Type: Task (was: Improvement) > [c] Test SSL without python bindings > > > Key: PROTON-2018 > URL: https://issues.apache.org/jira/browse/PROTON-2018 > Project: Qpid Proton > Issue Type: Task >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.28.0 > > > Much of the testing of the proton-c API is only possible using the Python > binding. It would be much better if every area of the API could be tested > using tests that onyl require C. > The only testing for SSL connections and data transfer is via the Python > binding and it would be vastly preferable to be able to do this purely in C. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2018) [c] Test SSL without python bindings
[ https://issues.apache.org/jira/browse/PROTON-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2018: --- Fix Version/s: proton-c-0.28.0 > [c] Test SSL without python bindings > > > Key: PROTON-2018 > URL: https://issues.apache.org/jira/browse/PROTON-2018 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.28.0 > > > Much of the testing of the proton-c API is only possible using the Python > binding. It would be much better if every area of the API could be tested > using tests that onyl require C. > The only testing for SSL connections and data transfer is via the Python > binding and it would be vastly preferable to be able to do this purely in C. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2027) Proactor connection wake after memory freed when using pn_proactor_disconnect().
[ https://issues.apache.org/jira/browse/PROTON-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen resolved PROTON-2027. -- Resolution: Fixed Test also works now on CentOS 6 > Proactor connection wake after memory freed when using > pn_proactor_disconnect(). > > > Key: PROTON-2027 > URL: https://issues.apache.org/jira/browse/PROTON-2027 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.27.0 >Reporter: Cliff Jansen >Assignee: Cliff Jansen >Priority: Major > Fix For: proton-c-0.28.0 > > > The normal cleanup procedure for epoll and win_iocp proactors waits for all > async activity to complete before freeing memory. > pn_proactor_disconnect can't actually force a close so it launches a separate > async activity piggy-backed on the internal wake mechanism of any connections > to be closed. > If the disconnect is happening at the same time as a separate thread doing a > normal close, a new wake can result after concluding there are none left. > The solution is to mark the connection as "already awake" before entering the > cleanup code so new wakes are no-ops. The libuv proactor doesn't need this > as the disconnect function is managed within libuv and never competes with > the normal close operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
