Hi,
We're using proton 14, and qpidd 1.35. We probably have bad routing at one
spot from a proton client to a qpidd broker on another machine, and the client
is slow to see the queue (it fails out with "amqp:no-found"), even though the
broker has been running steadily and the ping time is ~50
On 01/13/2017 10:08 AM, Adel Boutros wrote:
Hello Tim,
I took a look on the master brunch of the github repo and indeed it seems to be
fixed.
Regards,
Adel
I made some additional changes to make the error reporting more consistent.
From: Timothy Bish
S
Hello Tim,
I took a look on the master brunch of the github repo and indeed it seems to be
fixed.
Regards,
Adel
From: Timothy Bish
Sent: Friday, January 13, 2017 3:30:59 PM
To: users@qpid.apache.org
Subject: Re: [Qpid JMS 0.11.1] Nullpointer exception when
On 01/13/2017 08:41 AM, Adel Boutros wrote:
Hello,
While playing around with the JMS API, we noticed that if an empty string is passed to
the JmsConnectionFactory constructor, it will throw back a NullPointerException because
it tries to access the ".toString" of a NULL URL (See createURI).
Hello Rob,
You're right, there was something strange in my question. I realized that
it was not clear for me neither.
I explored different strategies for the consumer broadcast. One was indeed
to have the consumer to receive all the messages from the moment it
connects and not keep the messages on
Thank you for the reply. Yes, it really helped.
I spent more time investigating the metrics and found out that the
throughput is lower in my benchmark as the same time as the latency is
higher.
The higher latency can be explained with the network indirection.
Each producer sends the messages sequen
Hello,
While playing around with the JMS API, we noticed that if an empty string is
passed to the JmsConnectionFactory constructor, it will throw back a
NullPointerException because it tries to access the ".toString" of a NULL URL
(See createURI).
Do you agree that it would be better to thro
On 12 January 2017 at 15:21, Lorenz Quack wrote:
> Hello,
>
> Robbie, Rob, Alex, and I had a discussion on IRC yesterday about the Qpid
> Broker for Java support for JMS 2.0 shared subscriptions.
> This is a follow-up from that discussion.
>
> We discussed that it would be helpful to have a docume
