The Apache Qpid community is pleased to announce the immediate availability
of version 6.0.1 for Apache Qpid Java Broker and JMS Client for AMQP
0-8...0-10.
This release incorporates a number of defect fixes and enhancements.
The release is available now from our website:
http://qpid.apache.o
On 26 February 2016 at 12:46, Robbie Gemmell wrote:
> On 25 February 2016 at 23:18, Randy Armstrong
> wrote:
>> I think it is related to proton because the exact same messages using the
>> exact same credentials are processed by an AMQPlite client running at the
>> same time.
>>
>
> I think wha
On 25 February 2016 at 23:18, Randy Armstrong
wrote:
> I think it is related to proton because the exact same messages using the
> exact same credentials are processed by an AMQPlite client running at the
> same time.
>
I think what Andrew meant is that as the error seems to be coming from
the
On 25 February 2016 at 21:16, Gordon Sim wrote:
> On 25/02/16 16:01, Randy Armstrong wrote:
>>
>>
>> [00B3D578]:0 <- @detach(22) [handle=0, closed=true, error=@error(29)
>> [condition=:"amqp:unauthorized-access", description="Unauthorized access.
>> 'Listen' claim(s) are required to perform this o
Hi
I do not have a reproducer, we had this problem for the first time about 3/4
weeks ago and again this week. We have been running our qpid 0.32 for about a
year without any problem. I will try to make a reliable reproducer and I'll
send to you if I found out something.
Best regards,
Filipe S
Hi Paul
Regarding your question.it looks like federation in one option, dispatcher
is the other one.
With dispatcher, you can create distributed topology like
publishers --> dispatcher --> array of brokers (they do not know each
other) --> dispatcher --> consumers.
The broker can be java or c+
