Receiver fetch mybey block forever

hello! I use the c++ broker and c++ client api(version 0.34);the broker running on centos,and the client on windows server 2008; if the network is not stability between client and broker , I found the receive fetch() function maybe block forever. eg： Receiver receiver; Message

some questions about Receiver get() and fetch() function

hello! I use the c++ broker and c++ client api(version 0.34),Now I have some question about Receiver funtion fetch and get; call example: Session session; Receiver receiver; receive = session.createReceiver(); receive.setCapacity(1000); So I receive message from

[RESULT] [VOTE] Release Qpid JMS client 0.11.0

There were 5 binding +1 votes, and no other votes received. The vote has passed. I will add the archives to the dist release repo and release the maven staging repo shortly. The website will be updated later after the artifacts have had time to sync to the mirrors and maven central. Robbie

Re: [VOTE] Release Qpid JMS client 0.11.0

On 5 September 2016 at 16:47, Robbie Gemmell wrote: > Hi folks, > > I have put together a spin for a 0.11.0 Qpid JMS client release, please > test it and vote accordingly. > > The source and binary archives can be grabbed from: >

Re: [proton-j] Connections per client

That doesn't sound expected and I've likely done something vaguely similar with it in the past (minus the verticles). I'd say that sounds like a bug in either your [server] usage, the vert.x wrapping of proton-j, vert.x (/netty, though seems unlikely), and then maybe proton-j itself (which as

[Qpid Java Broker 6.0.x] Random failure in queue creation/deletion using REST calls

Hello guys, As I mentioned in my previous post, I am having some random REST call failures when deleting and creating a queue. I was able to have a smaller test code but still the error is very random. I launch my test code 10 000 times to get the exception: The failure occurs sometimes at run