Request for inclusion: PROTON-1212

This is a very simple fix, and potentially a very bad bug. Although I don't think the bad code is actually used in 0.13, I haven't scoured the code 100%. https://issues.apache.org/jira/browse/PROTON-1212 https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=23d2686 Andrew --

RE: [qpid-dispatch] No load balancing if destination is available on 2 brokers

Hello Robbie, Ted, After checking the JMS client doc, I found an option which could be provided in the url when the sender connects to force asynchronous sending "jms.forceAsyncSend=true". It works fine with JMS 1.1 (https://qpid.apache.org/releases/qpid-jms-0.8.0/docs/index.html) @TedI agree wi

Re: [qpid-dispatch] No load balancing if destination is available on 2 brokers

The client will currently send persistent messages synchronously by default and non-persistent messages asynchronously by default, with configuration (http://qpid.apache.org/releases/qpid-jms-0.9.0/docs/index.html#jms-configuration-options) to allow you to change either. In terms of asynchronous

Re: [qpid-dispatch] No load balancing if destination is available on 2 brokers

Balanced is the default mode and the most appropriate for anycast delivery. Having a sharded queue and a single synchronous producer is not a very useful real-world scenario. If you had many synchronous producers, balanced mode would spread the deliveries across the brokers. I hope I answere

RE: [qpid-dispatch] No load balancing if destination is available on 2 brokers

Allow me to add that asynchronous sending is part of JMS 2.0 which is still in alpha mode and it is not implemented in Qpid JMS client. So I can't really use it. Adel > From: adelbout...@live.com > To: users@qpid.apache.org > Subject: RE: [qpid-dispatch] No load balancing if destination is availa

RE: [qpid-dispatch] No load balancing if destination is available on 2 brokers

I agree this is not a bug. However, what mode would you recommend using? and what are the advantages and disadvantages of each mode? Adel > Subject: Re: [qpid-dispatch] No load balancing if destination is available on > 2 brokers > To: users@qpid.apache.org > From: tr...@redhat.com > Date: Tue,

Re: [VOTE] Release Qpid Java 6.0.3 (RC3)

On 19/05/16 12:04, Oleksandr Rudyy wrote: Hi all, I have built RC3 for 6.0.3 Qpid Java Components. The following changes have been made since RC2: QPID-6096 : java broker doesn't indicate that port is already in use QPID-7255

Re: [qpid-dispatch] No load balancing if destination is available on 2 brokers

Adel, Ganesh just reproduced your symptom. The issue is that your sender is synchronous. The send call blocks until the sent message is settled. Because of this, when a message is delivered to the router, there are no unsettled deliveries on either router so it picks the first one as the de

RE: [qpid-dispatch] No load balancing if destination is available on 2 brokers

Hello Ted, Could it be related to AMQP 1.0? It worked for me using simple_send.py. Whereas using JMS and another python script, I have the issue. python send script attached (./sender.py -b amqp://localhost:10400 -a cluster.queue -m 100) Regards,Adel > From: adelbout...@live.com > To: users@qpid

Re: Lock-up in waitForCompletion()

On 24/05/16 15:28, Toralf Lund wrote: On 24/05/16 13:22, Gordon Sim wrote: On 24/05/16 12:20, Gordon Sim wrote: if you run: qpid-config queues and: qpid-send -q I think that should allow us to see if there is any queue near its limit. qpid-config queues says Queue Name Attribute

Re: Lock-up in waitForCompletion()

On 24/05/16 13:22, Gordon Sim wrote: On 24/05/16 12:20, Gordon Sim wrote: On 24/05/16 10:39, Toralf Lund wrote: Hi, I have a program that sends messages to a topic exchange using the C++ messaging API. The messages are generally directed to a single receiver queue. I thought it worked just fin

RE: [qpid-dispatch] No load balancing if destination is available on 2 brokers

Typo: Replace "green-lx-slave1" with "localhost" > From: adelbout...@live.com > To: users@qpid.apache.org > Subject: RE: [qpid-dispatch] No load balancing if destination is available on > 2 brokers > Date: Tue, 24 May 2016 14:36:50 +0200 > > I am using the JMS client version 0.8.0ConnectionFacto

RE: [qpid-dispatch] No load balancing if destination is available on 2 brokers

I am using the JMS client version 0.8.0ConnectionFactory connectionFactory = new JmsConnectionFactory("amqp://green-lx-slave1:10400"); Connection connection = connectionFactory.createConnection(); try { //Create producer on Dispatcher connection.start(); Session session = connection.c

Re: [qpid-dispatch] No load balancing if destination is available on 2 brokers

Adel, How are you sending the messages? In my test, I used simple_send.py to send 500 messages. It looks like you've got everything set up correctly. -Ted On 05/24/2016 08:03 AM, Adel Boutros wrote: *a/fter the autolinks are activated/* *qdstat -a* Router Addresses class addr

Re: [qpid-dispatch] No load balancing if destination is available on 2 brokers

*a/fter the autolinks are activated/* *qdstat -a* Router Addresses class addr phs distribin-proc local remote cntnr in out thru to-proc from-proc =

Re: [qpid-dispatch] No load balancing if destination is available on 2 brokers

Can you provide the output of "qdstat -a" and "qdstat -l" at the time right after the autolinks are activated, and again after the test is run and all the messages went to one broker? Thanks, -Ted On 05/24/2016 05:26 AM, Adel Boutros wrote: Here is the forgotten attachement. The last incomin

Re: Lock-up in waitForCompletion()

On 24/05/16 12:20, Gordon Sim wrote: On 24/05/16 10:39, Toralf Lund wrote: Hi, I have a program that sends messages to a topic exchange using the C++ messaging API. The messages are generally directed to a single receiver queue. I thought it worked just fine (as always), but now I notice that i

Re: Lock-up in waitForCompletion()

On 24/05/16 10:39, Toralf Lund wrote: Hi, I have a program that sends messages to a topic exchange using the C++ messaging API. The messages are generally directed to a single receiver queue. I thought it worked just fine (as always), but now I notice that it gets stuck a short while after start

Lock-up in waitForCompletion()

Hi, I have a program that sends messages to a topic exchange using the C++ messaging API. The messages are generally directed to a single receiver queue. I thought it worked just fine (as always), but now I notice that it gets stuck a short while after start-up. Simply put, the sender.send()

RE: [qpid-dispatch] No load balancing if destination is available on 2 brokers

Here is the forgotten attachement. The last incoming connections correspond to the consumer and producer registering. > Date: Tue, 24 May 2016 02:24:00 -0700 > From: adelbout...@live.com > To: users@qpid.apache.org > Subject: Re: FW: [qpid-dispatch] No load balancing if destination is > availabl

Re: FW: [qpid-dispatch] No load balancing if destination is available on 2 brokers

Hello Ted, I retried this morning on the master trunk and still have the same issue. I am attaching the logs generated which shows clearly that all autolinks are activated and both consumer and producer are connected to the dispatcher. Here is the stats provided by the qdstat command *qdstat -b

Re: connect Qpid broker using the latest amqp 1.0 qpid-jms-client-0.9 ssl

On 24 May 2016 at 09:26, Gordon Sim wrote: > On 24/05/16 03:37, Steven wrote: >> >> Hello,every one, >> >> I was using the latest amqp 1.0 api to connect to broker ssl,The >> connection >> url is >> connectionfactory.qpidConnectionfactory = >> >> amqps://192.168.82.57:5673?transport.trustStoreLoca

Re: connect Qpid broker using the latest amqp 1.0 qpid-jms-client-0.9 ssl

On 24/05/16 03:37, Steven wrote: Hello,every one, I was using the latest amqp 1.0 api to connect to broker ssl,The connection url is connectionfactory.qpidConnectionfactory = amqps://192.168.82.57:5673?transport.trustStoreLocation=F:\\AMQP\\QpidSSL\\clientts.jks&transport.trustStorePassword=1234

connect Qpid broker using the latest amqp 1.0 qpid-jms-client-0.9 ssl

Hello,every one, I was using the latest amqp 1.0 api to connect to broker ssl,The connection url is connectionfactory.qpidConnectionfactory = amqps://192.168.82.57:5673?transport.trustStoreLocation=F:\\AMQP\\QpidSSL\\clientts.jks&transport.trustStorePassword=123456 it reported the following error