[jira] [Commented] (DISPATCH-1086) Dispatch Router sporadically goes into a state where TLS connections to the auth service fail
[
https://issues.apache.org/jira/browse/DISPATCH-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16617739#comment-16617739
]
Carsten Lohmann commented on DISPATCH-1086:
---
We also got this issue.
Using the additional log information provided by PROTON-1886 (with PN_TRACE_DRV
set to 1), there was this log output:
{noformat}
[0x7feae80d4f30]:Client SSL socket created.
[0x7feaf0142120]:Client SSL socket created.
[0x7feae80d4f30]:Read 26 bytes from SSL socket for app
[0x7feae80d4f30]:SSL socket freed.
[0x7feaf0142120]:Read 26 bytes from SSL socket for app
[0x7feaf0142120]:SSL socket freed.
[0x7feaec0c4e60]:SSL socket setup failure.
[0x7feaec0c4e60]:error:140BA0E4:SSL routines:SSL_new:ssl ctx has no default ssl
version
2018-09-17 15:48:49.713040 + AUTHSERVICE (warning) Cannot initialise SSL
[0x7feaec0c4e60]:SSL socket setup failure.
[0x7feaec0c4e60]:error:140BA0E4:SSL routines:SSL_new:ssl ctx has no default ssl
version
[0x7feae805ea00]:SSL socket setup failure.
[0x7feae805ea00]:error:140BA0E4:SSL routines:SSL_new:ssl ctx has no default ssl
version
2018-09-17 15:48:49.713156 + AUTHSERVICE (warning) Cannot initialise SSL
[0x7feae805ea00]:SSL socket setup failure.
[0x7feae805ea00]:error:140BA0E4:SSL routines:SSL_new:ssl ctx has no default ssl
version
[0x7feae8116100]:SSL socket setup failure.
[0x7feae8116100]:error:140BA0E4:SSL routines:SSL_new:ssl ctx has no default ssl
version
2018-09-17 15:48:49.758598 + AUTHSERVICE (warning) Cannot initialise SSL
[0x7feae8116100]:SSL socket setup failure.
[0x7feae8116100]:error:140BA0E4:SSL routines:SSL_new:ssl ctx has no default ssl
version
[0x7feae806adf0]:SSL socket setup failure.
[0x7feae806adf0]:error:140BA0E4:SSL routines:SSL_new:ssl ctx has no default ssl
version
2018-09-17 15:48:49.762368 + AUTHSERVICE (warning) Cannot initialise SSL
[0x7feae806adf0]:SSL socket setup failure.
[0x7feae806adf0]:error:140BA0E4:SSL routines:SSL_new:ssl ctx has no default ssl
version{noformat}
After the last line above, the router exited with a seg fault.
> Dispatch Router sporadically goes into a state where TLS connections to the
> auth service fail
> -
>
> Key: DISPATCH-1086
> URL: https://issues.apache.org/jira/browse/DISPATCH-1086
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Keith Wall
>Priority: Major
>
> Whilst running performance tests against Enmasse, we periodically see a
> problem where Dispatch Router (1.1.0) goes into a state where fails to form
> TLS connections to the authservice. When this occurs, the router needs to be
> restarted to restore service. There does not seem to be a pattern to when the
> issue occurs, but in all cases where it has been seen, the test case included
> tens or hundreds of concurrently formed connections.
> The following message is written to the log:
>
> {noformat}
> 2018-07-06 10:38:45.543519 + AUTHSERVICE (warning) Cannot initialise
> SSL{noformat}
> Unfortunately turning up the router logging (using the following command)
> reveal no more useful information. This Proton improvement JIRA was raised to
> include the diagnostics from OpenSSL.
>
--
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-1936) Support cross compiling to Windows from Linux
[ https://issues.apache.org/jira/browse/PROTON-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16617471#comment-16617471 ] ASF GitHub Bot commented on PROTON-1936: GitHub user marcelmeulemans opened a pull request: https://github.com/apache/qpid-proton/pull/156 PROTON-1936: lower case include and updated ifdefs You can merge this pull request into a Git repository by running: $ git pull https://github.com/marcelmeulemans/qpid-proton feat/PROTON-1936 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/156.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #156 commit a34bcdbdf03ea8d69a3d1170fb9df9d4130d5e5e Author: Marcel Meulemans Date: 2018-09-17T12:52:08Z PROTON-1936: lower case include and updated ifdefs > Support cross compiling to Windows from Linux > - > > Key: PROTON-1936 > URL: https://issues.apache.org/jira/browse/PROTON-1936 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Affects Versions: proton-c-0.25.0 >Reporter: Marcel Meulemans >Priority: Minor > > I am cross compiling proton for Windows via docker (multiarch/crossbuild) and > running into a few minor issues that make it not work out of the box (mainly > include file casing). Pull request will follow, more details there ... it > would be nice if this made it upstream. -- 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
[GitHub] qpid-proton pull request #156: PROTON-1936: lower case include and updated i...
GitHub user marcelmeulemans opened a pull request: https://github.com/apache/qpid-proton/pull/156 PROTON-1936: lower case include and updated ifdefs You can merge this pull request into a Git repository by running: $ git pull https://github.com/marcelmeulemans/qpid-proton feat/PROTON-1936 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/156.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #156 commit a34bcdbdf03ea8d69a3d1170fb9df9d4130d5e5e Author: Marcel Meulemans Date: 2018-09-17T12:52:08Z PROTON-1936: lower case include and updated ifdefs --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1936) Support cross compiling to Windows from Linux
Marcel Meulemans created PROTON-1936: Summary: Support cross compiling to Windows from Linux Key: PROTON-1936 URL: https://issues.apache.org/jira/browse/PROTON-1936 Project: Qpid Proton Issue Type: Improvement Components: proton-c Affects Versions: proton-c-0.25.0 Reporter: Marcel Meulemans I am cross compiling proton for Windows via docker (multiarch/crossbuild) and running into a few minor issues that make it not work out of the box (mainly include file casing). Pull request will follow, more details there ... it would be nice if this made it upstream. -- 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-1846) [proton-c] Message decode fails with PN_OUT_OF_MEMORY if there are large lists in the message
[
https://issues.apache.org/jira/browse/PROTON-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16617430#comment-16617430
]
ASF GitHub Bot commented on PROTON-1846:
GitHub user marcelmeulemans opened a pull request:
https://github.com/apache/qpid-proton/pull/155
PROTON-1846: allow more than 65536 nodes in a pn_data_t instance
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/marcelmeulemans/qpid-proton fix/PROTON-1846
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-proton/pull/155.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #155
commit 28f3b60841f3dbe96f81a77c509fd4ec9e571631
Author: Marcel Meulemans
Date: 2018-09-17T12:15:13Z
PROTON-1846: allow more than 65536 nodes in a pn_data_t instance
> [proton-c] Message decode fails with PN_OUT_OF_MEMORY if there are large
> lists in the message
> --
>
> Key: PROTON-1846
> URL: https://issues.apache.org/jira/browse/PROTON-1846
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.22.0
>Reporter: Ganesh Murthy
>Priority: Major
> Attachments: send_large_structured_body.js
>
>
> Steps to reproduce -
>
> # Start the Qpid Dispatch router
> # Run the following script that creates a bunch of addresses
> # for i in `seq 1 6546`; do echo
> "\{\"prefix\":\"address-$i\",\"distribution\":\"balanced\"}" | qdmanage
> CREATE --type=org.apache.qpid.dispatch.router.config.address --name
> address-$i --stdin; done
> # now run qdmanage QUERY --type=address
> # You will receive a Data error (-10)
> The following diff seems to fix the issue
> diff --git a/c/src/core/data.h b/c/src/core/data.h
> index 94dc7d67..f4320e2a 100644
> --- a/c/src/core/data.h
> +++ b/c/src/core/data.h
> @@ -27,7 +27,7 @@
> #include "decoder.h"
> #include "encoder.h"
>
> -typedef uint16_t pni_nid_t;
> +typedef uint32_t pni_nid_t;
> #define PNI_NID_MAX ((pni_nid_t)-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
[GitHub] qpid-proton pull request #155: PROTON-1846: allow more than 65536 nodes in a...
GitHub user marcelmeulemans opened a pull request: https://github.com/apache/qpid-proton/pull/155 PROTON-1846: allow more than 65536 nodes in a pn_data_t instance You can merge this pull request into a Git repository by running: $ git pull https://github.com/marcelmeulemans/qpid-proton fix/PROTON-1846 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/155.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #155 commit 28f3b60841f3dbe96f81a77c509fd4ec9e571631 Author: Marcel Meulemans Date: 2018-09-17T12:15:13Z PROTON-1846: allow more than 65536 nodes in a pn_data_t instance --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
