RE: Master/slave configuration not working

2012-02-16 Thread Chaitanya Gupta
Hi Matt, Can you help with this, I can provide config file and other details you need. Thanks, Chaitanya -Original Message- From: Chaitanya Gupta [mailto:chaitanya_gu...@persistent.co.in] Sent: Wednesday, February 15, 2012 5:56 PM To: users@activemq.apache.org Subject: Master/slave

RE: Master/slave configuration not working

2012-02-16 Thread Chaitanya Gupta
So you are saying it is DB2 Driver issue? But I can't move away from DB2. Has anyone tried clustering/failover protocol using Activemq configured with DB2? Thanks, Chaitanya -Original Message- From: Zagan [mailto:erbsen.fr...@gmail.com] Sent: Thursday, February 16, 2012 2:17 PM To: user

RE: logging.properties not found error during Activemq startup

2012-02-16 Thread Chaitanya Gupta
activemq.bat has following line - if "%ACTIVEMQ_OPTS%" == "" set ACTIVEMQ_OPTS=-Xmx512M -Dorg.apache.activemq.UseDedicatedTaskRunner=true -Djava.util.logging.config.file=logging.properties When I specify full path, I don't get any exception - if "%ACTIVEMQ_OPTS%" == "" set ACTIVEMQ_OPTS=-Xmx512

RE: Master/slave configuration not working

2012-02-15 Thread Chaitanya Gupta
I am using "IBM DB2" FYI - My application is working fine with Activemq 5.5.1, when AMQ is not configured in Master/Slave. Application can connect to the broker and send/consume the messages. Problem started when I configured in Master / Slave mode. -Original Message- From: Zagan [mai

RE: logging.properties not found error during Activemq startup

2012-02-15 Thread Chaitanya Gupta
ACTIVEMQ_HOME is set, getting echoed when I start activemq - D:\OEE\apache-activemq-5.5.1-bin\apache-activemq-5.5.1\bin>activemq.bat Java Runtime: IBM Corporation 1.6.0 D:\OEE\ibm_sdk60\ibm_sdk60\jre Heap sizes: current=4096k free=2787k max=524288k JVM args: -Xjcl:jclscar_24 -Dcom.ibm.oti.

RE: logging.properties not found error during Activemq startup

2012-02-15 Thread Chaitanya Gupta
I am using "apache-activemq-5.5.1\bin\activemq.bat" file to start AMQ. I copied one of the sample conf file as activemq.conf and using DB as message store. I can see logging.properties in conf directory. I don't see logging.properties in data directory. Dir output of Directory "D:\OEE\apache-

RE: Master/slave configuration not working

2012-02-15 Thread Chaitanya Gupta
Yes, both the broker are pointing to same DB. Master gets the lock but messageSend is not working, it is not returning back. Thanks, Chaitanya -Original Message- From: Zagan [mailto:erbsen.fr...@gmail.com] Sent: Wednesday, February 15, 2012 7:03 PM To: users@activemq.apache.org Subject:

Master/slave configuration not working

2012-02-15 Thread Chaitanya Gupta
Hi, I am using master/slave configuration with AMQ 5.5.1. The brokers are configured as master slave. Master has a lock on the db and slaves waits to acquire the lock. Application has queues configured using the failover protocol. e.g failover tcp://:61616?wireFormat.maxInactivityDuration=0,tcp

logging.properties not found error during Activemq startup

2012-02-15 Thread Chaitanya Gupta
Hi, I downloaded ActiveMq 5.5.1 and during startup getting below error, can anyone help me with this error - Loading message broker from: xbean:activemq.xml INFO | Refreshing org.apache.activemq.xbean.XBeanBrokerFactory$1@47ad47ad: star tup date [Wed Feb 15 14:47:03 IST 2012]; root of context h

RE: Activemq Clustering and failover

2012-02-02 Thread Chaitanya Gupta
nd sharing destinations, you can look to add slaves and client update to the URI's. Hope this helps! Matt Pavlovich On 1/25/12 4:20 AM, Chaitanya Gupta wrote: > Hi, > > I have an application deployed in clustered env (say app server1, app > server2). I also have activemq running

Activemq Clustering and failover

2012-01-25 Thread Chaitanya Gupta
Hi, I have an application deployed in clustered env (say app server1, app server2). I also have activemq running on server1 and server2 so I have 2 brokers (one queue on each broker). App on server1 can write to any of the queue (Q1, Q2) but will consume only messages on Q1. We are looking for