Hi Tim, Thanks for your useful tips. I agree that there may be some configuration problem in JDBS store, but I don't think the network connector should just be stopped and never be restarted again without restarting ActiveMQ service due to exeption in JDBC store. I don't think it is an acceptable behavior for ActiveMQ network relying on the message forwarding. Maybe you could add some feature to let the network still alive even such exception happens. For example, adding a peoperty of ignoreLocalIOException for networkConnector?
Best Regards -- View this message in context: http://activemq.2283324.n4.nabble.com/Failed-network-connector-can-not-be-re-established-tp4709054p4709183.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
