Hi Michal, Thanks for the reply. Because the stage of our project is at and past experiences with ST, we have to make the Seda working.
Based on the previouse commonts related to this issue, I tracked down the code and compared the http and https: http uses non-blocking contiuation, after suspended it aborts the current process(req,resp) and re-call the process(req, resp) after resume. so the if(!isPending) .. else: exchanges.remove is called. while https using blocking contiuation, after suspended, it waits and resume excuting the code right after suspend call. so the ...else: exchanges.remove is never called. the exchanges.size is increased by each request. to fix the problem I just put exchanges.remove() after the suspend(). so when using blocking contiuation, the passed exchange can be removed from the exchanges map after resumed. the size is not accumulated any more and the memory usage is stable as well. Michal wrote: > > 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#a13355759 Sent from the ServiceMix - User mailing list archive at Nabble.com.
