Re: Slave automatically switch to Master even though Master is up

On 07/01/2008, MQ Newbie <[EMAIL PROTECTED]> wrote: >> >> To add on, if I am running one of the broker in the same machine as the >> database in Windows OS, everything seems to be fine. But the error was >> thrown when running from separate Linux machines. Do you think

Re: Slave automatically switch to Master even though Master is up

version that you mentioned earlier will be available? MQ Newbie wrote: > > Hi, > > I started the Master broker followed by the Slave broker. Everything was > running fine at the beginning but I don't understand how the Slave could > take over as Master even the Mast

Re: Slave automatically switch to Master even though Master is up

org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:98) at org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:36) MQ Newbie wrote: > > I am running MySQL version 5.0.46. > > > James.Strachan wrote: >> >&g

Re: JDBCPersistenceAdapter Too many connections

Can you please provide me an example configuration for this? James.Strachan wrote: > > Your database is refusing new connections. Either increase the number > of available connections on your database, or specify a limit in the > DBCP configuration in activemq.xml > > On 27/

Re: Slave automatically switch to Master even though Master is up

taSource: > [EMAIL PROTECTED] > > it looks like your configuration and MySQL version are not honouring > the exclusive database lock. What version of MySQL are you using? We > might need to patch the SQL used to ensure the lock works. > > > On 28/12/2007, MQ Newbie &l

Slave automatically switch to Master even though Master is up

Hi, I started the Master broker followed by the Slave broker. Everything was running fine at the beginning but I don;t understand how the Slave could took over as Master even the Master broker is up. Please help. See logs before and after ** : I have used the following configuration: Mast

Exception when shutting down broker

I am running 2 brokers on Master/Slave architecture. Each broker is running on different machine. I have the following error when i tried to stop anyone of the brokers. Please advise. INFO BrokerService - ActiveMQ Message Broker (localhost, ID:sgjms01.sphsearch.com-38092-201931

Re: Master/Slave Connection and Synchronization Error

r. > > uri="static://(tcp://localhost:61616,tcp://host1:61616)" /> > > Note how the network and transport connector tcp uri's have the same host > and port (i.e., localhost:61616). > > Before running your next test, try cleaning out your data directories.

JDBCPersistenceAdapter Too many connections

I encountered the following error after submitting about 6-8 jms message consecutively on Master/Slave architecture. Please advise. Thank you. WARN JDBCPersistenceAdapter - Old message cleanup failed due to: java.io.IOException: Too many connections java.io.IOException: Too many connect

Master/Slave Connection and Synchronization Error

Hi, I have setup the jms to work on the master/slave architecture. It works fine on localhost Windows machine on 2 different ports. But i have the errors when i run on 2 separate linux machine on the same port on both the master and slave nodes. The following is the configuration that i hCoave