IZ78404: MESSAGES WRITTEN TO SYSLOG WHEN -XLOG:NONE ENABLED

APAR status

• Closed as program error.

Error description

• Error Message: -Xlog:none is supposed to stop messages being
  written to the syslog however, on Java 6 SR8 (and earlier SRs),
  messages are written to syslog with -Xlog:none enabled.
  .
  This issue can be reproduced  by running the following java
  command, which shows dump messages generated with the JVM stops:
  $ ./java -Xdump:java:events=vmstop -Xlog:none -version
  java version "1.6.0"
  Java(TM) SE Runtime Environment (build
  pap6460sr8-20100409_01(SR8))
  IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 AIX ppc64-64
  jvmap6460sr8-20100401_55940 (JIT enabled, AOT enabled)
  J9VM - 20100401_055940
  JIT  - r9_20100401_15339
  GC   - 20100308_AA)
  JCL  - 20100408_01
  JVMDUMP006I Processing dump event "vmstop", detail
  "#0000000000000000" - please wait.
  JVMDUMP032I JVM requested Java dump using
  '<path>/javacore.20100628.170604.1134826.0001.txt' in response
  to an event
  JVMDUMP010I Java dump written to
  <path>/javacore.20100628.170604.1134826.0001.txt
  JVMDUMP013I Processed dump event "vmstop", detail
  "#0000000000000000".
  .
  Then check the system log to see the JVMDUMP032I message wrongly
  printed there too.
  .
  Stack Trace: N/A
  .
  N/A
  

Local fix

• N/A
  

Problem summary

• The problem is caused when the JVM writes a message to the
  syslog, despite -Xlog:none being specified.
  

Problem conclusion

• The JVM has been updated to respect the -Xlog:none option, and
  not write message to the syslog when it is specified.
  .
  This defect will be fixed in:
  6.0.0 SR9
  

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:

  IZ89805

Fix information

• Fixed component name

  J9 COMMON CODE

• Fixed component ID

  620700127

Applicable component levels

• R600 PSN

     UP