A couple of suggestions:
- Try running `pluginviewer -c` to see if SCRAM-SHA-256 shows up as supported.
- Make sure e.g. using ccmake that your proton library is correctly
built to include sasl
- Turn on protocol tracing in order to see what mechanisms are
actually being offered by the server
On
On linux, proton uses the cyrus-sasl libraries. Different mechanisms
are often pacakged separately. So if on linux, check that you have the
right cyrus sasl plugin installed.
On Tue, Mar 19, 2024 at 11:33 AM abdelrhman abdelhmaed
wrote:
>
> Hi,
> I am using the qpid proton library to connect to
+1 (built from source including running all tests, ran example against
dispatch router)
On Wed, Nov 1, 2023 at 2:32 PM Timothy Bish wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M18 Qpid protonJ2
> release,
> please give it a test out and vote accordingly.
>
> The
+1 (checked signature and checksum, built from source including all
tests, configured broker via console, ran qpid::messaging, proton cpp
and proton python example programs against it)
On Wed, Aug 16, 2023 at 12:02 PM Tomas Vavricka wrote:
>
> +1
>
> * verified signatures and checksum files
> *
The c++ broker does not support that filter. The proton client should
be able to send it if you use that with service bus. There is an
example that shows how:
https://qpid.apache.org/releases/qpid-proton-0.39.0/proton/cpp/examples/service_bus.cpp.html
On Tue, Aug 1, 2023 at 4:31 AM 工作与生活 wrote:
+1 (checked signature and checksum, build from source including all
tests, ran example against router)
On Mon, Jul 31, 2023 at 3:37 PM Timothy Bish wrote:
>
> Vote remains open awaiting another binding +1 from someone with time to
> give a quick review.
>
> On 7/25/23 11:49, Timothy Bish wrote:
If you follow the link for whichever component you want from this
page: https://qpid.apache.org/releases/index.html#current-releases you
should get download links. I tried a couple and they worked for me.
On Thu, Jul 13, 2023 at 10:51 PM Paul Flores wrote:
>
> Download links are not working.
+1, verified checksum and signature, built from source including all
tests, ran example against router
On Mon, Jun 26, 2023 at 6:05 PM Timothy Bish wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M16 Qpid ProtonJ2
> release,
> please give it a test out and vote
+1, checked checksum and signature, built from source with tests, ran
example against router
On Tue, Jun 27, 2023 at 3:40 PM Robbie Gemmell wrote:
>
> Hi folks,
>
> I have put together a spin for a 1.10.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The staged
+1, checked checksum and signature, built from source with tests, ran
example against router
On Tue, Jun 27, 2023 at 4:34 PM Robbie Gemmell wrote:
>
> Hi folks,
>
> I have put together a spin for a 2.4.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The staged
+1, checked signature and checksum, ran the test script with no failures
On Fri, May 26, 2023 at 4:07 PM Timothy Bish wrote:
>
> Hi folks, gentle reminder that this vote still remains open pending
> one additional binding +1
>
> On Mon, May 22, 2023 at 6:33 PM Timothy Bish wrote:
> >
> > Hi
+1 (checked signature and checksum, build from source including
successful run through all tests, ran example against router 1.19.0)
On Wed, May 17, 2023 at 6:46 PM Robbie Gemmell wrote:
>
> I have put together a spin for a 2.3.0 Qpid JMS client release, please
> give it a test out and vote
+1 (checked signature and checksum, build from source including
successful run through all tests, ran example against router 1.19.0)
On Wed, May 17, 2023 at 5:52 PM Robbie Gemmell wrote:
>
> Hi folks,
>
> I have put together a spin for a 1.9.0 Qpid JMS client release, please
> give it a test out
+1, checked checksum and signature and ran the build script with
podman-test argument.
On Tue, May 9, 2023 at 6:22 PM Timothy Bish wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M8 Qpid
> proton-dotnet release,
> please give it a test out and vote accordingly.
>
>
+1 (Checked signature and checksum, built from source including tests
and ran example against 1.19.0 router)
On Tue, May 2, 2023 at 6:36 PM Timothy Bish wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M15 Qpid ProtonJ2
> release,
> please give it a test out and vote
On Mon, Mar 27, 2023 at 8:10 PM Timothy Bish wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M13 Qpid ProtonJ2
> release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
>
+1, checked checksum and signature, built from source, ran example
against latest router release
On Tue, Jan 10, 2023 at 9:35 PM Timothy Bish wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M12 Qpid ProtonJ2
> release,
> please give it a test out and vote
+1, checked checksum and signature, built from source, ran example
against latest router release
On Tue, Jan 10, 2023 at 6:04 PM Robbie Gemmell wrote:
>
> Hi folks,
>
> I have put together a spin for a 2.2.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The
+1, checked checksum and signature, built from source, ran example
against latest router release
On Tue, Jan 10, 2023 at 5:11 PM Robbie Gemmell wrote:
>
> Hi folks,
>
> I have put together a spin for a 1.8.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The
+1, verified checksum and signature, ran podman-test with no failures
On Mon, Dec 5, 2022 at 9:59 PM Timothy Bish wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M7 Qpid
> proton-dotnet release,
> please give it a test out and vote accordingly.
>
> The source and
+1
checked signature and checksum, ran `build.sh podman-test`, all passed
On Wed, Nov 9, 2022 at 1:25 PM Robbie Gemmell wrote:
>
> On Tue, 8 Nov 2022 at 19:46, Timothy Bish wrote:
> >
> > Hi folks,
> >
> > I have put together a release candidate for a 1.0.0-M6 Qpid
> > proton-dotnet release,
>
+1
checked signature and checksum, ran mvn install, untarred the target
and ran the example within it against qdrouterd 1.19
On Wed, Nov 9, 2022 at 2:55 PM Robbie Gemmell wrote:
>
> On Tue, 8 Nov 2022 at 18:00, Timothy Bish wrote:
> >
> > Hi folks,
> >
> > I have put together a release
Hello,
>
> would a migration from qpidd to artemis require changes on the clients ?
> Specifically, clients use python-qpid-proton bindings. Would we need to
> rewrite client's codes ?
>
> Cheers,
>
> On 10/10/22 10:32, Gordon Sim wrote:
> > ActiveMQ Artemis
&g
.
On Mon, Oct 10, 2022 at 8:50 AM Михаил Иванов wrote:
>
> Which broker then is supposed to be used instead?
>
> On 10.10.2022 10:31, Gordon Sim wrote:
> > In my opinion, in the absence of any volunteers able to spend some
> > amount of time on it, we should 'archive' it
In my opinion, in the absence of any volunteers able to spend some
amount of time on it, we should 'archive' it in some way (i.e. ensure
that the code remains available, but that it is clear from the website
etc that it is no longer maintained).
On Sat, Oct 8, 2022 at 8:44 PM Michael Ivanov
I don't know of any existing benchmarks. However my advice would be to
just go ahead and move. If you are concerned, you can do some simple
benchmarking with your actual application, but I doubt there will be
any issue with performance.
On Wed, Oct 5, 2022 at 10:48 PM rammohan ganapavarapu
If you want to completely disable the 5672 port, use --listen-disable tcp.
The require-encryption option only works when authentication is enabled.
On Wed, Oct 5, 2022 at 4:14 PM Michael Ivanov wrote:
>
> Greetings!
>
> I observed strange qpidd behavior. It is started from systemd with
On Wed, Sep 7, 2022 at 8:13 AM Yuanyuan Feng
wrote:
> Is it possible to use QPID messaging API to connect to a service bus
> namespace and then send/receive messages to/from a queue on demand?
I don't believe anyone has ever done so.
In general I would advise against starting new projects
+1, built from source including all tests
On Tue, Aug 30, 2022 at 7:24 PM Robbie Gemmell wrote:
>
> Hi folks,
>
> I have put together a spin for a Qpid Proton-J 0.34.0 release, please
> test it and vote accordingly.
>
> The files can be grabbed from:
>
On Tue, Jul 26, 2022 at 3:29 PM Turritopsis Dohrnii Teo En Ming
wrote:
> How do I install and use Apache Qpid?
Qpid comprises various different components. What component(s)
specifically are you interested in? I would advise going to
https://qpid.apache.org/ to find out more.
On Wed, Jul 6, 2022 at 2:26 PM Arjee Jacob wrote:
>
> Thank you. Sorry, This may be a delayed response.
> We have qpidd running on the device as a server, and we have 4 clients.
> 3 clients are qpid C++ clients, using a qpid topic.
> And 1 Client is a python script, which uses qpid proton using
I would not advise starting any project using the qpid messaging c++
api unless you are able and willing to invest time in maintaining the
code yourself. As far as the active development activity within qpid
is concerned, that api has been superceded by the proton c++ api.
On Fri, Jul 1, 2022 at
On Wed, Jun 29, 2022 at 4:53 PM Tiaan Wessels wrote:
> Thanks. When a topic varies per message, would it not be better to be able
> to set it per message. With the current design it seems one would need to
> create a new session per message if you want to vary the topic? It seems
> the only
On Wed, Jun 29, 2022 at 1:45 PM Tiaan Wessels wrote:
> When AMQP 1.0 is activated in a QPID Messaging API C++ program, what is the
> correct way to set the topic of a message to be sent to a broker ?
> The protocol is activated by protocol:'amqp1.0' in connection options.
> Also. is there a way
+1
- Verified signature and checksum
- Built from source including running tests
- Ran Hello World example against 1.19.0 router
On Tue, Jun 28, 2022 at 11:50 AM Robbie Gemmell
wrote:
>
> On Mon, 27 Jun 2022 at 17:05, Timothy Bish wrote:
> >
> > Hi folks,
> >
> > I have put together a release
On a server, that log suggests that something is opening a socket to
the 5672 port, but then not actually transmitting anything over it.
E.g. it could be some kind of L4 probe.
On Mon, Jun 6, 2022 at 8:35 AM Arjee Jacob wrote:
>
> Hey there,
>
> I am getting a message in my logs that says
>
Have you seen
https://qpid.apache.org/releases/qpid-proton-0.37.0/proton/python/docs/tutorial.html
and
https://qpid.apache.org/releases/qpid-proton-0.37.0/proton/cpp/api/tutorial_page.html
?
On Wed, Jun 1, 2022 at 5:45 AM Arjee Jacob wrote:
>
> Dear all,
>
> I am not sure if this is the right
I built from source using `mvn clean package`, then I untar the
tarball in the target directory. That contains th examples with the
pom file, but maven complained about not finding a parent. This may be
the wrong approach but is essentially how I tested the previous
version and also the original
+1, built from source including all tests and ran example against router
(My usual approach here did not work as the
apache-qpid-protonj2-1.0.0-M6-bin.tar.gz tarball which I 'install'
from after building did not have a top level maven project file, so
running maven against the examples failed.
On Mon, May 23, 2022 at 5:05 PM Tiaan Wessels wrote:
> Is it possible to connect with qpid messaging api c++ via ssl proxy to an
> AMQP broker?
It depends on the exact nature of the proxying. If the proxy uses SNI
information to route the connection, but leaves the encryption end to
end, that
On Thu, Apr 28, 2022 at 9:58 PM ONeil, Jerome wrote:
> So that's grand. I need to control the binding with more detail, though, and
> for the life of me I can't figure out how to do it. I've tried controlling
> on the URL. I've tried Filters and Selectors. I have tried a variety of
>
On Tue, Apr 5, 2022 at 8:40 PM Timothy Bish wrote:
> I have put together a release candidate for a 1.0.0-M5 Qpid ProtonJ2
> release,
> please give it a test out and vote accordingly. I made a mistake and
> went a step
> to far when staging the maven bits and hit release instead of just
> closing
On Thu, Mar 31, 2022 at 1:55 PM rahul.sin...@morganstanley.com
wrote:
>
> Many thanks Gordon. I tried using the selector while creating the Receiver
> for response queue (as per the example given
> https://lists.apache.org/thread/95ozl3hxf0cqzt0nxgbvwroddx39kq1w)
> However, I get below
On Thu, Mar 31, 2022 at 11:30 AM rahul.sin...@morganstanley.com
wrote:
> 2) For the longer term/better solution, I will start looking into selector.
> Is this within qpid C++ or proton layer. Any quick pointer will be highly
> appreciated.
For proton C++:
On Thu, Mar 31, 2022 at 11:06 AM rahul.sin...@morganstanley.com
wrote:
> How do we ensure the first receiver has released it? Is it invocation of
> Session::acknowledge(msg) which makes it available to other receivers?
No, acknowledging the message will remove it permanently from the
queue. To
AMQP 1.0 doesn't really support what you are trying to do, which if I
understand it correctly, is to have many receivers peek at messages in
the queue and only remove those that are relevant to them. There is
the concept of a delivery mode, but no way to 'acquire' a copied
message. For the default
On Tue, Mar 15, 2022 at 5:40 PM Robbie Gemmell wrote:
> I have put together another spin for a Qpid Proton 0.37.0 release,
> please give it a test out and vote accordingly.
>
> The files can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton/0.37.0-rc2/
I checked signature and
On Thu, Mar 17, 2022 at 1:14 AM Ken Giusti wrote:
> Please cast your vote on this thread to release RC2 as the official
> Qpid Dispatch Router version 1.19.0.
>
> RC2 of Qpid Dispatch Router version 1.19.0 can be found here:
> https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.19.0-rc2/
+1
On Fri, Mar 18, 2022 at 9:35 AM Jiri Daněk wrote:
>
> On Fri, Mar 18, 2022 at 10:20 AM Roddie Kieley wrote:
>
> > Has anyone else been testing with python 3.10? I see that we specify
> > python 3.6+ as per:
> >
> > -- Found Python: /usr/bin/python3.10 (found suitable version "3.10.0",
> >
On Tue, Feb 8, 2022 at 8:11 PM Pete Fawcett wrote:
> Would you prefer that I submit a Pull Request for the current fixes or wait
> until further changes are made?
Either way
-
To unsubscribe, e-mail:
On Fri, Jan 14, 2022 at 10:36 AM Pete Fawcett wrote:
> I tried this but it didn't, initially, fix the problem.
> It turns out that the current exception handling is causing the link to be
> closed from within Connection object doDeliveryUpdated
>
On Thu, Jan 6, 2022 at 8:56 PM Pete Fawcett wrote:
> *Questions:*
>
> Firstly, a simple work around is to check the link pointer when moving
> delivery pointers from 'pending' to completed and discarding them if the
> 'link' is NULL . Does this suffice?
I think that would probably work. However
On Wed, Dec 15, 2021 at 5:31 PM Robbie Gemmell wrote:
> I have put together a spin for a 0.60.1 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.60.1-rc1/
+1,
On Wed, Dec 15, 2021 at 4:50 PM Robbie Gemmell wrote:
> I have put together a spin for a 1.4.1 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.4.1-rc1/
+1,
On Mon, Dec 13, 2021 at 6:32 PM Robbie Gemmell wrote:
> I have put together a spin for a 1.4.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.4.0-rc1/
+1
*
On Tue, Nov 30, 2021 at 12:26 PM Andy Gibson wrote:
> My team are currently in the process of replacing header bindings with
> selectors. We're using a python3 proton client and the C++ qpid broker.
> We're used to being able to use the QMF console to see what header bindings
> are being used
On Tue, Nov 16, 2021 at 9:36 PM Ken Giusti wrote:
> Please cast your vote on this thread to release RC1 as the official
> Qpid Dispatch Router version 1.18.0.
>
> RC1 of Qpid Dispatch Router version 1.18.0 can be found here:
> https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.18.0-rc1/
+1
On Tue, Nov 16, 2021 at 12:17 PM Kai wrote:
> I am trying to set some application properties on a message to be sent
> using Qpid Python 0.36 using the following code:
> msg = Message(
> body="the body",
> properties={
> "status": 200
>
On Mon, Nov 15, 2021 at 6:32 PM Alec Liu wrote:
> Is there anyway that for a client program which linking with a qpid
> dispatch to receive all messages for different addresses? Like using some
> kind of wildcard address, etc.
No, wildcard based routing is not supported at this time.
+1 (build as a container and ran all tests)
On Thu, Oct 28, 2021 at 9:36 PM Kim van der Riet wrote:
>
> Hi,
>
> I have assembled a release of Qpid Interop Test 0.3.0. The proposed release
> (RC1) is available at:
> https://dist.apache.org/repos/dist/dev/qpid/interop-test/0.3.0-rc1/
>
> Issues
On Thu, Oct 28, 2021 at 10:30 PM Ken Giusti wrote:
> Please cast your vote on this thread to release RC1 as the official
> Qpid Dispatch Router version 1.17.1.
>
> RC1 of Qpid Dispatch Router version 1.17.1 can be found here:
> https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.17.1-rc1/
>
>
I would like to suggest a possible bug fix release, 1.17.1. I have two
fixes I would like to include in that - DISPATCH-2257 and
DISPATCH-2259 - in order to make those fixes available more easily to
those who need them before the 0.18.0 release. Any other bugs anyone
feels could/should be
This is because you are setting 'examples' to be a topic exchange, and
so the messages sent are pre-settled by default (which the example
application is not checking before trying to accept). The example is a
simple one intended to work with a queue (or queue like thing).
On Wed, Oct 13, 2021 at
On Wed, Sep 29, 2021 at 1:25 AM EXT-Walsh, Jody R
wrote:
> I am able to connect and send to a queue. To send to a topic, I need to
> prefix the address with "topic://", but this is not accepted by the qpid
> messaging api.
You need to add inner quotes around the topic, so e.g.
On Wed, Sep 22, 2021 at 8:11 PM Adrian Florea wrote:
> You can take a look at:
>
> https://azure.github.io/amqpnetlite/articles/azure_eventhubs.html
>
> Look at the "Filter" section.
For an example of setting a filter with proton c++:
On Wed, Sep 22, 2021 at 6:54 PM Arun Koshal wrote:
> I plan to use Apache qpid proton C++ API for receiving messages from Azure
> Event hub. I am able to implement a client and fetch the events. The
> problem is, whenever I restart my clients it reads all the events from the
> event hub.
>
> A
Is the broker disconnecting the client with the timed out error? Or is
it the client disconnecting from the broker?
My initial thought was that
https://issues.apache.org/jira/browse/PROTON-2422 might be relevant,
but that results in heartbeats *not* being sent by proton. Did you
notice any such
On Tue, Aug 24, 2021 at 9:39 PM Alex Rudyy wrote:
> I built release artefacts for Qpid Broker-J version 8.0.6 RC1.
> Please, give them a test out and vote accordingly.
>
> The source and binary archives can be found at:
> https://dist.apache.org/repos/dist/dev/qpid/broker-j/8.0.6-rc1/
+1, built
On Tue, Aug 3, 2021 at 9:15 PM Svrankovic11
wrote:
> I would like to connect to Qpid C++ broker 1.39.0 using different clients
> that run AMQP 1.0 and 0-10. How can I turn on both protocol versions for Qpid
> C++ Broker?
0-10 is always on, whether you want it or not
1.0 is built as a plugin;
On Tue, Jul 13, 2021 at 1:10 PM rahul.sin...@morganstanley.com
wrote:
> I need it to ensure I can run it on a specific CPU core.
Ok, running pstack against the process should show you the thread id for that.
-
To unsubscribe,
On Tue, Jul 13, 2021 at 12:23 PM rahul.sin...@morganstanley.com
wrote:
> I am using qpid-cpp-1.39.0 and want to create multiple topics and handle
> incoming data in the most efficient way. What I have understood is that the
> qpid::messaging::Connection, Session and Receiver are all created in
On Fri, Jul 9, 2021 at 4:00 PM rahul.sin...@morganstanley.com
wrote:
> I haven't look deeper but it would be really great if you can help locating
> where actually the generated code gets in. Does it go under the install
> directory or the source directory where we have qpid-cpp-1.39.0 folder.
On Thu, Jul 8, 2021 at 7:44 PM Steve Charbonneau
wrote:
> Can someone confirm if the Qpid C++ Broker (v1.39) is also supported for
> running on RHEL 8 ?
I can confirm it will build and run on RHEL8. However, work on that
component has mostly stopped. Have you considered the java broker? Or
one
On Fri, Jul 9, 2021 at 12:39 PM rahul.sin...@morganstanley.com
wrote:
> Building qpid-proton is fine without Ruby. However, when I try to build
> qpid-cpp-1.39.0, cmake gives below error -
>
> CMake Error at src/CMakeLists.txt:87 (message):
> Can't locate ruby, needed to generate amqp 0-10
On Fri, Jul 9, 2021 at 10:35 AM rahul.sin...@morganstanley.com
wrote:
>
> Hello,
> I have recently build qpid-proton-0.34.0 and qpid-cpp-1.39.0 and need them
> for AMQP1.0. I removed the BINDINGS for RUBY ( -DBUILD_BINDING_RUBY=OFF while
> building qpid-cpp-1.39.0 AND -DBUILD_RUBY=OFF while
On Mon, Jul 5, 2021 at 5:25 PM Robbie Gemmell wrote:
> I have put together a spin for a 1.1.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.1.0-rc1/
+1 (ran
would be highly appreciated.
>
> Best Regards,
> Rahul
> -Original Message-
> From: Robbie Gemmell
> Sent: 01 July 2021 15:01
> To: users
> Subject: Re: QPID C++ Subscribing to a topic
>
> On Thu, 1 Jul 2021 at 13:18, Gordon Sim wrote:
> >
> &g
On Thu, Jul 1, 2021 at 1:08 PM rahul.sin...@morganstanley.com
wrote:
> 1. As per Robbie's suggestion, I have tried adding topic:// in the past as
> well but the address and name selection gets chopped off from our end (after
> topic: ) in the outgoing AMQP frame to Broker.
>
> Our Code -
>
( " is not authorized to
> create: queue://ID.ExampleTopic" )
> From the QPID API usage perspective, do I need to invoke something else to
> make the topic usage clear. I also experimented with creating a Sender with
> same topic name but I get the same error.
>
> Be
+1
On Thu, Jul 1, 2021 at 12:23 AM Alex Rudyy wrote:
>
> Hi folks,
>
> I'd like to call a vote to offer commit rights to Tomas Vavricka
>
> Tomas has been contributing to Qpid Broker-J for a couple of years
> starting from 2017. In particular, he submitted an initial
> implementation of the
On Wed, Jun 30, 2021 at 9:40 AM rahul.sin...@morganstanley.com
wrote:
> After being able to establish the connection with the broker at other end, we
> try to subscribe to a given topic. For this, we create the receiver with
> string mapping to the topic. ( Id.ExampleTopic ), where Id is the
On Mon, Jun 28, 2021 at 7:33 PM Ken Giusti wrote:
> Please cast your vote on this thread to release RC1 as the official Qpid
> Dispatch Router version 1.16.1.
>
>
> RC1 of Qpid Dispatch Router version 1.16.1 can be found here:
>
>
>
>
On Tue, Jun 29, 2021 at 9:19 AM rahul.sin...@morganstanley.com
wrote:
> Many thanks for your help. I got it connected now...
Great! \o/
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands,
On Mon, Jun 28, 2021 at 7:43 PM rahul.sin...@morganstanley.com
wrote:
> On further debugging, we find that the SSL Connection is failing. The error
> reported is -
> [System] debug Exception constructed: Failed: NSS error [-8172]
>
On Mon, Jun 28, 2021 at 2:45 PM rahul.sin...@morganstanley.com
wrote:
> I don’t get url exception if I use example.xyz.com:5671 format. But still, I
> receive Connect failed error.
>
> "caught std::exception Connect failed to amqp:ssl::example.xyz.com:5671
> Exceeded retries"
>
> At the moment,
48)
>
> We have been by the broker at the other end that fully qualified domain names
> are necessary for certificate handshake.
>
> Best Regards,
> Rahul
> -Original Message-
> From: Gordon Sim
> Sent: 25 June 2021 11:40
> To: users@qpid.apache.org
> Subject
On Fri, Jun 25, 2021 at 9:50 AM rahul.sin...@morganstanley.com
wrote:
> The Apache QPID C++ Messaging library states the below rule for url
>
> /** Simple recursive-descent parser for this grammar:
> url = ["amqp:"][ user ["/" password] "@" ] protocol_addr *("," protocol_addr)
> protocol_addr =
On Thu, Jun 24, 2021 at 12:08 PM rahul.sin...@morganstanley.com
wrote:
> ldd for libqpidmessaging.so gives me libqpid-proton-core.so.10 alongwith
> other qpid libs- libqpidtypes.so.1, libqpidclient.so.2 and libqpidcommon.so.2.
> However, until I uncomment " protocol-defaults=amqp1.0,amqp0-10"
conf to
> select amqp 1.0
> protocol-defaults=amqp1.0,amqp0-10
>
> Any suggestions about the correctness of the API usage would be really
> appreciated.
> Further, are there any ways to get logs out of QPID libraries so that I can
> know how far it is going.
>
> Best Regards,
&
t/output error)
> Caught std::exception Invalid value for module-dir: Input/output error: Can't
> check directory PATH_ON_COMPILE_MACHINE/install/lib64/qpid/client
>
> Best Regards,
> Rahul
> -Original Message-
> From: Gordon Sim
> Sent: 21 June 2021 13:32
> To: us
You should not need to have any client module directory. My first
guess is that it is perhaps a permissions issue. Is your application
running as a user able to list files under the
/lib64/qpid directory?
(The exception seems to come from stat() returning an error other than ENOENT).
On Mon, Jun
+1 (ran tests, c++ qpid::messaging client and proton python examples
against it).
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
There have been a couple of fixes since the 1.16.0 release that are
useful for users of the tcp support. Making those available as a
1.16.1 seems like a good idea to me. The fixes I would suggest are:
DISPATCH-2142
DISPATCH-2097
DISPATCH-1878 (last commit)
On Fri, Jun 4, 2021 at 5:40 AM Namitha, Nancy wrote:
>
> Thank Robbie and Gordon for the suggestion, when I debug further, I observed
> that Consuming application was blocked even though the messages were there in
> the queue it was unable to receive the messages, when I restart the consuming
On Mon, May 24, 2021 at 11:54 AM Robbie Gemmell
wrote:
> On Wed, 19 May 2021 at 16:41, Robbie Gemmell wrote:
> >
> > Hi folks,
> >
> > I have put together a spin for a 1.0.0 Qpid JMS client release,
> > please give it a test out and vote accordingly.
> >
> > The source and binary archives can be
I would advise using the qpid java broker or one of the activemq brokers.
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
On Wed, May 19, 2021 at 3:34 PM Namitha, Nancy wrote:
> Is Broker - J optimized for the below mentioned scenario.
I believe the java broker will indeed perform better for synchronous
publish. Best thing is to run a quick test though.
On Wed, May 19, 2021 at 5:09 AM Namitha, Nancy wrote:
>I have deployed Qpid Broker C++ v 1.39 package on Ubuntu 18.4.
> And have enabled persistence using linearstore libraries. And I am using
> AMQP 1.0 Client Library for GO (https://github.com/Azure/go-amqp) for
> sending
On Mon, May 10, 2021 at 6:01 PM Ken Giusti wrote:
> Please cast your vote on this thread to release RC1 as the official Qpid
> Dispatch Router version 1.16.0.
+1 (verified signature and checksum, built from source ran all system
tests and installed, ran python examples against router)
On Tue, Apr 6, 2021 at 5:48 PM Robbie Gemmell wrote:
>
> Hi folks,
>
> I have put together a spin for a 0.58.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
>
1 - 100 of 2568 matches
Mail list logo
