short question because i just thought of it:
if a slave doesn't accept any connections while in slave mode:
how does the web console work for slaves?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Creating-a-Connection-to-an-activeMQ-in-Slave-Mode-tp4095183p4185911.html
Hi all,How can I upgrade amq from version 4.x to 5.x?
What I only know about is that 4.x works on jdk1.4 while 5.x works on jdk5+.
Is there any guide to introduce how to do this and what should be noted for
that?
Does upgrade need to reconstruct the client source?
Thanks.
SuoNayi
Does the web console work for your slave? I would have thought it does not
(assuming embedded web console and not an external web console).
The web console gets deployed at the end of the brokers startup, after it
started the transport connector.
If the slave waits on acquiring the lock that
Yes,so how to monitor the slave is a trouble as well.
I had raised a question about how to monitor master and slave as a whole but
none answered me.
At 2011-12-12 22:57:40,Torsten Mielke tors...@fusesource.com wrote:
Does the web console work for your slave? I would have thought it does not
Hello,
There is an ActiveMQ 5.5 migration guide [1] available on FuseSource.com.
Although it covers the migration from 5.4 to 5.5 some of the tips given there
may also apply to your migration or may at least be useful.
When going from version 4 to 5 you should better recompile your application
Hi,
You will also need to think about the persistence layer.
Most likely you will want to adopt KahaDB (which is in fact enabled by
default).
Regards,
Raúl.
On 12 December 2011 15:02, Torsten Mielke tors...@fusesource.com wrote:
Hello,
There is an ActiveMQ 5.5 migration guide [1] available
Hello,
when the consumer of a queue is unavailable for a while the number of
messages in the queue increases continuously. When the queue reaches a
critical unknown limit the broker is so busy to recover the messages from
the db that it blocks the producer and can no longer work properly. In the
There is generally not to monitor a lot about a slave as it won't startup
anything (with the exception of pure-master-slave). But it should start its JMX
server so that you can connect to the slave using any JMX client like jconsole.
Regards,
Torsten
On Dec 12, 2011, at 4:01 PM, SuoNayi
I am just getting started with activemq. I was trying to get it going in
code:
public class Launcher {
public static void main(String[] args) throws Exception{
BrokerService broker = new BrokerService();
broker.setUseJmx(true);
i'm using pure master slave and the easiest way to be notified that the
master has failed is to listen to the slave for the inevitable: i am master
now advisory.
--
View this message in context:
Hi Raul,
As far as I know, the Message Group is closed when the property JMSXGroupSeq is
set to -1.
Please raise a Jira to get that fixed…
I wrote something regarding that some time ago that should help as well…
http://marcelojabali.blogspot.com/2011/11/load-balanced-ordered-message.html
Hi Phill,
Just out of curiosity… what ActiveMQ version are you trying to use?
I've just tested your Broker class below and it seems to be working fine.
How are you trying to connect to the broker? As a local or remote process?
I've tried local and remote approaches against a 5.4.2 and 5.5.x
It's 5.5.1….
But I just tried again, and it works. The difference: I wasn't on VPN.
Not sure why that would matter, but it seems to.
Thanks!
On Mon, Dec 12, 2011 at 8:22 PM, Marcelo Jabali mjab...@fusesource.comwrote:
Hi Phill,
Just out of curiosity… what ActiveMQ version are you trying to
13 matches
Mail list logo
