A few cosmetic changes and perhaps fixes for qrun and related task problems.

Note: qrun now defined in jcs/qrun.ijs

The main problem was that a task ending could have a delayed close of the
associated socket port and this could, depending on timing, prevent the
proper start of the next task trying to use the same port.

The jcs sockets now set LINGER 0. This should avoid that class of problem.
Initial stress tests all run clean on Linux and Windows.

The other problem was that a server errror in qrun caused a hang. This
wouldn't happen normally if the jobs were well defined and ran to
completion. A way to trigger the qrun server error in Windows was to run a
large number of tasks with large (memory consumption) jobs. This could
exhaust windows swap memory and get an out-of-memory error.

qrun now catches the server error, reports the lse error, and continues.
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to