Am 29.12.2016 um 22:18 schrieb John D. Ament: > That's what I thought as well, but the job config doesn't have any timeouts > set. It should, but doesn't. Something in features is causing the spawned > JVM to crash. Does it perhaps need a -Xmx setting?
Thanks for the hint, but I assume: -Xmx2g -Xms256m -XX:MaxPermSize=512m should be enough. @Anatole: I can reproduce the failure locally (with the same stack) - does it work with your settings? Cheers, Phil
