Java process that calls transformations via API runs out of memory

Hi All,

I have a Java process that consumes RabbitMQ messages and submits the payload via the Java API for Transformations to process. It works well - except that the jobs that use the Ruby plugin consume memory that isn't released via Garbage Collection. It's only 2 class files (which I am attaching).

My questions are:

Is there a better way to call the Java API that would more reliably release memory?
Is there something that I may have missed in our approach?
Has anyone had a similar task that they approached differently?

- Short explanation of attached files -
Rabbitqueuemanager.txt is a java file that consumes events off a RabbitMQ queue and passes them to a defined transformation (read from a queues.xml config file)
xformlauncher.txt is a java file that accepts the necessary variables (payload, transformation name, repository credentials) and launches the transformation.

My concern is that if these transformations leak memory - others have the potential. My goal is better encapsulation.

Thanks,

David

Attached Files

• xformlauncher.txt (3.8 KB)
• rabbitqueuemanager.txt (2.8 KB)