Some more results

Since the error behavior only propagated while running the dmtcp_restart_script.sh through a Java process builder but I never got any error messages or any indication of what went wrong.
I decided to build a small test system and mimick the behavior without having to start up the complete CBAS system.
This system exists out of the process builder and the S3Streamgobblers running the restart script.

And lo and behold the error appeared again but now with additional error output !
Unfortunately it seems to be a Java JVM problem :

20/06 17:36:43 :: 418
20/06 17:36:48 :: 419
20/06 17:36:53 :: 420
#

[error occurred during error reporting (printing fatal error message), id 0x4]

#
#  SIGILL (0x4) at pc=0x00007f2960897dd8, pid=40000
[error occurred during error reporting (printing current thread and pid), id 0x4]

#

[error occurred during error reporting (printing Java version string), id 0x4]


[error occurred during error reporting (printing problematic frame), id 0x4]

#
[error occurred during error reporting (printing core file information), id 0x4]


[error occurred during error reporting , id 0x4]


[error occurred during error reporting , id 0x4]


[error occurred during error reporting , id 0x4]


[error occurred during error reporting , id 0x4]


[error occurred during error reporting , id 0x4]


[Too many errors, abort]

I am currently testing it out with the java JVM from Oracle to see if this shows the same behavior.
I also want to compare this with the regular ProcessBuilder without S3StreamGobbler.