IV73361: TRACE TRIGGER ACTION 'ABORT' IGNORED.

APAR status

• Closed as program error.

Error description

• Error Message: When running the JVM with trace enabled to
  trigger an operating system abort on a trace point or method
  call no abort occurs
  For example when running with:
  > java
  "-Xtrace:print=mt,trigger=method{java/lang/String.length,abort}"
  -version
  the JVM prints out the version information and exits normally.
  .
  Stack Trace: N/A
  .
  Changing the action confirms that the trigger clause is being
  processed correctly.
  For example running with:
  > java
  "-Xtrace:print=mt,trigger=method{java/lang/String.length,sleep}"
  -version
  causes the JVM to sleep for 30 seconds every time String.length
  is invoked.
  

Local fix

• A similar trigger action "segv" exists to allow testing of crash
  situations. It has a similar effect to raising abort() - the JVM
  will terminate abruptly.
  

Problem summary

• The problem was caused by the "abort" trigger action being
  ignored.
  

Problem conclusion

• The trigger action "abort" will now raise an operating system
  abort() from within the JVM. After abort is called platform
  specific error handling will occur and the JVM will be
  terminated.
  .
  This APAR will be fixed in the following Java Releases:
     7    SR9 FP 10 (7.0.9.10)
     6 R1 SR8 FP7   (6.1.8.7)
     8    SR1 FP10  (8.0.1.10)
     7 R1 SR3 FP10  (7.1.3.10)
  .
  Contact your IBM Product's Service Team for these Service
  Refreshes and Fix Packs.
  For those running stand-alone, information about the available
  Service Refreshes and Fix Packs can be found at:
             https://www.ibm.com/developerworks/java/jdk/
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  J9 COMMON CODE

• Fixed component ID

  620700127

Applicable component levels

• R260 PSY

     UP

• R270 PSY

     UP