Hey Alexios,
thanks a lot for your help. I read some time yesterday and also came to the
conclusion to use the ProcessBuilder; i just wanted to test how much time it
will take to spawn a new process for every transformation and use the Object
In/Out Streams for handling the communication.
To avoid waiting until the memory usage gets high, start the JVM with the
following options which will write the heap dump when an out of memory error
occurs. I use them in production systems, there is no overhead.
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/diskWithFreeSpace/dumps
Note
Hi Normen,
The Java Thread Model does not support forcefully stopping a thread executing
arbitrary code. Thread.stop() is deprecated as it unlocks all the monitors it
has locked and other threads may view an inconsistent state of protected
objects. Thread.interrupt() does not guarantee when or
Hey there,
using FOP for quite some time now, thanks everyone for all the fine
development.
Iam running FOP 2.0 embedded into a Servlet on Tomcat 8.0.x with Java8 on a
Windows Machine (server 2012 R2).
Usually we have no problems but from time to time during the transformation
