Hi Tim, Thanks for your advice, I've already filed a jira ticket for it. It is AMQ-6200 Add a retry mechanism would be a decent solution to my problem, and I agree with you that just ignoring the exception is not a good one. Please add this feature to future ActiveMQ release. We can disable pooling preparestatement. But I am looking for another way as a workaround, I am enabling testOnBorrow or testwhileIdle to see whether that could help since I doubt it is because we used invalid connection to create preparestatement and throw that exception.
Anyway, adding retry for network connector is definitely a good improvement. :) Best Regards -- View this message in context: http://activemq.2283324.n4.nabble.com/Failed-network-connector-can-not-be-re-established-tp4709054p4709217.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
