In a situation when a job request that generates a big file (at least 10G) (for example via dd command), while job is executing the unicorex becomes unresponsive, and the gateway is not able to communicate with it. During that if a client supposedly queries for the job status or generally interacts, it sees an exception. Please find attached the exception snippet from the gateway logs.
This problem can be seen with the NO-BATCH deployments, but not with the ones deployed on batch systems such as Torque.
Note: As a workout I have also tried to extend timeout attributes on gateway, unicorex (wsrflite.xml, xnjs_legacy.xml), however they didn't solve this issue.
Log in to post a comment.