The JMS spec does call out the need to call start() before consuming messages. There is setup that can experience race conditions, or order-of-operation problems otherwise. For example, a connection listener cannot be reliably added to a connection before it's needed.
It's frustrating to experience the problem of simply failing to consume, especially since it all "just looks right" otherwise. -- View this message in context: http://activemq.2283324.n4.nabble.com/Should-connection-createSession-throw-an-exception-if-the-connection-isn-t-started-tp4682160p4682181.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
