On May 24, 2006, at 10:13 PM, G.S.S. Mahadevan wrote:
I think so? Every call to putObject uses a new OOS, so I'm not sure what effect the small change you had made? Have you use a profiler, such as http://yourkit.com/ , to see where the memory is actually being retained?I am also not very sure that it is Protocol Encoding/Decosing, My stack trace shows conistently the Encoder Write ops. I will test my fix today and let you know more.
okay. OOM stack traces generally don't indicate the source of the leak, just the code that attempted to allocate memory after its full.
you may want to ensure that you are using mina 0.9.4, which has fixes to trim the byte buffer pool occasionally
I do have plan for doing a customized ProtocolCodecFactory after my prototype. But I wanted to query is it safe in MINA-framework todo the ObjectOutputStream.close in a low priority thread (apart from a callee-thread).
probably safe, but i'm not sure thats necessary :) -pete -- [EMAIL PROTECTED] - http://fotap.org/~osi
smime.p7s
Description: S/MIME cryptographic signature
