[jira] [Resolved] (QPIDJMS-600) Session and Connection close should await async send completion
[ https://issues.apache.org/jira/browse/QPIDJMS-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish resolved QPIDJMS-600. - Resolution: Fixed > Session and Connection close should await async send completion > --- > > Key: QPIDJMS-600 > URL: https://issues.apache.org/jira/browse/QPIDJMS-600 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 2.5.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Minor > Fix For: 2.6.0 > > > According to the JMS specification the close of a session or connection > should be allowing for messages sent via the asynchronous API to complete > normally before completing the close. Currently this is not being allow to > happen and pending asynchronous sends are failed from a call to session or > connection close. The MessageProducer close is awaiting completion of > asynchronous sends as the specification requires. -- 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] (QPIDJMS-600) Session and Connection close should await async send completion
[ https://issues.apache.org/jira/browse/QPIDJMS-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839146#comment-17839146 ] ASF subversion and git services commented on QPIDJMS-600: - Commit 90eb60f59cb59b7b9ad8363ee8a843d6903b8e77 in qpid-jms's branch refs/heads/main from Timothy Bish [ https://gitbox.apache.org/repos/asf?p=qpid-jms.git;h=90eb60f5 ] QPIDJMS-600 Ensure session and connection close await async sends Session and Connection close should be awaiting the outcome of async send completions before returning. This change allows them to await up to the close timeout value before moving on and failing any completions that are not completed after that point. Several tests added to cover this behavior. > Session and Connection close should await async send completion > --- > > Key: QPIDJMS-600 > URL: https://issues.apache.org/jira/browse/QPIDJMS-600 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 2.5.0 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Minor > Fix For: 2.6.0 > > > According to the JMS specification the close of a session or connection > should be allowing for messages sent via the asynchronous API to complete > normally before completing the close. Currently this is not being allow to > happen and pending asynchronous sends are failed from a call to session or > connection close. The MessageProducer close is awaiting completion of > asynchronous sends as the specification requires. -- 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] [Assigned] (PROTON-2810) C++ compile standard needs to be advanced to c++14 or later
[ https://issues.apache.org/jira/browse/PROTON-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-2810: --- Assignee: Andrew Stitcher > C++ compile standard needs to be advanced to c++14 or later > --- > > Key: PROTON-2810 > URL: https://issues.apache.org/jira/browse/PROTON-2810 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding, examples >Reporter: Kim van der Riet >Assignee: Andrew Stitcher >Priority: Major > > The use of opentelemetry-cpp API in qpid-proton is forcing the C++ compile > standard to be c++14 or later. The support for c++11 (which qpid-proton is > currently using) in opentelemetry-cpp was removed in v 1.12.0 (we are > currently at version 1.14.2), and the use of its APIs is causing compile > errors. > Consideration should be given to moving the compiler C++ standard to 14, 17 > or even 20. > I have tested the compile using c++17, and this does not create any compile > errors, and solves the opentelemetry-cpp API error too. -- 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-2817) [Python] Allow control of whether python build uses pip inside virtual environments
[ https://issues.apache.org/jira/browse/PROTON-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2817. - Resolution: Fixed > [Python] Allow control of whether python build uses pip inside virtual > environments > --- > > Key: PROTON-2817 > URL: https://issues.apache.org/jira/browse/PROTON-2817 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > For the purposes of distribution package building (and other repeatable, > reliable environments). We need to have a way to restrict the python build > from attemping to access the internet to download updated packages as part of > its build. -- 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-2816) The current python pkg build can only build a package with a bundled proton core
[ https://issues.apache.org/jira/browse/PROTON-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2816. - Resolution: Fixed > The current python pkg build can only build a package with a bundled proton > core > > > Key: PROTON-2816 > URL: https://issues.apache.org/jira/browse/PROTON-2816 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.38.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > This is an issue for 2 scenarios: > - Producing python packages for distributions that should depend on the > system installed proton core library > - Debugging the C code (either library or adaptation layer code) when running > from python. -- 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-2816) The current python pkg build can only build a package with a bundled proton core
[ https://issues.apache.org/jira/browse/PROTON-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839144#comment-17839144 ] ASF GitHub Bot commented on PROTON-2816: asfgit merged PR #426: URL: https://github.com/apache/qpid-proton/pull/426 > The current python pkg build can only build a package with a bundled proton > core > > > Key: PROTON-2816 > URL: https://issues.apache.org/jira/browse/PROTON-2816 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.38.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > This is an issue for 2 scenarios: > - Producing python packages for distributions that should depend on the > system installed proton core library > - Debugging the C code (either library or adaptation layer code) when running > from python. -- 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-2817) [Python] Allow control of whether python build uses pip inside virtual environments
[ https://issues.apache.org/jira/browse/PROTON-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839143#comment-17839143 ] ASF subversion and git services commented on PROTON-2817: - Commit a2e9eb63444bbda70f8870e28d5ef93b68c0bbe5 in qpid-proton's branch refs/heads/main from Andrew Stitcher [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=a2e9eb634 ] PROTON-2816/PROTON-2817: Support building python extension with unbundled proton There are 3 cases: * Bundled proton library - this should be the default and is what you should use with pip etc. * System proton library - this is what you should use in a distro package. * Use the in tree library built earlier in the build process - this is what you usually want for developer debugging, and should be the version actually tested by the in tree tests. This change also add control of the ability to package and test in isolated virtual python environments. Using these is the default, but under some circumstances you do not want the build process to construct a virtual environment by pulling packages from the internet. So we now have an option to turn this behaviour off and rely on the hosts python environment. > [Python] Allow control of whether python build uses pip inside virtual > environments > --- > > Key: PROTON-2817 > URL: https://issues.apache.org/jira/browse/PROTON-2817 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > For the purposes of distribution package building (and other repeatable, > reliable environments). We need to have a way to restrict the python build > from attemping to access the internet to download updated packages as part of > its build. -- 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-2816) The current python pkg build can only build a package with a bundled proton core
[ https://issues.apache.org/jira/browse/PROTON-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839142#comment-17839142 ] ASF subversion and git services commented on PROTON-2816: - Commit a2e9eb63444bbda70f8870e28d5ef93b68c0bbe5 in qpid-proton's branch refs/heads/main from Andrew Stitcher [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=a2e9eb634 ] PROTON-2816/PROTON-2817: Support building python extension with unbundled proton There are 3 cases: * Bundled proton library - this should be the default and is what you should use with pip etc. * System proton library - this is what you should use in a distro package. * Use the in tree library built earlier in the build process - this is what you usually want for developer debugging, and should be the version actually tested by the in tree tests. This change also add control of the ability to package and test in isolated virtual python environments. Using these is the default, but under some circumstances you do not want the build process to construct a virtual environment by pulling packages from the internet. So we now have an option to turn this behaviour off and rely on the hosts python environment. > The current python pkg build can only build a package with a bundled proton > core > > > Key: PROTON-2816 > URL: https://issues.apache.org/jira/browse/PROTON-2816 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.38.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > This is an issue for 2 scenarios: > - Producing python packages for distributions that should depend on the > system installed proton core library > - Debugging the C code (either library or adaptation layer code) when running > from python. -- 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-2815) [Python] Use up to date tooling to produce python packages
[ https://issues.apache.org/jira/browse/PROTON-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2815. - Resolution: Fixed > [Python] Use up to date tooling to produce python packages > -- > > Key: PROTON-2815 > URL: https://issues.apache.org/jira/browse/PROTON-2815 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > > Using setup.py as a python script to produce python packages/install packages > etc has been deprecated for a little while and will be going away from python > soon. > We should update our build to use a supported tool to build our packages. > The simplest approach would be to use the 'build' module with the setuptools > backend. -- 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
Re: [PR] PROTON-2816/PROTON-2817: Support building python extension with unbun… [qpid-proton]
asfgit merged PR #426: URL: https://github.com/apache/qpid-proton/pull/426 -- 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
[PR] PROTON-2816/PROTON-2817: Support building python extension with unbun… [qpid-proton]
astitcher opened a new pull request, #426: URL: https://github.com/apache/qpid-proton/pull/426 …dled proton There are 3 cases: * Bundled proton library - this should be the default and is what you should use with pip etc. * System proton library - this is what you should use in a distro package. * Use the in tree library built earlier in the build process - this is what you usually want for developer debugging, and should be the version actually tested by the in tree tests. This change also add control of the ability to package and test in isolated virtual python environments. Using these is the default, but under some circumstances you do not want the build process to construct a virtual environment by pulling packages from the internet. So we now have an option to turn this behaviour off and rely on the hosts python environment. -- 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] [Commented] (PROTON-2816) The current python pkg build can only build a package with a bundled proton core
[ https://issues.apache.org/jira/browse/PROTON-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839132#comment-17839132 ] ASF GitHub Bot commented on PROTON-2816: astitcher opened a new pull request, #426: URL: https://github.com/apache/qpid-proton/pull/426 …dled proton There are 3 cases: * Bundled proton library - this should be the default and is what you should use with pip etc. * System proton library - this is what you should use in a distro package. * Use the in tree library built earlier in the build process - this is what you usually want for developer debugging, and should be the version actually tested by the in tree tests. This change also add control of the ability to package and test in isolated virtual python environments. Using these is the default, but under some circumstances you do not want the build process to construct a virtual environment by pulling packages from the internet. So we now have an option to turn this behaviour off and rely on the hosts python environment. > The current python pkg build can only build a package with a bundled proton > core > > > Key: PROTON-2816 > URL: https://issues.apache.org/jira/browse/PROTON-2816 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.38.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > This is an issue for 2 scenarios: > - Producing python packages for distributions that should depend on the > system installed proton core library > - Debugging the C code (either library or adaptation layer code) when running > from python. -- 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] [Created] (PROTON-2817) [Python] Allow control of whether python build uses pip inside virtual environments
Andrew Stitcher created PROTON-2817: --- Summary: [Python] Allow control of whether python build uses pip inside virtual environments Key: PROTON-2817 URL: https://issues.apache.org/jira/browse/PROTON-2817 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: proton-c-0.39.0 Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: proton-c-0.40.0 For the purposes of distribution package building (and other repeatable, reliable environments). We need to have a way to restrict the python build from attemping to access the internet to download updated packages as part of its build. -- 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-599) JmsTransactionInDoubtException: error
[ https://issues.apache.org/jira/browse/QPIDJMS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish closed QPIDJMS-599. --- Resolution: Information Provided > JmsTransactionInDoubtException: error > - > > Key: QPIDJMS-599 > URL: https://issues.apache.org/jira/browse/QPIDJMS-599 > Project: Qpid JMS > Issue Type: Bug >Affects Versions: 1.6.0 >Reporter: Rajesh Kumar >Priority: Major > Attachments: JMS_Exception_Details.txt > > > Hi Team, > we are receiving the following error intermittently > > Exception Details related JmsTransactionInDoubtException: > > Call Stack: org.apache.qpid.jms.JmsTransactionInDoubtException: Transaction > is not declared Reference:9a13135d-348c-4a78-b53c-097a11ac103f, > TrackingId:8ee88669-b631-4261-93eb-09b9beded92f_G8S3, SystemTracker:gtm, > Timestamp:2024-03-05T01:40:45 [condition = amqp:transaction:unknown-id] > at > org.apache.qpid.jms.provider.exceptions.ProviderTransactionInDoubtException.toJMSException(ProviderTransactionInDoubtException.java:39) > at > org.apache.qpid.jms.provider.exceptions.ProviderTransactionInDoubtException.toJMSException(ProviderTransactionInDoubtException.java:25) > > Kindly help in fixing this error in priority -- 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] [Created] (PROTON-2816) The current python pkg build can only build a package with a bundled proton core
Andrew Stitcher created PROTON-2816: --- Summary: The current python pkg build can only build a package with a bundled proton core Key: PROTON-2816 URL: https://issues.apache.org/jira/browse/PROTON-2816 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: proton-c-0.38.0 Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: proton-c-0.40.0 This is an issue for 2 scenarios: - Producing python packages for distributions that should depend on the system installed proton core library - Debugging the C code (either library or adaptation layer code) when running from python. -- 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-2815) [Python] Use up to date tooling to produce python packages
[ https://issues.apache.org/jira/browse/PROTON-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839076#comment-17839076 ] ASF subversion and git services commented on PROTON-2815: - Commit e3ba722b6df57b2f81787e0ace8efb7ac639d501 in qpid-proton's branch refs/heads/main from Andrew Stitcher [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=e3ba722b6 ] PROTON-2815: [Python] Correct supported versions of Python (again) > [Python] Use up to date tooling to produce python packages > -- > > Key: PROTON-2815 > URL: https://issues.apache.org/jira/browse/PROTON-2815 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > > Using setup.py as a python script to produce python packages/install packages > etc has been deprecated for a little while and will be going away from python > soon. > We should update our build to use a supported tool to build our packages. > The simplest approach would be to use the 'build' module with the setuptools > backend. -- 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
