As a bit more information, I turned on debug for activemq when running my test.
Based on the debug logging, it appears that the message I send is not expired until the "ActiveMQ Scheduler" fires and executes "Expiring messages. . ." This appears to happen somewhere around 30 seconds into my unit test. Is there a way to configure this scheduler in activemq to fire more frequently in the unit test? -john -- View this message in context: http://activemq.2283324.n4.nabble.com/unit-test-with-expired-advisory-tp3596907p3597378.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
