Looks like you have multiple brokers starting up. The first "[BrokerService] ActiveMQ 4.0-SNAPSHOT JMS Message Broker (BROKER_1) is starting" message is expected.
The next "[BrokerService] ActiveMQ 4.0-SNAPSHOT JMS Message Broker (null) is starting" message is odd. Why is this happening? Perhaps you have a client app using vm://null ... as a connection string. The vm transport will create the named broker if it is not all ready running in the current JVM.
