We are running JBOSS in a z/OS 64-bit environment, and using Runtime.exec("java ...") to spawn a new JVM that will perform some work that can be performed asynchronously so it will not impact heap usage for the server. Most of the time this works with no problem, but sporadically we will see the following errors and the JBOSS server will crash. The system dump or the javacore doesn't seem to have any useful information in it. As far as I can tell the UTF8 error is a side effect of the FORK OR SPAWN error. I guess the question is, what are the implications of using Runtime.exec() in a JVM that has many threads running and a rather large (>1500MB) heap. This problem seems to have only started occurring after we upgraded our server to use the new v7r0m0 release of the JDK. Is there anything I can look for in the dump that can indicate why the problem occurred?
04.53.43 STC51732 BPXP005I A FORK OR SPAWN ERROR WAS ENCOUNTERED. RETURN CODE 00000070 REASON CODE 0B170023
04.53.47 STC51732 BPXM023I (BLAHADM2) 877
877 JVMJ9VM030E Invalid UTF8 used in JNI function
04.53.47 STC51732 BPXM023I (BLAHADM2) 878
878 JVMDUMP006I Processing dump event "abort", detail "" - please wait.
04.53.47 STC51732 BPXM023I (BLAHADM2) 879
879 JVMDUMP032I JVM requested System dump using 'BLAHQA.PUBLIC.BLAHJBOP.D0
879 413.T085347' in response to an event
Notice: We have upgraded developerWorks Community to the latest version of IBM Connections. For more information, read our upgrade FAQ.
Pinned topic z/OS fork/spawn error with Runtime.exec()
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-05-22T22:39:27Z at 2012-05-22T22:39:27Z by Ian_Partridge