[ANNOUNCE] Apache Qpid ProtonJ2 1.0.0-M14 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache ProtonJ2 1.0.0-M14. This is the latest release of our AMQP Java client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid ProtonJ2 protocol engine also contained in this release. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via Maven Central: http://qpid.apache.org/maven.html Release notes can be found at: http://qpid.apache.org/releases/qpid-protonj2-1.0.0-M14/release-notes.html Thanks to all involved, -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT][VOTE] Release Apache Qpid ProtonJ2 1.0.0-M14
There were 3 binding +1 votes, and 1 other votes received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly. The website will be updated after the release has had time to sync to the mirrors and maven central. -- Tim Bish - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [EXTERNAL]Re: Installing qpid-cpp on RHEL9 with python3 fails
On Thu, Apr 13, 2023 at 2:31 PM Do, Eling wrote: > Hi Jiri, thanks for responding to my question...much appreciated. That > would be great if changing the order of things during the install would > allow the library install to complete even if the tests cannot run. Done now, it is failing merrily on setup.py now. > Any idea as to when a build/snapshot with this change might be available? > I won't promise anything. The setup.py processes the spec xml and generates the .pcl file, which means it actually runs more of the client code than what I originally expected. I already have all of it fixed on my machine, passing all the tests, but I am still reviewing it and trying to make as little of a mess as possible. Specifically, I am confused regarding where bytes (b"") or strings (u"") should be accepted, for example as message bodies, various message fields, and so on; I _can_ of course make the library convert inputs to bytes, but the question is if it is desirable. My current feeling is that I should not do this and instead have the tests pass b"" where necessary...) That makes the changes Python 2-neutral, because in python2, adding b in front of "string" does nothing. I want to carry on with this, hopefully ending up running an Apache release vote when the work is done ;P, but it is hardly my top priority. I don't want to diminish the significance of what I am trying to do here, but, to tell the truth, if I were a Qpid user wanting a broker on RHEL9, I would probably run qpid-cpp in a RHEL8-based docker, having compiled it against Python 2). Or I'd try to migrate to some other, more actively developed, broker. Are there some particular features of qpidd that you are especially attached to, that are hard to get from the alternatives? -- Mit freundlichen Grüßen / Kind regards Jiri Daněk
RE: [EXTERNAL]Re: Installing qpid-cpp on RHEL9 with python3 fails
Hi Jiri, thanks for responding to my question...much appreciated. That would be great if changing the order of things during the install would allow the library install to complete even if the tests cannot run. Any idea as to when a build/snapshot with this change might be available? Thanks again. -Eling -Original Message- From: Jiri Daněk Sent: Wednesday, April 12, 2023 3:45 PM To: users@qpid.apache.org Subject: Re: [EXTERNAL]Re: Installing qpid-cpp on RHEL9 with python3 fails On Wed, Apr 12, 2023 at 4:20 PM Do, Eling wrote: > Thanks for your response Robbie. It seems as though the error I'm > getting comes from a released version of qpid-python that is > automatically downloaded during the install (See below). Do you know > if there is a way to have it download a snapshot version that includes > the fix for the > python3 syntax errors or if there is a snapshot of qpid-cpp that would > download a newer version of qpid-python that supports python3? Sorry > I am very new to qpid and github so I'm not very familiar with how to > find specific snapshots on the site. > There is no such snapshot published anywhere. At some point we had a prerelease version on PyPI for qpid-proton, though https://pypi.org/project/python-qpid-proton/0.38.0.dev0/ so there is precedent for doing things like this. I should probably eventually learn how to get PyPI credentials... It should be enough to upload them to GitHub and then use this nice workflow to do PyPI releases https://github.com/apache/qpid-python/blob/main/.github/workflows/python-publish.yml Personally I am thinking about adding a CMake build option to qpid-cpp which would tell it to go fetch qpid-python from a git repository, which I then want to enable in CI, so that I get test results from the combination of the two git heads. > File "/tmp/easy_install-u03_e80q/qpid-python-1.36.0-1/setup.py", line 42 > raise DistutilsFileError, \ > ^ > SyntaxError: invalid syntax > It is not yet completely fixed on qpid-python main. I still have there the Python 2 `except:` written like except os.error as (errno, errstr): which needs to be changed. I guess I should also change the order of CI steps for qpid-python, to first try to install the library, and only then to run the tests. The current order means I get Python 3 failure on trying to run tests, and install is not even attempted. For qpid-cpp install it is enough if the qpid-python lib installs, it does not have to actually work on Python 3. And making it work, resolving all the bytes/str issues correctly, will take time. I'm going to try what I just suggested next. For this evening I got insead stuck on debugging disappearing tests after switching to the new module importer (from __future__ import absolute import) ;( Btw, regarding the disappearning tests on Python 3. The qpid-proton-python uses the same bespoke testrunner and thus has the same problem https://issues.apache.org/jira/browse/QPID-8170?focusedCommentId=17711533&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17711533, but since the test code there does not have nested modules and weird * imports, this problem does not actually visibly manifest there. -- Mit freundlichen Grüßen / Kind regards Jiri Daněk - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
connection issue from Apache ActiveMQ to Solace PubSub+ using python qpid::proton
Hello all, In the european aviation community a well know provider of flight data has change its internal AMQP1.0 broker, switching from Apache ActiveMQ to Solace PubSub+. A set of our application but very few in fact use Python3 and interrogate this AMQP broker. So we have too few experience in this matter. I use to maintain a library built above Apache qpid::proton which has work very well while we were accessing Apache ActiveMQ, the former version. Reaching Solace PubSub+, i face some insidious error : ERROR:proton:SMF AD open flow response error (which seems linked to "credential") but i do not succeed to localize . And afterwards, the queue or subscription are empty object . The run() method of proton.reactor.Container instance that i use abruptally end very soon. Has someone already experience that or can help me to choose the area where i am supposed to dig into ? Many thanks . Didier (happy to share my issue ;-) )
