Rajith,
Thanks for the prompt response. I look forward to your feedback.
Richard
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Java-Reconnection-failure-when-processing-a-Message-tp7579188p7579195.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
-
Is it possible to use the failover syntax when creating queue routes via
qpid-config? If so, how?
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Federation-and-Queue-Route-Failover-tp7491759p7548483.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
All,
I'm looking at using the failover behaviour inbuilt with Qpid (v0.8).
So when I publish messages to a set of brokers, using the brokerlist (below)
the behaviour I see is ...
brokerlist=brokerA;brokerB&failover=roundrobin
(BrokerA and BrokerB are running)
Publisher continually sending mes
Thanks for the quick reply.
"Are you using the generic DESTINATION value for the route as well?"
Yes.
"Yes, links and bridges can be durable (though I believe they are not by
default). Their details are then stored in the database along with
details of durable queues, exchanges etc.
You can r
Sorry (obviously) sent my message to the wrong place. Ignore my last post.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Creation-of-Request-and-Response-quese-tp7479418p7491761.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
All,
I want durable queues that DO NOT persist the messages, i.e. I want my
configuration to survive a restart but (as a performance trade-off) I do not
want to incur the costs of persisting data, so do not care if my data
survives.
So I have created a durable queue and tried starting up the br
Hi Gordon,
Ok - I have done some more testing using the unique keys and have some
interesting results.
To confirm I am re-starting the brokers before each trial, and am repeating
the general idea as specified at the top of this thread. However the key
information is below:-
Send two message
Hi Gordon,
Thanks for the update.
I'll have a go at using a unique key and let you know how I get on.
Richard
--
View this message in context:
http://apache-qpid-users.2158936.n2.nabble.com/Dynamic-Routes-and-Duplicate-Messages-tp6562267p6583763.html
Sent from the Apache Qpid users mailing
Hello,
I am creating a route between two brokers on the headers exchange and would
like to know how you specify an appropriate binding key.
If I were subscribing direct to a headers exchange using AMQP I might use
... x-bindings:[{exchange:'amq.match', arguments : {x-match:all,
data-service:loo