ed to restart my consumer app (tomcat
based app) to make it working. I am using activemq 5.2
Thanks,
Chaitanya
-Original Message-
From: Matt Pavlovich [mailto:mattr...@gmail.com]
Sent: Wednesday, January 25, 2012 9:15 PM
To: users@activemq.apache.org
Subject: Re: Activemq Clustering and fai
I'm guessing you still have client-side code problems, which is very
common. I suggest using the out-of-the-box test harnesses available
from ActiveMQ to help eliminate the broker configuration. Try running
100, 1,000 and then ramp up to 100,000 messages through your Master
broker. If your c
Hi Matt
First, thank you.
Second , unfortunely it does not work.
I did both changes in the configuration you had suggested, but it does not
work.
In the first 2 attempts, I was really excited, because it had worked . But
when I did another attempt, it did not.
To give you a scenario : I 'm runnin
Abimael-
A couple of things:
You don't use a networkConnector for master/slave. This is definitely
causing a problem. Network Connectors are to connect to *other*
master/slave pairs to provide scaling of traffic load. Remember:
Master/Slave *only* provides high availability for the messag
Hi Matt
I shared both (master and slave ) there :
http://www.4shared.com/folder/uSPBPhA4/activemq.html
The message that appears on console for the Producer console when the
master shut down :
.7585 [ActiveMQ Transport: tcp://sim1648/127.0.1.1:61616] WARN
org.apache.activemq.transport.failov
Abimael-
It might be helpful to understand that the client-side fail-over is
handled by the ActiveMQ client-side library. The end-user just needs to
code the consumer program as if it was talking to one broker.
I suggest adding DEBUG, or TRACE level logging on the client-side. You
may find
Oh no! No it does not work.. I did another test to check and it does not
work even with Durable SUbscriber .
Scenario :
2 brokers >: master and slave
1 producer with failover uri on the code to connect and provide messages;
1 consumer with failover uri on the code to connect and consume messa
I just forgot to mention that it works properly IF you use durable topic
subscriber .
If you use "dynamic topics" , created by code , I noticed that it does not
work (as I had explained in my previous comments and I assume is very
similar your scenario ) .
Regards
--
View this message in context
I had the same issue and unfortunely it seems that it is back .
My test applications are not equals of you, as I am doing some tests about
failover and H.A. using 2 simple applications.
But, the bottom line is : when master goes down, you (and me) want that the
slave start working properly AND ,b
9:15 PM
To: users@activemq.apache.org
Subject: Re: Activemq Clustering and failover
Chaitanya-
There are several solutions for this, and I suggest starting with just
two brokers connected via network connectors. On the client side, you
configure the clients to point to both brokers and they will
Chaitanya-
There are several solutions for this, and I suggest starting with just
two brokers connected via network connectors. On the client side, you
configure the clients to point to both brokers and they will
automatically fail-over to the "live" broker if you are doing maintenance.
Ser
11 matches
Mail list logo
