Thanks Gary, However it doesn't seem to be so. Running exactly the same setup and code with kahaDb as persistence adapter results in a proper behaviour. But when changing only persistenceAdapter setting to use jdbc with mssql - no messages/queue survive the service restart.
Could the consumers' creation depend on the persistence type enabled in activemq configuration file? -- View this message in context: http://activemq.2283324.n4.nabble.com/Restarting-ActiveMq-removes-cleans-all-persisted-messages-queues-topics-tp3728577p3736183.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
