When i tried to execute a transformation with xalan 2.1 with many threads and requests i am getting outofmemory error .

When i profiled :
My Observations are :
One instance of "org.apache.xml.utils.XMLReaderManager" loaded by "sun.misc.Launcher$AppClassLoader @ 0x17d5efa0" occupies 10,189,376 (54.13%) bytes. The memory is accumulated in one instance of "java.util.Hashtable$Entry[]" loaded by "<system class loader>".

Is there any specific with xalan or xerces jars.

Thanks & Regards,
Sasi.A

__________________
A. Sasi

You haven't said how big the source document was, or how much memory you allocated to the Java VM. It's not uncommon for XSLT to be memory-hungry: the information you have given is no evidence of a bug.

__________________
Michael Kay
http://www.saxonica.com/
Author, XSLT 2.0 and XPath 2.0 Programmer\'s Reference