Could you try to give your brokers names without underscore character? I once had trouble with such a name...
Regards, Holger Koka wrote: > > Why is the broker starting itself again? Below is what I see after I start > up ActiveMQ > > ACTIVEMQ_HOME: /home/wchung/apache-activemq-4.1.1 > ACTIVEMQ_BASE: /home/wchung/apache-activemq-4.1.1 > Loading message broker from: xbean:Static_Matt.xml > INFO BrokerService - ActiveMQ 4.1.1 JMS Message Broker > (Active MQ_On_Mfriedman) 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:r > mi:///jndi/rmi://localhost:1099/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.ap > [EMAIL PROTECTED] > INFO JournalPersistenceAdapter - Journal Recovery Started from: > Active Jou rnal: using 2 x 20.0 Megs > at: /home/wchung/apache-activemq-4.1.1/conf/activemq-d > > ata/ActiveMQ_On_Mfriedman/journal > INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in > transa ctions recovered. > INFO TransportServerThreadSupport - Listening for connections at: > tcp://mfrie dman.dyndns.biz:61616 > INFO TransportConnector - Connector TC_mFriedman Started > INFO NetworkConnector - Establishing network connection > between f rom vm:?network=true to > tcp://mitacp52257:61616 > INFO BrokerService - ActiveMQ 4.1.1 JMS Message Broker > (null) is starting > INFO BrokerService - For help or more information please > see: > http://incubator.apache.org/activemq/ > WARN ManagementContext - Failed to start jmx connector: > Cannot bin d to URL > [rmi://localhost:1099/jmxrmi]: javax.naming.NameAlreadyBoundException: > > jmxrmi [Root exception is java.rmi.AlreadyBoundException: 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.ap > [EMAIL PROTECTED] > INFO JournalPersistenceAdapter - Journal Recovery Started from: > Active Jou rnal: using 2 x 20.0 Megs > at: /home/wchung/apache-activemq-4.1.1/conf/activemq-d > > ata/null/journal > INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in > transa ctions recovered. > INFO BrokerService - ActiveMQ JMS Message Broker (null, > ID:mfr > iedman.dyndns.biz-45507-1196090254923-1:1) started > INFO TransportConnector - Connector vm://null Started > WARN NetworkConnector - Could not start network bridge > between: v m:?network=true and: > tcp://mitacp52257:61616 due to: java.net.ConnectException: > > Connection refused > INFO NetworkConnector - Establishing network connection > between f rom vm:?network=true to > tcp://mitacp52257:61616 > INFO TransportConnector - Connector vm://null Stopped > WARN ManagementContext - Failed to start jmx connector: > Cannot bin d to URL > [rmi://localhost:1099/jmxrmi]: javax.naming.NameAlreadyBoundException: > > jmxrmi [Root exception is java.rmi.AlreadyBoundException: jmxrmi] > INFO BrokerService - ActiveMQ 4.1.1 JMS Message Broker > (null) is starting > INFO BrokerService - For help or more information please > see: > http://incubator.apache.org/activemq/ > INFO NetworkConnector - Establishing network connection > between f rom vm:?network=true to > tcp://comfsd001:61616 > INFO faultPersistenceAdapterFactory - Journal is locked... waiting 10 > seconds f or the journal to be > unlocked. > > The broker tries to start itself twice, hence the lock. Any idea why this > is happening? > -- View this message in context: http://www.nabble.com/Static-Network-of-brokers-tf4863557s2354.html#a13969477 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
