[jira] [Commented] (PROTON-1990) drain gets stuck on
[ https://issues.apache.org/jira/browse/PROTON-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761507#comment-16761507 ] ASF subversion and git services commented on PROTON-1990: - Commit d47160b715b8d103985d0c26edbb64d8a4235708 in qpid-proton's branch refs/heads/master from Clifford Jansen [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=d47160b ] PROTON-1990: no-op whitespace "fix". Sorry for the Windows AppVeyor test abuse. > drain gets stuck on > --- > > Key: PROTON-1990 > URL: https://issues.apache.org/jira/browse/PROTON-1990 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.26.0 >Reporter: Gordon Sim >Assignee: Cliff Jansen >Priority: Major > Labels: patch > Fix For: proton-c-0.27.0 > > Attachments: drain.patch > > > See [http://qpid.2158936.n2.nabble.com/Drain-issue-in-proton-C-td7681843.html] > > When draining a receiver link in the proton c++ api, if there are > insuffficient messages on the source, the draining mode gets stuck on so that > subsequent granting of credit causes the credit to be immediately drained. > This appears to be due to the flag not being set on the pn_link_t instance. > -- 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-1990) drain gets stuck on
[ https://issues.apache.org/jira/browse/PROTON-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761029#comment-16761029 ] ASF subversion and git services commented on PROTON-1990: - Commit aad89ef1b999d378ee595f18c7c6d83c70b26097 in qpid-proton's branch refs/heads/master from Clifford Jansen [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=aad89ef ] PROTON-1990: stay within C++03 constraints > drain gets stuck on > --- > > Key: PROTON-1990 > URL: https://issues.apache.org/jira/browse/PROTON-1990 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.26.0 >Reporter: Gordon Sim >Assignee: Cliff Jansen >Priority: Major > Labels: patch > Fix For: proton-c-0.27.0 > > Attachments: drain.patch > > > See [http://qpid.2158936.n2.nabble.com/Drain-issue-in-proton-C-td7681843.html] > > When draining a receiver link in the proton c++ api, if there are > insuffficient messages on the source, the draining mode gets stuck on so that > subsequent granting of credit causes the credit to be immediately drained. > This appears to be due to the flag not being set on the pn_link_t instance. > -- 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] alanconway merged pull request #171: NO-JIRA: outdated `pn_connection_driver_free` reference in doc comment
alanconway merged pull request #171: NO-JIRA: outdated `pn_connection_driver_free` reference in doc comment URL: https://github.com/apache/qpid-proton/pull/171 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (PROTON-1990) drain gets stuck on
[ https://issues.apache.org/jira/browse/PROTON-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen reopened PROTON-1990: -- Naughty and unnecessary C++11 usage. > drain gets stuck on > --- > > Key: PROTON-1990 > URL: https://issues.apache.org/jira/browse/PROTON-1990 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.26.0 >Reporter: Gordon Sim >Assignee: Cliff Jansen >Priority: Major > Labels: patch > Fix For: proton-c-0.27.0 > > Attachments: drain.patch > > > See [http://qpid.2158936.n2.nabble.com/Drain-issue-in-proton-C-td7681843.html] > > When draining a receiver link in the proton c++ api, if there are > insuffficient messages on the source, the draining mode gets stuck on so that > subsequent granting of credit causes the credit to be immediately drained. > This appears to be due to the flag not being set on the pn_link_t instance. > -- 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] gemmellr commented on issue #175: src/ssl/openssl: add libressl compatibility
gemmellr commented on issue #175: src/ssl/openssl: add libressl compatibility URL: https://github.com/apache/qpid-proton/pull/175#issuecomment-460630039 I'll defer review/merge to folks familiar with these bits, but can you please raise a JIRA issue at https://issues.apache.org/jira/browse/PROTON and reference it in your commit message (see previous commits for example). This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1893) [c] idle-timeout set in REMOTE_OPEN does not take immediate effect.
[ https://issues.apache.org/jira/browse/PROTON-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1893: --- Fix Version/s: (was: proton-c-0.27.0) proton-c-0.28.0 > [c] idle-timeout set in REMOTE_OPEN does not take immediate effect. > --- > > Key: PROTON-1893 > URL: https://issues.apache.org/jira/browse/PROTON-1893 > Project: Qpid Proton > Issue Type: Bug >Affects Versions: proton-c-0.24.0 >Reporter: Alan Conway >Assignee: Cliff Jansen >Priority: Major > Fix For: proton-c-0.28.0 > > > If idle-timeout is set on the server in a PN_CONNECTION_REMOTE_OPEN event, it > is correctly sent to the peer in the OPEN frame, but the local timer is not > activated until the first data is read or written on the connection. If the > client never sends another frame, the server does not time out the connection. -- 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] rc-matthew-l-weber opened a new pull request #175: src/ssl/openssl: add libressl compatibility
rc-matthew-l-weber opened a new pull request #175: src/ssl/openssl: add libressl compatibility URL: https://github.com/apache/qpid-proton/pull/175 Similar to 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. Signed-off-by: Matthew Weber This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Uncontrolled exit of qpidd broker
The mailing list strips larger attachments like images. Send information as text in the body. Please mail the users mailing list for user questions. There is far less 'noise' traffic, and a larger audience who can chime in. Replies go to the list normally, so if you dont subscribe you will need to monitor the archives for responses. On Tue, 5 Feb 2019 at 08:50, Bhavadharini Krishnamoorthy (bhavadkr) wrote: > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > For additional commands, e-mail: dev-h...@qpid.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Uncontrolled exit of qpidd broker
- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
