On Tue, Jul 21, 2009 at 10:14 AM, Rob Davies<[email protected]> wrote:
> Don't use journaledJDBC - just JDBC - or KahaDB - or the default
> (AMQPersistenceAdaptor)
OK we're running an antiquated version of ActiveMQ (4.1.1), so it
looks like we don't have the fancy AMQ or KahaDB persistence adapters.
With this config in activemq.xml I was able to get both the brokers to come up:
<persistenceAdapter>
<jdbcPersistenceAdapter dataDirectory="/local/betaactivemq" />
</persistenceAdapter>
However, as I started to celebrate success I started the second
broker, and it looks like they both think they can acquire an
exclusive lock :(
Broker 1:
----------------------------------
activemq start
ACTIVEMQ_HOME: /home/h3app/activemq
ACTIVEMQ_BASE: /home/h3app/activemq
Loading message broker from: xbean:activemq.xml
INFO BrokerService - ActiveMQ 4.1.1 JMS Message
Broker (localhost) is starting
INFO BrokerService - For help or more information
please see: http://incubator.apache.org/activemq/
INFO ManagementContext - JMX consoles can connect to
service:jmx:rmi:///jndi/rmi://localhost:8097/jmxrmi
INFO JDBCPersistenceAdapter - Database driver recognized:
[apache_derby_embedded_jdbc_driver]
INFO DefaultDatabaseLocker - Attempting to acquire the
exclusive lock to become the Master broker
INFO DefaultDatabaseLocker - Becoming the master on
dataSource: org.apache.derby.jdbc.embeddeddatasou...@4bb7b407
INFO TransportServerThreadSupport - Listening for connections at:
tcp://0.0.0.0:61616
INFO TransportConnector - Connector openwire Started
INFO BrokerService - ActiveMQ JMS Message Broker
(localhost, ID:delbpsjhhcapp02-36440-1248180630339-1:0) started
Broker 2:
----------------------------------
activemq start
ACTIVEMQ_HOME: /home/h3app/activemq
ACTIVEMQ_BASE: /home/h3app/activemq
Loading message broker from: xbean:activemq.xml
INFO BrokerService - ActiveMQ 4.1.1 JMS Message
Broker (localhost) is starting
INFO BrokerService - For help or more information
please see: http://incubator.apache.org/activemq/
INFO ManagementContext - JMX consoles can connect to
service:jmx:rmi:///jndi/rmi://localhost:8097/jmxrmi
INFO JDBCPersistenceAdapter - Database driver recognized:
[apache_derby_embedded_jdbc_driver]
INFO DefaultDatabaseLocker - Attempting to acquire the
exclusive lock to become the Master broker
INFO DefaultDatabaseLocker - Becoming the master on
dataSource: org.apache.derby.jdbc.embeddeddatasou...@4bb7b407
INFO TransportServerThreadSupport - Listening for connections at:
tcp://0.0.0.0:61616
INFO TransportConnector - Connector openwire Started
INFO BrokerService - ActiveMQ JMS Message Broker
(localhost, ID:delbpsjhhcapp01-42436-1248180928625-1:0) started
So it's looking like using a Windows share mounted via CIFS doesn't
give you flock() properly....
Is there a specific persistence adapter I should use in 4.1 that might
get this working? Anyone?
--
Eric
http://nixwizard.net
