activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mathias <math...@afjochnick.net>
Subject Re: Duplicate brokers created in Tomcat
Date Wed, 20 Oct 2010 23:06:46 GMT

Quick update on this issue:

I did one change. In my webapp that is to be the consuming end of the queue
im trying to set up, i changed the URL to the broker to:

vm://nubaBroker?brokerConfig=xbean:file:/karpet/conf/activemq.xml&amp;create=false

this of course resulted in that i could see errors that the broker didn't
exist at first
WARN  2010-10-21 01:00:28 DefaultMessageListenerContainer [WARN] Could not
refresh JMS Connection for destination 'messaging.in' - retrying in 5000 ms.
Cause: Could not create Transport. Reason: java.io.IOException: Broker named
'nubaBroker' does not exist.

However, when i started the sending webapp, which created the broker on the
same url and put a message on the queue, the receiving webapp saw the
broker, did NOT create a second, and i saw no 'lock' messages.

Would be very nice if someone had any ideas as to why this happened. I'm
also not sure about whether i should worry about the previous lock issue.
Again thankful for pointers.
-- 
View this message in context: http://activemq.2283324.n4.nabble.com/Duplicate-brokers-created-in-Tomcat-tp3003512p3004783.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message