hey all, i've got a question regarding the behaviour of using the jdbcPersistenceAdaptor. i have deployed ActiveMQ into a clustered JBoss 4.0.5 environment. I basically have 2 JBoss servers, each of which has the ActiveMQ RAR deployed. I've attached the broker xml file for reference: http://www.nabble.com/file/p13696937/broker.xml broker.xml
When i start up the JBoss servers, the first server comes up correctly but the second jboss instance hangs during start up while it is trying to get a lock on the database (activemq). when i shut down server one, the second instance continues and finishes the start up. is this how it should behave? i added the 'useDatabaseLock="false"' attribute to the broker.xml but to me this will result in both servers available to accept requests which is not what is desired. can someone confirm this is how it is expected to behave? the reason i'm asking was i intended to deploy a EAR file in the jboss instance on each server which would use activemq tp send messages to other applications. however, if the second instance doesn't come up ever then this won't work as i need to ensure i have clustering working on the EAR level. cheers and thanks ahead of time ben -- View this message in context: http://www.nabble.com/jdbcPersistence-behaviour-tf4787830s2354.html#a13696937 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
