IV91526: POTENTIAL FILE DESCRIPTOR LEAK WHEN DEREGISTRATING AT AROUND THE SAME TIME AS AN ASYNC CLOSE

APAR status

• Closed as program error.

Error description

• Error Message: ?Too many open files? error reported by the
  application
  .
  Stack Trace: N/A
  .
  Application appears to have file descriptor leak and reports Too
  many open files.
  

Local fix

• NA
  

Problem summary

• There occurs a race condition between registration and socket
  close resulting in file descriptor leak . The issue is addressed
   in Oracle bug JDK-7118373  .
  

Problem conclusion

• The JDK has been updated to perform the checks for the states
  before calling close on the socket and thus avoiding the file
  descriptor leak
  .
  This APAR will be fixed in the following Java Releases:
     7    SR10      (7.0.10.0)
     7 R1 SR4       (7.1.4.0)
     8    SR4       (8.0.4.0)
  .
  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

  JAVA CLASS LIBS

• Fixed component ID

  620700130

Applicable component levels

• R700 PSY

     UP

• R800 PSY

     UP