Hi,
I didn't solved it.
I didnt find a way to bypass it.
I've tried to use the new servicemix-jms binding component (with ServiceMix 3.3), as Chris suggested. It does not show this memory leak problem but has some strange connection/deconnection problems.
I did not investiguate further (in the end, we decided to use a pure JMS solution with no ServiceMix, especially due to our required message volume/count).
If I use the same scenario with HTTP/SOAP binding components instead of JMS ones, the memory leak does not appear (millions of messages are OK).
Regards,
Damien.
JIRA jira@apache.org wrote:
Hi,
I"m using the newest version of servicemix (4) and I think I'm having the same problem of memory leak. I'd like to know if you solved it or if you found a way to bypass it.
Regards,
Tarek.
