IT27231: UNHANDLED SOCKET EXCEPTION ON INTEGRATION NODE STARTUP

APAR status

• Closed as program error.

Error description

• From IIB 10.0.0.12, on startup on UNIX and Linux platforms, the
  integration node processes no longer inherit undesired file
  descriptors from child processes upon start or restart after
  failure. See APAR IT23390 for details. It implements this by
  calling fcntl() on each owned file descriptor and setting the
  FD_CLOEXEC (close-on-exec) flag. However a bad file descriptor
  causes the following unhandled exception:
  
  (Msg 2/2) BIP3150S: A socket error occurred. Operation:
  ::fcntl(F_SETFD). Error Code: 9. Error Text: Bad file
  descriptor.
  (Msg 1/2) BIP2121E: The thread bootstrap code caught an
  unhandled exception on thread number '12345' with name ''.
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus v10 and IBM App Connect
  Enterprise V11 on UNIX and Linux platforms.
  
  
  Platforms affected:
  AIX, HP-UX Itanium platform, Linux on Power platform, Linux on
  x86 platform, Linux on x86-64 platform, Linux on zSeries
  platform, Solaris x86-64 platform, Solaris SPARC platform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  From IIB 10.0.0.12, on startup on UNIX and Linux platforms, the
  integration node processes no longer inherit undesired file
  descriptors from child processes upon start or restart after
  failure. See APAR IT23390 for details. It implements this by
  calling fcntl() on each owned file descriptor and setting the
  FD_CLOEXEC (close-on-exec) flag. However a bad file descriptor
  causes the following unhandled exception to be logged in the
  system log:
  
  (Msg 2/2) BIP3150S: A socket error occurred. Operation:
  ::fcntl(F_SETFD). Error Code: 9. Error Text: Bad file
  descriptor.
  (Msg 1/2) BIP2121E: The thread bootstrap code caught an
  unhandled exception on thread number '12345' with name ''.
  
  This may cause the integration node process to become
  unresponsive to certain requests, for instance shutdown.
  

Problem conclusion

• The product no longer throws an exception on startup if the
  fcntl() system call fails, but an error is logged if the return
  code from the call is anything other than success or bad file
  descriptor.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.16
  v11.0      11.0.0.4
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available,information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

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

  INTEGRATION BUS

• Fixed component ID

  5724J0540

Applicable component levels