IT33093: INTEGRATION NODE REPEATEDLY ABENDS ON STARTUP IF SERVER UNABLE TO START

APAR status

• Closed as program error.

Error description

• On integration node startup, the node will start and monitor any
  defined integration servers. If an integration server fails to
  stay running once started, the integration node will try to
  re-start it and re-adopt it. On Windows, if the integration
  server process has stopped before the node attempts to re-adopt
  it, an exception is thrown which is not caught and this causes
  the integration node (bipbroker) process to terminate. The
  following information will be seen in the abend file.
  
  Function: ImbAbend::unhandledExceptionFilterInternal()
  AbendAction: 3
  
  ---> Inserts <---
  An Unhandled Exception detected in process 1234, on thread
  0x5678.
  Type: EXCEPTION_UNKNOWN_TYPE: E06D7363 (E06D7363).
  
  ---> Last Errors <---
  Note these error codes are not necessarily reliable
  GetLastError() returned: 87
  errno          returned: 0
  
  
  Stack Backtrace:
  
  KERNELBASE!RaiseException
  VCRUNTIME140!_CxxThrowException
  bipbroker!??4ImbShared@@QEAAAEAV0@AEBV0@@Z
  bipbroker!??4ImbShared@@QEAAAEAV0@AEBV0@@Z
  bipbroker!??4ImbShared@@QEAAAEAV0@AEBV0@@Z
  bipbroker!??4ImbShared@@QEAAAEAV0@AEBV0@@Z
  bipbroker!??4ImbShared@@QEAAAEAV0@AEBV0@@Z
  bipbroker!??4ImbShared@@QEAAAEAV0@AEBV0@@Z
  bipbroker!??4ImbShared@@QEAAAEAV0@AEBV0@@Z
  ucrtbase!_o__realloc_base
  KERNEL32!BaseThreadInitThunk
  ntdll!RtlUserThreadStart
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM App Connect Enterprise V11 on Windows.
  
  
  Platforms affected:
  Windows on x86-64 platform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  On integration node startup, the node will start and monitor any
  defined integration servers. If an integration server fails to
  stay running once started, the integration node will try to
  re-start it and re-adopt it. On Windows, if the integration
  server process has stopped before the node attempts to re-adopt
  it, an exception is thrown which is not caught and this causes
  the integration node (bipbroker) process to terminate.
  
  The following information will be seen in the abend file, with
  GetLastError() reporting a value of 87 meaning that the supplied
  parameter is incorrect, in this case the process identifier for
  the child DataFlowEngine process.
  
  Function: ImbAbend::unhandledExceptionFilterInternal()
  AbendAction: 3
  
  ---> Inserts <---
  An Unhandled Exception detected in process 1234, on thread
  0x5678.
  Type: EXCEPTION_UNKNOWN_TYPE: E06D7363 (E06D7363).
  
  ---> Last Errors <---
  Note these error codes are not necessarily reliable
  GetLastError() returned: 87
  errno          returned: 0
  
  Stack Backtrace:
  
  KERNELBASE!RaiseException
  VCRUNTIME140!_CxxThrowException
  bipbroker!??4ImbShared@@QEAAAEAV0@AEBV0@@Z
  bipbroker!??4ImbShared@@QEAAAEAV0@AEBV0@@Z
  bipbroker!??4ImbShared@@QEAAAEAV0@AEBV0@@Z
  bipbroker!??4ImbShared@@QEAAAEAV0@AEBV0@@Z
  bipbroker!??4ImbShared@@QEAAAEAV0@AEBV0@@Z
  bipbroker!??4ImbShared@@QEAAAEAV0@AEBV0@@Z
  bipbroker!??4ImbShared@@QEAAAEAV0@AEBV0@@Z
  ucrtbase!_o__realloc_base
  KERNEL32!BaseThreadInitThunk
  ntdll!RtlUserThreadStart
  

Problem conclusion

• The product now catches the exception if thrown from creating a
  child process and will log the error. It also does additional
  checking on the process before attempting to adopt it.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v11.0      11.0.0.10
  
  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

  APP CONNECT ENT

• Fixed component ID

  5724J0550

Applicable component levels