Gert, I have attached a patch to SM-1134. I don't think that is fixes the problem as Guillaume intended, however it does appear to be working and I did not see any (serious) memory leaks. Could you have a look at it?
Thanks, Jeroen Ninck Blok -----Original Message----- From: Gert Vanthienen [mailto:[EMAIL PROTECTED] Sent: maandag 25 augustus 2008 8:58 To: [email protected] Subject: Re: SM-1134 / NPE PojoChannel Jeroen, If you look at the servicemix-bean BeanEndpoint class, you'll notice that everything revolves around the Request object that is being created on a provider exchange. This object is being used to track callbacks, but it is also being correlated to every consumer exchange being sent by the servicemix-bean component -- the original request object is being retrieved when the response message for the consumer exchange is received. We also use it to track if/when the original MessageExchange is done so we can clean up memory. I think what Guillaume means is that you'll need changes almost everywhere to accommodate the use case where there is no initial Request object. Feel free to submit patches for it if you need this behavior and cannot use the sendSync() workaround for some reason. Just ask for any help you need implementing this... Regards, Gert Ninck Blok, Jeroen wrote: > Hi all, > > > > We have stumbled into ServiceMix bug SM-1134 and we are wondering if > there has been any progress on this bug since it original report in > November 2007. > > It looks like a very basic functionality which is not working correctly. > Am I correct on this? > > Guillaume, you mentioned that this use case is not really supported > right now and that several modifications are required to support this. > Can you be more specific on these modifications? > > > > Thanks in advance, > > > > Jeroen Ninck Blok > > > > > > > > This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. > > > This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
