RE: [EXTERNAL] Re: Enabling AMQP 1.0 on Qpid C++ Broker

I ended up figuring it out. Even though I build qpid-cpp-1.36.0 after proton, for some reason in the CMakeCache.txt file, it had BUILD_AMQP:BOOL=OFF. I switched that to ON and now everything is working great. Max From: Jakub Scholz-2 [via Qpid]

Logging ThreadId in Java broker logs

Hi All, After looking logback's PatternLayout, I don't think its possible to log thread id by simply supplying a pattern for it. Has anyone looked into ways to achieve it? I would like to have thread ids in the log lines as well, since it appears to be me that same thread name gets assigned for

can somebody help explain on_sendable and threading (qpid-proton / C++)?

Hi all, I came across a discussion about on_sendable[1] only being called once. This is what I had observed creating my own application. Usually, the first time on_sendable is called, my application doesn't have any messages to send (there is a data structure in RAM, populated from another

RE: [EXTERNAL] Re: Enabling AMQP 1.0 on Qpid C++ Broker

Hmm. I'm on RHEL5 (sadly. We're upgrading to 7 soon). And in my [install location]/lib64/qpid/daemon I only have an ha.so and store.so. I also am not seeing that log message. I'm not sure why I would see that amqp 1.0 was enabled when doing the cmake command but then not be able to find this

Re: Enabling AMQP 1.0 on Qpid C++ Broker

I think that might depend on the OS etc. In my build on CentOS 7 it is in /usr/lib64/qpid/daemon/ ... $ ls /usr/lib64/qpid/daemon/ amqp.so linearstore.so xml.so When the module is loaded, the broker log should print following message when starting: 2017-03-31 18:23:12 [Broker] info Loaded

Enabling AMQP 1.0 on Qpid C++ Broker

Hi, I have a Qpid JMS (1.11.1) client trying to connect to a Qpid C++ (1.36.0) broker. I recently recompiled my qpid broker alongside Qpid Proton and saw the message that AMQP 1.0 support was enabled. When my client tried to connect, they kept getting a "transport connection remotely closed"

RE: Accessing queues with '/' in name in Rest API [qpid java broker 6.0.4]

Hello Rob, Olivier and I re-checked the global address domain feature and it seems it does not resolve the global addresses correctly. When I create the queue 'queueA' on the broker and I set the globalAddressDomains to '/domain/subdomain', and then I register a listener with JMS for the queue

Re: [DISCUSS] Migrate Qpid Broker for Java and Qpid JMS AMQP 0-x Client from SVN to GIT

On 30 March 2017 at 12:32, Lorenz Quack wrote: > +1 on the migration to git. > > Regarding the name of the broker's git repo: > * qpid-broker: I agree with others that this might lead to confusions >with the cpp broker. > * qpid-java-broker: I am worried that legal

Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

Small correction: We are using Proton 0.16.0 with only C++ and Python bindings activated. From: Adel Boutros Sent: Friday, March 31, 2017 9:55:32 AM To: users@qpid.apache.org Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 Hello Ganesh, Please

Re: [Proton C++ 0.16.0] Reconnect and reconnect timer

Thank you Alan, As suggested, we will reconnect when we receive transport closed or connection forced exceptions. Adel Get Outlook for Android From: Alan Conway Sent: Thursday, March 30, 18:54 Subject: Re: [Proton C++ 0.16.0] Reconnect and reconnect timer To: