Peek at this test and that package
https://github.com/apache/activemq/blob/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/usecases/ThreeBrokerQueueNetworkUsingTcpTest.java
On 21 Feb 2014 06:26, "Enrico Olivelli" wrote:
> thanks, I'll try to write down a test case to reproduce my dupl
thanks, I'll try to write down a test case to reproduce my duplicate
message issue on transactions
Can you tell me a sample test case to copy from in order to get started
? I think I have to start a little network of brokers inside one single
JVM in order to reproduce the problem
thank you
Il
inline
On 16 February 2014 16:09, Enrico Olivelli wrote:
> If I set updateURIsSupported=false do I need to reconfigure all the clients
> when I'm going to a a new broker ?
yes. you could make use of updateURIsURL to externalise the list.
>
> I cannot find the documentation for reconnectSupported
If I set updateURIsSupported=false do I need to reconfigure all the
clients when I'm going to a a new broker ?
I cannot find the documentation for reconnectSupported here
http://activemq.apache.org/failover-transport-reference.html
what does that option mean ?
I do not understand clearly what
the rebalance is all about new brokers in the cluster, so the
rebalance should only fire on a broker start.
the priorityBackup options allow a failover client to be sticky. Also
updateURIsSupported=false and reconnectSupported=false disables this
feature client side
On 8 February 2014 17:07, Enri
n advance
> > ActiveMQ is great
> >
> >
> > Enrico Olivelli
> >
> >
> > If you reply to this email, your message will be added to the discussion
> below:
> >
> http://activemq.2283324.n4.nabble.com/rebalanceClusterClients-failover-and-transactions-tp46776
o this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/rebalanceClusterClients-failover-and-transactions-tp4677662.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n234180...@n4.nabble.com
> To unsub
Hi,
I'm facing a problem in my system due to the option rebalanceClusterClients.
As I can see when this option is enabled every time a new connection is
created a signal is sent to every connected client in the network and
every failover connection is closed and re-opened.
In my system it happen
hanks,
Dave
--
View this message in context:
http://www.nabble.com/Failover-and-Transactions-tp15040387s2354p15040387.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
