But I do as what you say , it does work after a while , not starting.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Broker-Blocked-WARN-Broker-localhost-not-started-so-using-DCFR-instead-tp2353940p3801138.html
Sent from the ActiveMQ - User mailing list archive
Hello,
My broker can not do anything, nor send or receive messages.
When I look at the console, there's only this error:
2009-11-10 09:35:21,205 [7638536 @ qtp0-34] WARN BrokerRegistry - Broker
localhost not started so using instead
Does someone can help me solve this painful problem ?
can you post your configuration and some more context?
The brokerName attribute is relevant to the vm: url you use, localhost
is the default value.
Also, try and enable full debug logging to see if you can extract more
information.
2009/11/10 titexe tit...@yahoo.fr:
Hello,
My broker can not
The context :
i have a network broker type duplex.
and a route camel : move message to othe queue, and track the message in
database.
Below my configuration :
broker xmlns=http://activemq.apache.org/schema/core; brokerName=DCFR
dataDirectory=${activemq.base}/data
!-- Destination
I guess you have tried to un comment:
!-- property name=brokerURL
value=vm://DCFR?create=falseamp;waitForStart=1 / --
2009/11/10 titexe tit...@yahoo.fr:
The context :
i have a network broker type duplex.
and a route camel : move message to othe queue, and track the message in
I removed the just waitForStart
Otherwise there's the line
property name=brokerURL value=vm://localhost?create=false /
Gary Tully wrote:
I guess you have tried to un comment:
!-- property name=brokerURL
value=vm://DCFR?create=falseamp;waitForStart=1 / --
2009/11/10 titexe
but I think it should be vm://DCFR as that matches the brokerName
attribute of your configured broker.
2009/11/10 titexe tit...@yahoo.fr:
I removed the just waitForStart
Otherwise there's the line
property name=brokerURL value=vm://localhost?create=false /
Gary Tully wrote:
I guess you