IT49023: INTEGRATION SERVER FAILED TO START UP

APAR status

• Closed as documentation error.

Error description

• After a network outage, the AppConnect Enterprise integration
  node has restarted but one of the integration servers failed to
  start. When trace is enabled, we can see that there are "failed
  to acquire lock" messages.
  

Local fix

• If the integration server failed to start up due to write lock
  access issue, the section: "Integration server failed to start
  up due to write lock access issue" on this
  page:
  https://www.ibm.com/docs/en/app-connect/13.0.x?topic=probl
  ems-resolving-when-starting-integration-node
  can provide hints
  on how to deal with the situation. If the situation was
  initiated by a hanging message flow that led to manual
  terminations, then the guidance under the section "A message
  flow or server is not responsive" on the same page should be
  followed before you consider manually terminating integration
  node processes.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of App Connect Enterprise versions 12 and 13.
  
  
  Platforms affected:
  LinuxX64, AIX
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  Integration server failed to start up due to write lock access
  issue and a message flow is not responsive.
  

Problem conclusion

• If the integration server failed to start up due to write lock
  access issue, the section: "Integration server failed to start
  up due to write lock access issue" on this
  page:
  https://www.ibm.com/docs/en/app-connect/13.0.x?topic=probl
  ems-resolving-when-starting-integration-node
  can provide hints
  on how to deal with the situation. If the situation was
  initiated by a hanging message flow that led to manual
  terminations, then the guidance under the section "A message
  flow or server is not responsive" on the same page should be
  followed before you consider manually terminating integration
  node processes.
  

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

Applicable component levels