Hello Tim,
The error is happening when trying to create a session with the below
failover URL when the first URL is that of the REPLICATE. I am using the
amqp.vhost option to specify the virtual host, could that be the issue? I
mean the vhost is not present on the REPLICATE machine.
On 03/10/2016 06:12 PM, Rob Godfrey wrote:
On 10 March 2016 at 23:44, Adel Boutros wrote:
If I compile while skipping tests and deploy the jar then the broker no
longer crashes.
Nevertheless, the client doesn't try the 2nd URL, instead it fails with the
below stack. If I
On 03/10/2016 05:44 PM, Adel Boutros wrote:
If I compile while skipping tests and deploy the jar then the broker no
longer crashes.
Nevertheless, the client doesn't try the 2nd URL, instead it fails with the
below stack. If I put back the MASTER URL before the Replicate URL, then
everything
On 11 March 2016 at 00:07, Rob Godfrey wrote:
> OK - that's my fault, I need to fix some of the mocking in that test... I
> will do that shortly - you can ignore this issue in the meantime.
>
>
I've merged the fixes for the mocking in the unit tests to the 6.0.x branch
On 10 March 2016 at 23:44, Adel Boutros wrote:
> If I compile while skipping tests and deploy the jar then the broker no
> longer crashes.
> Nevertheless, the client doesn't try the 2nd URL, instead it fails with the
> below stack. If I put back the MASTER URL before the
OK - that's my fault, I need to fix some of the mocking in that test... I
will do that shortly - you can ignore this issue in the meantime.
-- Rob
On 10 March 2016 at 23:36, Adel Boutros wrote:
> Hello Rob,
>
> I have 3 tests failing under *ProtocolEngine_1_0_0Test* when
Hello Rob,
I have 3 tests failing under *ProtocolEngine_1_0_0Test* when compiling
*broker-plugins
6.0.2-SNAPSHOT *in Intellij or maven
- ProtocolEngine_1_0_0Test.testProtocolEngineWithNoSaslNonTLSandAnon
- ProtocolEngine_1_0_0Test.testProtocolEngineWithNoSaslTLSandExternal
-
If I compile while skipping tests and deploy the jar then the broker no
longer crashes.
Nevertheless, the client doesn't try the 2nd URL, instead it fails with the
below stack. If I put back the MASTER URL before the Replicate URL, then
everything works fine.
It seems to me that the order in
On Thu, Mar 10, 2016 at 3:37 PM, Olivier Mallassi <
olivier.malla...@gmail.com> wrote:
> Hi
>
> I do not know about the JS API but
>
> 1/ AFAIK, AMQP 1.0 does not define anything regarding queue creation and
> assume queues already exist on the broker side.
> 2/ with qpid cpp, you could be able
Hi
I do not know about the JS API but
1/ AFAIK, AMQP 1.0 does not define anything regarding queue creation and
assume queues already exist on the broker side.
2/ with qpid cpp, you could be able to create the "filtered queue " with
qpid-config add exchange topic subjects
qpid-config add
Apologies for this - you have indeed run into bug :-(
I've raised a JIRA - https://issues.apache.org/jira/browse/QPID-7136 .
I've committed a fix both to trunk, and the 6.0.x branch which I hope will
fix this issue... If you want to test it out you can use the 6.0.x branch
which can be found
Hi All,
I was previously using AMQP 0.9.1 (RabbitMQ) and the client library amqplib
for Node JS. With these components it was easy to give the client the
possibility to create the queue and the bindingKey and connect it to an
topic-exchange.
I now would like a client to create a queue and a
12 matches
Mail list logo