Vince,
When you run the qpidd broker, are you loading the amqp.so module
(--load-module amqp.so)? If not, the broker won't support AMQP 1.0.
You can also get useful information by turning on tracing when you run
the router (PN_TRACE_FRM=1 qdrouterd ...).
-Ted
On 08/31/2016 09:32 AM,
Hi Ted
It looks like the dispatcher is connecting to ActiveMQ, but not Qpid...
Does qpidd expect to be told what protocol to use, when something connects
to it?
The qpidd logs contains this error every few seconds, whilst the dispatcher
is running:
[system] error Connection
Can you please add the above to your config and see if the router still
continues to segfault?
Thanks.
- Original Message -
> From: "Vince Cole" <m...@vincecole.co.uk>
> To: users@qpid.apache.org
> Sent: Wednesday, August 31, 2016 8:40:32 AM
> Subjec
Hi Ted
Thanks for the help, I'll try out that config and see what happens.
In the meantime, I caused the segfault by entering a partial example (taken
from
http://qpid.2158936.n2.nabble.com/Qpid-Dispatch-to-ActiveMQ-td7624037.html#a7624153
)
The actual content I used was similar to:
connector {
On 08/31/2016 07:46 AM, Vince Cole wrote:
Hi
I want to route AMQP 1.0 messages from a named queue/topic on a remote
'source' broker, to a queue/topic (name doesn't matter, can be the same as
the source for simplicity) on a remote 'destination' broker, on Linux
(Centos 7.0) using qdrouterd.
Is
Hi
I want to route AMQP 1.0 messages from a named queue/topic on a remote
'source' broker, to a queue/topic (name doesn't matter, can be the same as
the source for simplicity) on a remote 'destination' broker, on Linux
(Centos 7.0) using qdrouterd.
Is this possible?
Is there an example of a
