activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robottaway <rotta...@musiciansfriend.com>
Subject Re: networkConnectors causing NPE
Date Thu, 09 Nov 2006 00:24:27 GMT

Thanks taking the spaces out of the <brokerName/> element did fix that
problem. Now I am having a problem with an extra broker starting up, LOL!
All I do to get this behavior is enable the 'networkConnector' element.
Using the exact same config I posted earlier.

ACTIVEMQ_HOME:
/opt/MFApps/ServiceMix/activemq_installs/incubator-activemq-4.0.2
Loading message broker from: xbean:activemq.xml
INFO  BrokerService                  - ActiveMQ 4.0.2 JMS Message Broker
(BSDdev4.0.2AMQbroker) is starting
INFO  BrokerService                  - For help or more information please
see: http://incubator.apache.org/activemq/
INFO  JDBCPersistenceAdapter         - Database driver recognized:
[apache_derby_embedded_jdbc_driver]
INFO  JournalPersistenceAdapter      - Journal Recovery Started from: Active
Journal: using 5 x 20.0 Megs at:
/opt/MFApps/ServiceMix/activemq_installs/activemq-data/journal
INFO  JournalPersistenceAdapter      - Journal Recovered: 0 message(s) in
transactions recovered.
INFO  TransportServerThreadSupport   - Listening for connections at:
tcp://bsddev.musiciansfriend.com:61605
WARN  MulticastDiscoveryAgent        - brokerName not set
INFO  TransportConnector             - Connector default Started
INFO  TransportServerThreadSupport   - Listening for connections at:
stomp://bsddev.musiciansfriend.com:61606
INFO  TransportConnector             - Connector stomp Started
INFO  NetworkConnector               - Network Connector multicastordeaux
Started
INFO  BrokerService                  - ActiveMQ JMS Message Broker
(BSDdev4.0.2AMQbroker,
ID:bsddev.musiciansfriend.com-58540-1163031439033-1:0) started
INFO  NetworkConnector               - Establishing network connection
between from vm:?network=true to tcp://robert-ottaways-computer.local:61616
INFO  BrokerService                  - ActiveMQ 4.0.2 JMS Message Broker
(null) is starting
INFO  BrokerService                  - For help or more information please
see: http://incubator.apache.org/activemq/
INFO  JDBCPersistenceAdapter         - Database driver recognized:
[apache_derby_embedded_jdbc_driver]
INFO  JournalPersistenceAdapter      - Journal Recovery Started from: Active
Journal: using 2 x 20.0 Megs at:
/opt/MFApps/ServiceMix/activemq_installs/incubator-activemq-4.0.2/activemq-data/null/journal
INFO  JournalPersistenceAdapter      - Journal Recovered: 0 message(s) in
transactions recovered.
INFO  BrokerService                  - ActiveMQ JMS Message Broker (null,
ID:bsddev.musiciansfriend.com-58540-1163031439033-1:1) started
INFO  TransportConnector             - Connector vm://null Started
WARN  NetworkConnector               - Could not start network bridge
between: vm:?network=true and: tcp://robert-ottaways-computer.local:61616
due to: java.net.UnknownHostException: robert-ottaways-computer.local
INFO  NetworkConnector               - Establishing network connection
between from vm:?network=true to tcp://robert-ottaways-computer.local:61616
INFO  TransportConnector             - Connector vm://null Stopped
INFO  BrokerService                  - ActiveMQ 4.0.2 JMS Message Broker
(null) is starting
INFO  BrokerService                  - For help or more information please
see: http://incubator.apache.org/activemq/
ERROR BrokerService                  - Failed to start ActiveMQ JMS Message
Broker. Reason: org.apache.activeio.journal.active.JournalLockedException:
Journal is already opened by this application.
org.apache.activeio.journal.active.JournalLockedException: Journal is
already opened by this application.
        at
org.apache.activeio.journal.active.ControlFile.lock(ControlFile.java:77)
        at
org.apache.activeio.journal.active.LogFileManager.initialize(LogFileManager.java:121)
        at
org.apache.activeio.journal.active.LogFileManager.<init>(LogFileManager.java:102)
        at
org.apache.activeio.journal.active.JournalImpl.<init>(JournalImpl.java:101)
        at
org.apache.activemq.store.DefaultPersistenceAdapterFactory.createJournal(DefaultPersistenceAdapterFactory.java:199)
        at
org.apache.activemq.store.DefaultPersistenceAdapterFactory.getJournal(DefaultPersistenceAdapterFactory.java:135)
        at
org.apache.activemq.store.DefaultPersistenceAdapterFactory.createPersistenceAdapter(DefaultPersistenceAdapterFactory.java:64)
        at
org.apache.activemq.broker.BrokerService.createPersistenceAdapter(BrokerService.java:969)
        at
org.apache.activemq.broker.BrokerService.getPersistenceAdapter(BrokerService.java:560)
        at
org.apache.activemq.broker.BrokerService.createRegionBroker(BrokerService.java:930)
        at
org.apache.activemq.broker.BrokerService.createBroker(BrokerService.java:889)
        at
org.apache.activemq.broker.BrokerService.getBroker(BrokerService.java:459)
        at
org.apache.activemq.broker.BrokerService.start(BrokerService.java:362)
        at
org.apache.activemq.transport.vm.VMTransportFactory.doCompositeConnect(VMTransportFactory.java:106)
        at
org.apache.activemq.transport.vm.VMTransportFactory.doConnect(VMTransportFactory.java:52)
        at
org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:64)
        at
org.apache.activemq.network.NetworkConnector.createLocalTransport(NetworkConnector.java:283)
        at
org.apache.activemq.network.DiscoveryNetworkConnector.onServiceAdd(DiscoveryNetworkConnector.java:110)
        at
org.apache.activemq.transport.discovery.multicast.MulticastDiscoveryAgent$2.run(MulticastDiscoveryAgent.java:342)
        at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
        at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
        at java.lang.Thread.run(Thread.java:595)
WARN  NetworkConnector               - Could not connect to local URI:
vm:?network=true: Journal is already opened by this application.


-- 
View this message in context: http://www.nabble.com/networkConnectors-causing-NPE-tf2598042.html#a7250150
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message