IV66818: INCORRECT BYTE TO CHARACTER CONVERSION

PI30707: SHIP JAVA 7.1 SR2 + IV66608+ IV66375+ IV66944+ IV65517+ IV66818+ IV67220 AS WSAS V855x IFIX

APAR status

• Closed as program error.

Error description

• Error Message: In the only reported instance of this problem it
  surfaced as a NullPointerException during XML processing.
  However, because the problem occurs in very low level code it
  seems likely that the symptoms could include a variety of
  incorrect byte to char conversions, unexpected conversion errors
  and possibly memory corruption.
  .
  Stack Trace: Example
  stack:com.ibm.jtc.jax.xml.bind.v2.model.impl.RuntimeBuiltinLeafI
  nfoImpl$StringImplImpl.parse(RuntimeBuiltinLeafInfoImpl.java:103
  1)atcom.ibm.jtc.jax.xml.bind.v2.model.impl.RuntimeBuiltinLeafInf
  oImpl$StringImplImpl.parse(RuntimeBuiltinLeafInfoImpl.java:1024)
  atcom.ibm.jtc.jax.xml.bind.v2.runtime.reflect.TransducedAccessor
  $CompositeTransducedAccessorImpl.parse(TransducedAccessor.java:2
  48)atcom.ibm.jtc.jax.xml.bind.v2.runtime.unmarshaller.StructureL
  oader.startElement(StructureLoader.java:205)
  .
  

Local fix

• The problem can be avoided by
  either:-Xjit:disableIdiomRecognitionorSetting the shell
  environment variable TR_disablePPCTROT=1.The environment
  variable disables the specific transformation that causes the
  problem and should have a lower overhead than
  Xjit:disableIdiomRecognition which will disable several other
  transformations as well as the problem one.
  

Problem summary

• This is a rare problem that only happens when processing a
  mixture of single and multi-byte encoded characters with very
  specific buffer length and memory alignment characteristics. The
  idiom recognition optimisation replaces the conversion loop with
  a call to a highly optimised assembler routine which under these
  very specific conditions behaved incorrectly.
  

Problem conclusion

• The JIT has been updated so that this case is handled correctly.
  .
  This APAR will be fixed in the following Java Releases:
     7 R1 SR -      (7.1.-.0)
  .
  Contact your IBM Product's Service Team for these Service
  Refreshes and Fix Packs.
  For those running stand-alone, information about the 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

  JIT

• Fixed component ID

  620700124

Applicable component levels

• R130 PSY

     UP