IZ44826: INCORRECT BEHAVIOUR OF MAPPEDBYTEBUFFER.FORCE

APAR status

• Closed as program error.

Error description

• Error Message: MappedBytebuffer.Force does not flush the data.
  .
  Stack Trace: N/A
  .
  MappedBytebuffer.Force does not flush the data whereas force
  method of FileChannel flushes the data.
  This means that during recovery from extreme errors, data
  that was guaranteed to be written to the transaction
  log by the JVM is actually missing and this results in
  incorrect determination that resources have not been
  been committed when they have.  This results in inconsistant
  resource states.
  

Local fix

Problem summary

• The Windows API FlushFileBuffers was not invoked after calling
  FlushViewOfFile and hence the data in buffer was not completely
  written to disk when JVM exited abnormally.
  

Problem conclusion

• This defect will be fixed in:
  5.0.0 SR11
  .
  Have invoked Windows API FlushFileBuffers after FlushViewOfFile
  to ensure all the data in buffer is written to disk.
  .
  To obtain the fix:
  Install build 20090916 or later
  

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

  JAVA 5 J9 COMMO

• Fixed component ID

  620500127

Applicable component levels

• R500 PSN

     UP