IT31322: ATTEMPTING TO ACCESS AN INTEGRATION SERVICE THAT HAS NEVER STARTED VIA THE ADMINISTRATIVE REST API WILL TRIGGER ABEND

APAR status

• Closed as program error.

Error description

• If an Integration Service type application is deployed with a
  manual start mode (i.e. it is not started when the Integration
  Server starts), then any /apiv2 REST admin call that would
  access details of this Integration Service application will
  abend with the following entries in the stack before the abend:
  
  ImbServiceInstance::getTransportForBindingType(ImbWstring) from
  /opt/mqsi/11.0.0.7/server/lib/libWSLibrary.dylib
  
  ImbServiceApplication::getLiveState(ImbConfigObject*,
  ImbAdminRESTRequest const&, ImbWstring const&) const from
  /opt/mqsi/11.0.0.7/server/lib/libWSLibrary.dylib
  
  ImbAdminRESTHelper::populateConfigObjectForDoGetForRestResource(
  ImbConfigObject*, ImbAdminRESTResource*, ImbAdminRESTRequest
  const&, int, ImbWstring const&) from
  /opt/mqsi/11.0.0.7/server/lib/libAdminServices.dylib
  
  ImbAdminRESTResource::populateConfigObjectForDoGetWithDepth(ImbC
  onfigObject*, ImbAdminRESTRequest const&, int, ImbWstring
  const&) from
  /opt/mqsi/11.0.0.7/server/lib/libAdminServices.dylib
  
  ImbAdminRESTHelper::populateConfigObjectForDoGetForRestResource(
  ImbConfigObject*, ImbAdminRESTResource*, ImbAdminRESTRequest
  const&, int, ImbWstring const&) from
  /opt/mqsi/11.0.0.7/server/lib/libAdminServices.dylib
  
  ImbAdminRESTResource::populateConfigObjectForDoGetWithDepth(ImbC
  onfigObject*, ImbAdminRESTRequest const&, int, ImbWstring
  const&) from
  /opt/mqsi/11.0.0.7/server/lib/libAdminServices.dylib
  
  ImbAdminRESTHelper::populateConfigObjectForDoGetForRestResource(
  ImbConfigObject*, ImbAdminRESTResource*, ImbAdminRESTRequest
  const&, int, ImbWstring const&) from
  /opt/mqsi/11.0.0.7/server/lib/libAdminServices.dylib
  
  ImbAdminRESTResource::populateConfigObjectForDoGetWithDepth(ImbC
  onfigObject*, ImbAdminRESTRequest const&, int, ImbWstring
  const&) from
  /opt/mqsi/11.0.0.7/server/lib/libAdminServices.dylib
  
  ImbAdminRESTResource::doGet(ImbAdminRESTRequest const&,
  ImbAdminRESTResponse&) from
  /opt/mqsi/11.0.0.7/server/lib/libAdminServices.dylib
  
  ImbResource::doGet(ImbAdminRESTRequest const&,
  ImbAdminRESTResponse&) from
  /opt/mqsi/11.0.0.7/server/lib/libMessageServices.dylib
  
  ImbAdminRESTHandlerBase::handleAdminRequest(ImbAdminRESTRequest
  const&, ImbAdminRESTResponse&) from
  /opt/mqsi/11.0.0.7/server/lib/libAdminServices.dylib
  
  Additional Symptom(s) Search Keyword(s):
  

Local fix

• Deploy each Integration Service with an automatic start mode,
  and then manually stop them once the Integration Server has
  finished starting.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of Integration Service applications in IBM App Connect
  Enterprise v11.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  If an Integration Service type application is deployed with a
  manual start mode (i.e. it is not started when the Integration
  Server starts), then any /apiv2 REST admin call that would
  access details of this Integration Service application will
  abend with the following entries in the stack before the abend:
  
  ImbServiceInstance::getTransportForBindingType(ImbWstring) from
  /opt/mqsi/11.0.0.7/server/lib/libWSLibrary.dylib
  ImbServiceApplication::getLiveState(ImbConfigObject*,
  ImbAdminRESTRequest const&, ImbWstring const&) const from
  /opt/mqsi/11.0.0.7/server/lib/libWSLibrary.dylib
  ImbAdminRESTHelper::populateConfigObjectForDoGetForRestResource(
  ImbConfigObject*, ImbAdminRESTResource*, ImbAdminRESTRequest
  const&, int, ImbWstring const&) from
  /opt/mqsi/11.0.0.7/server/lib/libAdminServices.dylib
  ImbAdminRESTResource::populateConfigObjectForDoGetWithDepth(ImbC
  onfigObject*, ImbAdminRESTRequest const&, int, ImbWstring
  const&) from
  /opt/mqsi/11.0.0.7/server/lib/libAdminServices.dylib
  ImbAdminRESTHelper::populateConfigObjectForDoGetForRestResource(
  ImbConfigObject*, ImbAdminRESTResource*, ImbAdminRESTRequest
  const&, int, ImbWstring const&) from
  /opt/mqsi/11.0.0.7/server/lib/libAdminServices.dylib
  ImbAdminRESTResource::populateConfigObjectForDoGetWithDepth(ImbC
  onfigObject*, ImbAdminRESTRequest const&, int, ImbWstring
  const&) from
  /opt/mqsi/11.0.0.7/server/lib/libAdminServices.dylib
  ImbAdminRESTHelper::populateConfigObjectForDoGetForRestResource(
  ImbConfigObject*, ImbAdminRESTResource*, ImbAdminRESTRequest
  const&, int, ImbWstring const&) from
  /opt/mqsi/11.0.0.7/server/lib/libAdminServices.dylib
  ImbAdminRESTResource::populateConfigObjectForDoGetWithDepth(ImbC
  onfigObject*, ImbAdminRESTRequest const&, int, ImbWstring
  const&) from
  /opt/mqsi/11.0.0.7/server/lib/libAdminServices.dylib
  ImbAdminRESTResource::doGet(ImbAdminRESTRequest const&,
  ImbAdminRESTResponse&) from
  /opt/mqsi/11.0.0.7/server/lib/libAdminServices.dylib
  ImbResource::doGet(ImbAdminRESTRequest const&,
  ImbAdminRESTResponse&) from
  /opt/mqsi/11.0.0.7/server/lib/libMessageServices.dylib
  ImbAdminRESTHandlerBase::handleAdminRequest(ImbAdminRESTRequest
  const&, ImbAdminRESTResponse&) from
  /opt/mqsi/11.0.0.7/server/lib/libAdminServices.dylib
  

Problem conclusion

• Integration Services that have not started how behave correctly
  when queried via the administrative REST API.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v11.0      11.0.0.8
  
  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