[ANNOUNCE] Apache Qpid JMS 2.2.0 released
The Apache Qpid (https://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid JMS 2.2.0. This is the latest release of our newer JMS client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, https://www.amqp.org), based around the Apache Qpid Proton protocol engine and implementing the AMQP JMS Mapping as it evolves at OASIS. Note the 2.x client releases use Jakarta Messaging 3.1 and its "jakarta.jms" package. For existing "javax.jms" use cases continue to use the 1.x client releases. The release is available now from our website: https://qpid.apache.org/download.html Binaries are also available via Maven Central: https://qpid.apache.org/maven.html Release notes can be found at: https://qpid.apache.org/releases/qpid-jms-2.2.0/release-notes.html Thanks to all involved, Robbie - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid JMS 1.8.0 released
The Apache Qpid (https://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid JMS 1.8.0. This is the latest release of our newer JMS client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, https://www.amqp.org), based around the Apache Qpid Proton protocol engine and implementing the AMQP JMS Mapping as it evolves at OASIS. The release is available now from our website: https://qpid.apache.org/download.html Binaries are also available via Maven Central: https://qpid.apache.org/maven.html Release notes can be found at: https://qpid.apache.org/releases/qpid-jms-1.8.0/release-notes.html Thanks to all involved, Robbie - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2663) class ssl_client_options does not have a constructor for a custom client certificate, and default certificate trust database
[ https://issues.apache.org/jira/browse/PROTON-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676700#comment-17676700 ] ASF GitHub Bot commented on PROTON-2663: astitcher commented on PR #384: URL: https://github.com/apache/qpid-proton/pull/384#issuecomment-1382141185 Thank you for this PR - I've now merged it into the main branch and it should be in the 0.39 release > class ssl_client_options does not have a constructor for a custom client > certificate, and default certificate trust database > - > > Key: PROTON-2663 > URL: https://issues.apache.org/jira/browse/PROTON-2663 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.37.0 > Environment: Linux 64bit > Ubuntu 22.04: libqpid-proton-cpp12 0.22.0-5 (used for testing, not intended > for production) > Redhat, Oracle: qpid-proton-cpp-0.37.0-1.el8.x86_64 >Reporter: Marko Hrastovec >Priority: Blocker > Labels: ssl > Fix For: proton-c-0.39.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > Class ssl_client_options does not have a constructor for a custom client > certificate, and default certificate trust database. > Out application has to present a custom certificate to the server, but the > server uses a certificate signed by a certificate authority (CA) that is > present in the systems default certificate trust database. > Curently, our only option to connect is to supply a dummy certificate trust > database, and use proton::ssl::ANONYMOUS_PEER which disables server check. In > that way, we skip an important check for a secure connection. That is > unacceptable for a production version of our application. Until we come to a > production version we must resolve that issue. That is why I marked it as a > blocker. > I have a patch, but I am not sure how to contribute it. I guess reporting is > a first step? -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2663) class ssl_client_options does not have a constructor for a custom client certificate, and default certificate trust database
[ https://issues.apache.org/jira/browse/PROTON-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676701#comment-17676701 ] ASF GitHub Bot commented on PROTON-2663: astitcher closed pull request #384: PROTON-2663 Add a constructor to ssl_client_options class URL: https://github.com/apache/qpid-proton/pull/384 > class ssl_client_options does not have a constructor for a custom client > certificate, and default certificate trust database > - > > Key: PROTON-2663 > URL: https://issues.apache.org/jira/browse/PROTON-2663 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.37.0 > Environment: Linux 64bit > Ubuntu 22.04: libqpid-proton-cpp12 0.22.0-5 (used for testing, not intended > for production) > Redhat, Oracle: qpid-proton-cpp-0.37.0-1.el8.x86_64 >Reporter: Marko Hrastovec >Priority: Blocker > Labels: ssl > Fix For: proton-c-0.39.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > Class ssl_client_options does not have a constructor for a custom client > certificate, and default certificate trust database. > Out application has to present a custom certificate to the server, but the > server uses a certificate signed by a certificate authority (CA) that is > present in the systems default certificate trust database. > Curently, our only option to connect is to supply a dummy certificate trust > database, and use proton::ssl::ANONYMOUS_PEER which disables server check. In > that way, we skip an important check for a secure connection. That is > unacceptable for a production version of our application. Until we come to a > production version we must resolve that issue. That is why I marked it as a > blocker. > I have a patch, but I am not sure how to contribute it. I guess reporting is > a first step? -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-proton] astitcher commented on pull request #384: PROTON-2663 Add a constructor to ssl_client_options class
astitcher commented on PR #384: URL: https://github.com/apache/qpid-proton/pull/384#issuecomment-1382141185 Thank you for this PR - I've now merged it into the main branch and it should be in the 0.39 release -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-proton] astitcher closed pull request #384: PROTON-2663 Add a constructor to ssl_client_options class
astitcher closed pull request #384: PROTON-2663 Add a constructor to ssl_client_options class URL: https://github.com/apache/qpid-proton/pull/384 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2663) class ssl_client_options does not have a constructor for a custom client certificate, and default certificate trust database
[ https://issues.apache.org/jira/browse/PROTON-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2663. - Fix Version/s: proton-c-0.39.0 (was: proton-c-0.37.0) Resolution: Fixed > class ssl_client_options does not have a constructor for a custom client > certificate, and default certificate trust database > - > > Key: PROTON-2663 > URL: https://issues.apache.org/jira/browse/PROTON-2663 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.37.0 > Environment: Linux 64bit > Ubuntu 22.04: libqpid-proton-cpp12 0.22.0-5 (used for testing, not intended > for production) > Redhat, Oracle: qpid-proton-cpp-0.37.0-1.el8.x86_64 >Reporter: Marko Hrastovec >Priority: Blocker > Labels: ssl > Fix For: proton-c-0.39.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > Class ssl_client_options does not have a constructor for a custom client > certificate, and default certificate trust database. > Out application has to present a custom certificate to the server, but the > server uses a certificate signed by a certificate authority (CA) that is > present in the systems default certificate trust database. > Curently, our only option to connect is to supply a dummy certificate trust > database, and use proton::ssl::ANONYMOUS_PEER which disables server check. In > that way, we skip an important check for a secure connection. That is > unacceptable for a production version of our application. Until we come to a > production version we must resolve that issue. That is why I marked it as a > blocker. > I have a patch, but I am not sure how to contribute it. I guess reporting is > a first step? -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2663) class ssl_client_options does not have a constructor for a custom client certificate, and default certificate trust database
[ https://issues.apache.org/jira/browse/PROTON-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676698#comment-17676698 ] ASF subversion and git services commented on PROTON-2663: - Commit b292237524dbe9f8df4d53bc68295f5b45aa915c in qpid-proton's branch refs/heads/main from Marko Hrastovec [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=b29223752 ] PROTON-2663: Add a constructor to ssl_client_options class Previously there was no way for the C++ API to specify an SSL certificate whilst leaving the system trusted certificate db > class ssl_client_options does not have a constructor for a custom client > certificate, and default certificate trust database > - > > Key: PROTON-2663 > URL: https://issues.apache.org/jira/browse/PROTON-2663 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.37.0 > Environment: Linux 64bit > Ubuntu 22.04: libqpid-proton-cpp12 0.22.0-5 (used for testing, not intended > for production) > Redhat, Oracle: qpid-proton-cpp-0.37.0-1.el8.x86_64 >Reporter: Marko Hrastovec >Priority: Blocker > Labels: ssl > Fix For: proton-c-0.37.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > Class ssl_client_options does not have a constructor for a custom client > certificate, and default certificate trust database. > Out application has to present a custom certificate to the server, but the > server uses a certificate signed by a certificate authority (CA) that is > present in the systems default certificate trust database. > Curently, our only option to connect is to supply a dummy certificate trust > database, and use proton::ssl::ANONYMOUS_PEER which disables server check. In > that way, we skip an important check for a secure connection. That is > unacceptable for a production version of our application. Until we come to a > production version we must resolve that issue. That is why I marked it as a > blocker. > I have a patch, but I am not sure how to contribute it. I guess reporting is > a first step? -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDJMS-582) Update to Netty 4.1.86
[ https://issues.apache.org/jira/browse/QPIDJMS-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPIDJMS-582. Resolution: Fixed > Update to Netty 4.1.86 > -- > > Key: QPIDJMS-582 > URL: https://issues.apache.org/jira/browse/QPIDJMS-582 > Project: Qpid JMS > Issue Type: Task > Components: qpid-jms-client >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 1.8.0, 2.2.0 > > > Update to Netty 4.1.86 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDJMS-582) Update to Netty 4.1.86
[ https://issues.apache.org/jira/browse/QPIDJMS-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed QPIDJMS-582. -- > Update to Netty 4.1.86 > -- > > Key: QPIDJMS-582 > URL: https://issues.apache.org/jira/browse/QPIDJMS-582 > Project: Qpid JMS > Issue Type: Task > Components: qpid-jms-client >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 1.8.0, 2.2.0 > > > Update to Netty 4.1.86 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-broker-j] dakirily opened a new pull request, #168: NO-JIRA: update dependencies versions
dakirily opened a new pull request, #168: URL: https://github.com/apache/qpid-broker-j/pull/168 This PR updates - com.fasterxml.jackson.core:jackson-core to 2.14.1 - com.fasterxml.jackson.core:jackson-databind to 2.14.1 - org.dojotoolkit:dojo to 1.17.3 - org.mockito:mockito-core to 4.11.0 - io.netty:* to 4.1.87.Final - org.apache.qpid:qpid-client to 6.4.0 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-8617) [Broker-J] Jetty server dependencies update
Daniil Kirilyuk created QPID-8617: - Summary: [Broker-J] Jetty server dependencies update Key: QPID-8617 URL: https://issues.apache.org/jira/browse/QPID-8617 Project: Qpid Issue Type: Improvement Components: Broker-J Affects Versions: qpid-java-broker-9.0.0 Reporter: Daniil Kirilyuk Fix For: qpid-java-broker-9.0.1 Jetty Server 9.x has reached end of community support ([github issue|https://github.com/eclipse/jetty.project/issues/7958]). Current Jetty version should be updated either to 10.x or 11.x. Considering that Jetty 12.x is currently in alpha version, it would be preferable to update it to the latest version available (11.x) to make easier further updates. Update will include * dependencies update * namespaces update (javax.servlet.* migrated to jakarta.servlet.*) * code refactoring (in few cases it may be needed to refactor logic in favor of more actual Jetty mechanisms) -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2653) [cpp] Can't see tracing documentation on public website.
[ https://issues.apache.org/jira/browse/PROTON-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakhi Kumari resolved PROTON-2653. -- Fix Version/s: proton-c-0.39.0 Resolution: Fixed > [cpp] Can't see tracing documentation on public website. > > > Key: PROTON-2653 > URL: https://issues.apache.org/jira/browse/PROTON-2653 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Reporter: Rakhi Kumari >Assignee: Rakhi Kumari >Priority: Major > Fix For: proton-c-0.39.0 > > Attachments: Tracing_doc_-not_visible-1.png > > > Tracing documentation in doxygen format (cpp/examples/tracing.dox) is not > linking properly and thus is not visible on the public website. > [https://qpid.apache.org/releases/qpid-proton-0.38.0/proton/cpp/api/tracing.html] > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2657) [cpp] Accessors for user data on endpoints and deliveries
[ https://issues.apache.org/jira/browse/PROTON-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakhi Kumari resolved PROTON-2657. -- Fix Version/s: proton-c-0.39.0 Resolution: Fixed > [cpp] Accessors for user data on endpoints and deliveries > - > > Key: PROTON-2657 > URL: https://issues.apache.org/jira/browse/PROTON-2657 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Reporter: Rakhi Kumari >Assignee: Rakhi Kumari >Priority: Major > Fix For: proton-c-0.39.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2653) [cpp] Can't see tracing documentation on public website.
[ https://issues.apache.org/jira/browse/PROTON-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676534#comment-17676534 ] ASF GitHub Bot commented on PROTON-2653: DreamPearl closed pull request #383: PROTON-2653: [cpp] Move tracing.dox to docs folder URL: https://github.com/apache/qpid-proton/pull/383 > [cpp] Can't see tracing documentation on public website. > > > Key: PROTON-2653 > URL: https://issues.apache.org/jira/browse/PROTON-2653 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Reporter: Rakhi Kumari >Assignee: Rakhi Kumari >Priority: Major > Attachments: Tracing_doc_-not_visible-1.png > > > Tracing documentation in doxygen format (cpp/examples/tracing.dox) is not > linking properly and thus is not visible on the public website. > [https://qpid.apache.org/releases/qpid-proton-0.38.0/proton/cpp/api/tracing.html] > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2653) [cpp] Can't see tracing documentation on public website.
[ https://issues.apache.org/jira/browse/PROTON-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676533#comment-17676533 ] ASF GitHub Bot commented on PROTON-2653: DreamPearl commented on PR #383: URL: https://github.com/apache/qpid-proton/pull/383#issuecomment-1381514548 Merged as https://github.com/apache/qpid-proton/commit/21280a08a9c673393fb7dd01dfd2f05f36378722. > [cpp] Can't see tracing documentation on public website. > > > Key: PROTON-2653 > URL: https://issues.apache.org/jira/browse/PROTON-2653 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Reporter: Rakhi Kumari >Assignee: Rakhi Kumari >Priority: Major > Attachments: Tracing_doc_-not_visible-1.png > > > Tracing documentation in doxygen format (cpp/examples/tracing.dox) is not > linking properly and thus is not visible on the public website. > [https://qpid.apache.org/releases/qpid-proton-0.38.0/proton/cpp/api/tracing.html] > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-proton] DreamPearl closed pull request #383: PROTON-2653: [cpp] Move tracing.dox to docs folder
DreamPearl closed pull request #383: PROTON-2653: [cpp] Move tracing.dox to docs folder URL: https://github.com/apache/qpid-proton/pull/383 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-proton] DreamPearl commented on pull request #383: PROTON-2653: [cpp] Move tracing.dox to docs folder
DreamPearl commented on PR #383: URL: https://github.com/apache/qpid-proton/pull/383#issuecomment-1381514548 Merged as https://github.com/apache/qpid-proton/commit/21280a08a9c673393fb7dd01dfd2f05f36378722. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
