Well was able to solve this issue sometime back. Thought of sharing with you all. Apparently our client was sending a very very huge xml by mistake(by huge I mean huge was having records for 36000 entries!). Now Http component was successfully forwarding it to the LWC component on the other machine. The LWC component was using XMLbeans to parse that cml which was taking more than 3 minutes and anyways rejecting the request as we allo max of 100 entries at a time. hence our backend was safe from being battered. But the Http thread was timing out due to the delay and seems was giving rise to memory leak.
Btw just an q - is this a bug and if so has this been fixed in future versions? We use servicemix 3.2.1. Cheers, allgo -- View this message in context: http://old.nabble.com/Servicemix-Http-component-memory-leak-issue-tp26177254p27108996.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
