Saxon

I think the most likely explanation is that you are using the same JAXP Transformer repeatedly, in which case the documents it reads are held in memory in case they are needed again. You can avoid this by creating a new Transformer for each transformation.

If this is not the case, please show us your code. With performance problems, the devil is always in the detail.

Hi Michael,

Thanks for your quick response, It would be nice to show you the code but due to policy reason I cannot copy/paste any piece of code here. If there is a screen share way that i could walk you over my code that would be nice as we talk over the phone.

By the way I am creating new Transformer every time. I have an EcecutorService with fixed thread pool and I keep creating Transformers and assigning it to the EcecutorService and calling the Futures of the callable object to get to know either success or failure. I create the template only once and the whole logic is driven by Quartz scheduler which keeps polling the DB for any new files to be transformed. When the batch is done and no files to be processed then I am calling GC to get the objects out, the screenshot is sent after 12 hours of idle time. I would hope to get the heap down to some 1G or even less.

Hope I explained in a nutshell. Please let me know if you may require additional information.

Hi Michael,

We are into an another issue right now, For performance improvement we planned to pass pre-generated jaxb nodes to the transformer and if the XSLT has saxon:threads the transformation fails with Null pointer exception pointing the line where saxon:threads is used. This is not consistent for the same XSLT and each time this points to a different XSLT(child having saxon:threads). Should we handle these saxon:threads differently in case of passing pregenerated nodes..?

Transformer trans=getTemplates().newTransformer();

trans.setParameter("xmlDetailsMap", new ObjectValue(xmlDetailsMap));

Using Saxon Extensibility with Saxon:threads is was causing the above mentioned issue. Need help, as I end up no where in improving the performance. If there is any suggestion please pass on some tested code to accomplish this scenario.

Any updates pls.

As I have tried to explain, we can't offer much help unless we can run the failing code and observe the symptoms for ourselves.

From what you are saying, it seems that you are running Saxon in multithreaded mode, but calling external Java code which isn't thread-safe. If that's the case, then you need either to switch multi-threading off, or make the external code thread-safe.