The only workaround for https consumer is using synchronous flow: ST. In this flow memory leak will not happen.
-- View this message in context: http://www.nabble.com/Memory-leaking-when-using-https-for-version-3.0.1.x-tf4668593s12049.html#a13338055 Sent from the ServiceMix - User mailing list archive at Nabble.com.
