Cannot launch ANY process in Java (ProcessBuilder process immediately returns with exit code 128)?

So we "solved" this by killing a large number of the system processes. We think the problem is closely related to the issues described here: arcanadev.com/support/kb/K00000329.aspx with the process trying to call java's exec being out of available heap space or memory. Very strange.

So we "solved" this by killing a large number of the system processes. We think the problem is closely related to the issues described here: arcanadev.com/support/kb/K00000329.aspx, with the process trying to call java's exec being out of available heap space or memory. Very strange.

You should call p.waitFor() before p.exitValue().

Calling p.waitFor() without p.exitValue() also produces 128. – Paul Karlin May 17 at 21:53 I actually wasn't calling p.exitValue() at all and having the same problem. I just added in p.exitValue() to help give additional context (program not even starting) – Zugwalt May 17 at 22:29.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.