Background Process Hangs When There's Too Much Unprocessed Output

[samsieber]

I startup a java server in the background with this (a tomcat instance preloaded with a war in this instance), and it hangs after a bit, deadlocking on a System.out.println statement.

After doing some digging, I found the explanation here: http://stackoverflow.com/questions/2783190/java-hangs-when-trying-to-close-a-processbuilder-outputstream

So... basically it renders this useless for me since I can't successfully start long running apps.

Platform: Linux, OS X

[samsieber]

On further investigation, we might be able to use nohup to work around this on *nix platforms (and BSD, like OS X). I'll submit a merge request if I can figure this out.

[nhoughto]

Just use this instead

https://github.com/psxpaul/gradle-execfork-plugin

[samsieber]

If you don't need the process to run after gradle exits and of you don't need to wait for output, then yes, that other plugin seems like an option.