It seems as if, if I use the broker.start() method things are BETTER. I still get this error when I'm trying to set a specific destination.
One other thing is that if my Spring Message List tosses an exception because it can't write to the database the message seem to STOP flowing to it. Instead of queue of my own, should I just be listening to ActiveMQ.DLQ? -- View this message in context: http://activemq.2283324.n4.nabble.com/Broker-Configuration-Redlivery-Policy-tp4678217p4678293.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
