Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
When a submitted ManagedReservation fails to launch, it is difficult for the user to determine what went wrong. There are (at least) three problems to be addressed:
1. There is no user log file
2. The Agent Reason shown by WS is "Discontinued"
3. The Exit Code shown by WS is "0"
This problem can be recreated by, for example, submitting a Managed Reservation with an environment string 128K characters long. In this case, the Agent's log clearly shows the problem, but this is inaccessible to user:
09 Feb 2016 09:20:47,790 ERROR Agent.DuccCommandExecutor - J[19] T[349] exec 19
java.io.IOException: Cannot run program "/users1/degenaro/svn/apache/ducc/workspace/bluejws67/install/apache-uima-ducc-2.1.0-SNAPSHOT/admin/amd64/ducc_ling": error=7, Argument list too long
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1040)
at org.apache.uima.ducc.agent.launcher.DuccCommandExecutor.doExec(DuccCommandExecutor.java:770)
at org.apache.uima.ducc.agent.launcher.DuccCommandExecutor.startProcess(DuccCommandExecutor.java:721)
at org.apache.uima.ducc.agent.launcher.DuccCommandExecutor.exec(DuccCommandExecutor.java:277)
at org.apache.uima.ducc.agent.launcher.CommandExecutor.call(CommandExecutor.java:194)
at org.apache.uima.ducc.agent.launcher.CommandExecutor.call(CommandExecutor.java:35)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:345)
at java.util.concurrent.FutureTask.run(FutureTask.java:177)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626)
at java.lang.Thread.run(Thread.java:780)
Caused by: java.io.IOException: error=7, Argument list too long
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(UNIXProcess.java:139)
at java.lang.ProcessImpl.start(ProcessImpl.java:163)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1032)
... 10 more