Hello,
Sorry to revive an old mail but we are still facing the issue with IPv6 and we
had to do an ugly patch to remove all references to IPv6 in the tests.
Have you found a better alternative? It seems that Chuck suggested it could be
done using C code.
Regards,
Adel
Hi Rawad,
Dispatch Policy
http://qpid.apache.org/releases/qpid-dispatch-0.7.0/book/book.html#policy
can do just that. Policy can deny or allow consumer sources and sender targets.
Dispatch
will always create the address internally if the policy allows the user to
access it.
Sample policies
When you start the dispatch router, it puts out a line on the console saying
something like this -
"Thu Jan 26 14:46:53 2017 SERVER (info) Running in DEBUG Mode"
That means that the router is ready to receive requests.
If you want to see all all detailed trace messages from all router modules
Hello Robbie,
I replaced the "createQueue" with "createTemporaryQueue" for the reply consumer
and activated PN_TRACE_FRM on Dispatch Router and JMS Client.
PS: As Rabih stated before, we are using the same connection and same session
to create the JMSProducer for the request and the
Yes. By default a reasonable log should already be there.
If not then configure log settings in the qdrouterd.conf
---
log {
module: ROUTER_LS
enable: trace+
}
log {
module: ROUTER_MA
enable: trace+
}
log {
module: ROUTER_HELLO
enable: trace+
}
---
More details are at:
Hello,
I am trying to showcase an example where a dispatch router instance is used
as medium for AMQP based point-to-point messaging between a client and a
server.
In my example, the server creates a JMS consumer on a queue and the client
sends messages to it. I noticed that as soon as the
