Re: Dispatch: ‘posix_memalign’, declared with attribute warn_unused_result [-Werror=unused-result]

Thanks Ted. My build seems to work fine again now after your fix. J. On Tue, Sep 20, 2016 at 1:51 PM, Ted Ross wrote: > Jakub, > > This is a bug in the DISPATCH-511 update. I'll get it fixed. > > -Ted > > On 09/19/2016 04:00 PM, Jakub Scholz wrote: > >> Hi, >> >> I seem to

Re: Help! ->qpid::Exception what(): Invalid argument (../include/qpid/sys/posix/Mutex.h:116): QPID - 6416?

We are grasping at straws. Ran valgrind and it appears issue is occurring in Connection destructor (~ConnectionIMPL ?). I will post valgrind output messages when I get them copied over. In searching for like issues we came across QPID-6416. But that fixed in 0.31, right? We did not see any

RE: Testing failover on dispatcher/java-broker cluster

Hello Ted, I confirm the fix solved the issue. Would it be possible to do a 0.6.2 release? We cannot compile newer versions of Proton (We currently use 0.12.2) due to lack of resources from our side and we really need this fix for our tests. Regards, Adel > Subject: Re: Testing failover on

Re: Dispatch: ‘posix_memalign’, declared with attribute warn_unused_result [-Werror=unused-result]

Jakub, This is a bug in the DISPATCH-511 update. I'll get it fixed. -Ted On 09/19/2016 04:00 PM, Jakub Scholz wrote: Hi, I seem to have problems with building latest version of Qpid Dispatch (from master) on some systems. In particular on Ubuntu it seems to crash with the error below which

Re: [QPID C++][Java JMS client] Data gets corrupted when sent to the server over SSL

Hi, I am the one doing the client end using qpid java library. I can confirm that this problem doesn't seem to exists when using the AMQP 1.0 version 0.11.0 library. -- View this message in context:

Re: async send message blocked forever

On 20/09/16 09:39, 634749...@qq.com wrote: thanks! the message is not large, the depth of the queue information flowed: The stack trace looks like the sender is waiting for confirmation of previously sent messages. As the broker

Re: help : special characters in qpid password

I think you should be able to escape characters in the username / password with % encoding... so something like amqp://PQ-RST-UV-W:VPN%3amwrst@clientid/localhost?brokerlist=... should work (where %3a is the encoding of the : character). The only problem I see (which shouldn't cause you an

Re: help : special characters in qpid password

Hi All *I have java qpid broker 0.32 installed and i am connecting to it from spring java client using 0.32 java library of qpid.* I have amqp port linked with LDAP for simple authentication. The username is PQ-RST-UV-W password is VPN:mwrst When I give this username and password in qpid

help : special characters in qpid password

Hi All I have amqp port linked with LDAP for simple authentication. The username is PQ-RST-UV-W password is VPN:mwrst When I give this username and password in qpid CLIENT url amqp://PQ-RST-UV-W:VPN:mwrst@clientid/localhost?brokerlist=... The authentication fails. When investigated its

Re: async send message blocked forever

Is any information useful? Look forward to your reply，thanks！ -- View this message in context: http://qpid.2158936.n2.nabble.com/async-send-message-blocked-forever-tp7650922p7650927.html Sent from the Apache Qpid users mailing list archive at Nabble.com.

Re: async send message blocked forever

thanks! the message is not large, the depth of the queue information flowed: -- View this message in context: http://qpid.2158936.n2.nabble.com/async-send-message-blocked-forever-tp7650922p7650926.html Sent from the Apache Qpid

Re: async send message blocked forever

On 20/09/16 09:04, 634749...@qq.com wrote: HI: I user the c++ broker(verison 0.34) and the c++ API on windows,but I found the send() function of sender maybe blocked forever, I did not start the flow stop,and send message async; example code: Sender sender =

async send message blocked forever

HI: I user the c++ broker(verison 0.34) and the c++ API on windows,but I found the send() function of sender maybe blocked forever, I did not start the flow stop,and send message async; example code: Sender sender = session.createSender(address); sender.setCapacity(1000);