Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of james.strachan@gmail.com
 designates 64.233.166.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=HEZEfeyNimtyjLWnfiP2VDFqa5cs2xXDFnAe2RhTL+r9EKC4NCaMCxGwTbPxjMbAvdI25U0rhogBlcwUveaQoslRMIcnHbbUF782oNDk5L3J2yDegEN0n0NNR96ra+1TzGgw2Q79vQ53bRoIwoWGIMx54MIFvw9BgkQfD0bCk7Q=
Message-ID: <ec6e67fd0711260946x3130c9a0gffddcde28af743ea@mail.gmail.com>
Date: Mon, 26 Nov 2007 17:46:07 +0000
From: "James Strachan" <james.strachan@gmail.com>
To: users@activemq.apache.org
Subject: Re: Static Network of brokers
In-Reply-To: <13952449.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <13918077.post@talk.nabble.com>
	 <46450069-5E11-4B85-BE92-B286E0D36317@gmail.com>
	 <13948774.post@talk.nabble.com> <13949909.post@talk.nabble.com>
	 <13952449.post@talk.nabble.com>

It could be a dependency issue in your spring.xml
http://activemq.apache.org/the-vm-transport-starts-a-broker-before-my-configured-broker-starts.html

On 26/11/2007, Koka <wchung@symcor.com> 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
> ache.derby.jdbc.EmbeddedDataSource@6458a6
> 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
> ache.derby.jdbc.EmbeddedDataSource@c67a88
> 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#a13952449
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://open.iona.com