yes… definitely agree on locking down the config file.
But I'm more worried about a regression at some future point. Unit tests
go a long way… but I can also put in guards in the code to prevent it from
even working with a broken broker by verifying that things are sane when it
connects to the br
We migrated from 5.8 to 5.10 without any problem.
Which protocol are you using ?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ACtivemq-5-10-compatibility-tp4682244p4682342.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi All,
I'm using ActiveMQ 5.8.0, jdk 1.5 / JRE 1.7, tomcat 6
I use applet in tomcat.
I'm able to publish message from web application, but when i try to send a
message from java applet, my messages goes directly into DLQ. It had worked
well with earlier activemq versions like 5.6.0.
Anyone, any
it is a very general requirement.
one approach is to have some sort of ping test of broker functionality
that you require.
deploy a camel route in the xml config.
have it do jms request/reply after it has done some validation like
produce/consume an advisory.
Then to validate ping that route. Wit
Hi Simon,
1. The example in the docs was wrong, I've just fixed it. It should have
said: If you want to take all messages sent to a Topic and publish them to
a Queue...
2. You are using activemq component, but you should use the broker
component :)
Cheers,
On 28 May 2014 23:29, simon.allen w
