Hi Gary, Yes. I got the issue root cause. It's the EHCache library configuration.
Thanks for all who spent time reading & responding to my emails. With regards, R Kaja Mohideen -----Original Message----- From: Gary Gregory [mailto:ggreg...@rocketsoftware.com] Sent: Tuesday, December 20, 2011 3:41 AM To: R Kaja Mohideen (WT01 - GMT-Telecom Equipment) Cc: kesh...@us.ibm.com; jgr...@alumni.princeton.edu; xalan-j-users@xml.apache.org Subject: Re: Xalan Tranformation Running Slow after about 5K Transformations It sounds from an earlier email that you problem was introduced by you cache. I suggest that you figure out if this layer causes the problem and if it can be configured to get the behavior you want. Gary On Dec 19, 2011, at 6:18, "kaja.mohid...@wipro.com<mailto:kaja.mohid...@wipro.com>" <kaja.mohid...@wipro.com<mailto:kaja.mohid...@wipro.com>> wrote: Hi Gary, I'm using VisualVM to monitor my application. I am taking Thread dumps to see where my threads are Blocked. I can also take Heap dump to see what eats my memory. But, I don't understand how to analyze this issue by seeing the memory as my application has cache that eats more memory. Any input like the classes' instances to be looked for will be helpful. Thanks in advance, With Regards, R Kaja Mohideen ________________________________ From: Gary Gregory [mailto:ggreg...@rocketsoftware.com] Sent: Sun 12/18/2011 2:47 AM To: R Kaja Mohideen (WT01 - GMT-Telecom Equipment) Cc: kesh...@us.ibm.com<mailto:kesh...@us.ibm.com>; jgr...@alumni.princeton.edu<mailto:jgr...@alumni.princeton.edu>; xalan-j-users@xml.apache.org<mailto:xalan-j-users@xml.apache.org> Subject: Re: Xalan Tranformation Running Slow after about 5K Transformations How about using a profiler to see if you have a memory retention bug? Gary On Dec 17, 2011, at 8:35, "kaja.mohid...@wipro.com<mailto:kaja.mohid...@wipro.com><mailto:kaja.moh id...@wipro.com>" <kaja.mohid...@wipro.com<mailto:kaja.mohid...@wipro.com><mailto:kaja.moh id...@wipro.com>> wrote: Gentle reminder! From: R Kaja Mohideen (WT01 - GMT-Telecom Equipment) Sent: Tuesday, December 13, 2011 7:35 PM To: kesh...@us.ibm.com<mailto:kesh...@us.ibm.com><mailto:kesh...@us.ibm.com> Cc: jgr...@alumni.princeton.edu<mailto:jgr...@alumni.princeton.edu><mailto:j gr...@alumni.princeton.edu>; xalan-j-users@xml.apache.org<mailto:xalan-j-users@xml.apache.org><mailto :xalan-j-users@xml.apache.org> Subject: RE: Xalan Tranformation Running Slow after about 5K Transformations Importance: High What do you mean by releasing cached information? I have only javax.xml.transform.Templates cached and the newTransformers are created in method scope of threads and those references are not maintained anywhere. Ok.. I forgot to add one important information. My application was running smoothly for any number of transformations without any issues previously. I'm facing this issue only after I have included EHCache library in my application to store the XSLT output. Have any idea where these two conflicts? With regards, R Kaja Mohideen From: kesh...@us.ibm.com<mailto:kesh...@us.ibm.com><mailto:kesh...@us.ibm.com> [mailto:kesh...@us.ibm.com] Sent: Tuesday, December 13, 2011 7:23 PM To: R Kaja Mohideen (WT01 - GMT-Telecom Equipment) Cc: jgr...@alumni.princeton.edu<mailto:jgr...@alumni.princeton.edu><mailto:j gr...@alumni.princeton.edu>; xalan-j-users@xml.apache.org<mailto:xalan-j-users@xml.apache.org><mailto :xalan-j-users@xml.apache.org> Subject: RE: Xalan Tranformation Running Slow after about 5K Transformations > I'm wondering why the first few thousands of transformations are running > smoothly and then the performance degrades! Hitting the swapper knee, I suspect. Yes, it's the user's responsibility to release cached information, when it's no longer needed, by discarding the Transformer. ______________________________________ "You build world of steel and stone I build worlds of words alone Skilled tradespeople, long years taught: You shape matter; I shape thought." (http://www.songworm.com/lyrics/songworm-parody/ShapesofShadow.html) Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com> Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
