Damien, The knownExchanges map should only contain the number of exchanges that are currently pending in the ESB, so it should definitely not contain the full list of exchanges that ever passed through it.
If that's what you're seeing, I'd invite you to raise a JIRA issue for it. It would be cool if you could attach the sample SA there as well. That will make it a lot easier to troubleshoot things. Regards, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ 2009/4/6 dmorcellet <[email protected]>: > > Hi, > > I don't think you're to blame : > I'm using version 3.3 as downloaded from the download page of the site. > > Here are 2 archives : > - my maven project for my SA and my 2 SUs, > - Java source code for the JMS emitter and the JMS receiver. The main class > is Main. The emitter receives "EMITTER" as argument, and the receiver > receives "RECEIVER". > > http://www.nabble.com/file/p22904692/jms2jms.zip jms2jms.zip > http://www.nabble.com/file/p22904692/src.zip src.zip > > best regards, > Damien MORCELLET > > -- > View this message in context: > http://www.nabble.com/Memory-leak-when-using-the-JMS-binding-component-in-version-3.3-tp22895746p22904692.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > >
