LI80449: LOCKING PROBLEM WITH SERVICE REGISTRATION FLOW

APAR status

• Closed as program error.

Error description

• If there is a registration failure on the first time due to some
  reason like wrong endpoint etc .. and on retrying you use with
  same name, the row lock in the Database remains for the given
  name prevening the registration to proceed further .
  Steps to reproduce the problem:
  Create a gateway service with wrong / bad endpoint.
  Try to recreate with same name
  Result:
  It fails with the message:
  ---
  Failed to create gateway service GW.
  An error occurred communicating with the gateways subsystem.
  500 API Error.
  ---
  In the apim log you see entries such as:
  [b0975a9c-1272-4aa2-8c30-fccaf8ee1fe6]  - lib/db::applyLock:
  The resource apim.gateway_service_by_ns_name
  45fc9667-1886-4b50-a16e-1e02d50a
  eddc:2c944027-a2df-460a-a653-b3b3f528c034 gw is in use by
  another request, error code: ERR_LOCK
  Fri, 23 Nov 2018 09:11:56 GMT bhendi:error
  [b0975a9c-1272-4aa2-8c30-fccaf8ee1fe6] lib/db::insert: error: {
    "stack": "TypeError: Cannot read property 'toString' of
  undefined
    at applyLock
  (/app/node_modules/bhendi/lib/db.js:612:210)
    at
  <anonymous>
    at process._tickCallback
  (internal/process/next_tick.js:188:7)",
    "message": "Cannot read property 'toString' of undefined"
  }
  Fri, 23 Nov 2018 09:11:56 GMT bhendi:error
  [b0975a9c-1272-4aa2-8c30-fccaf8ee1fe6] Error in POST
  post:/api/orgs/:org/availability-zones/:availabilityzone/gateway
  -services (gateway_service.js:create)
   - status : 500
   - message: Cannot read property 'toString' of undefined
   - stack : TypeError: Cannot read property 'toString' of
  undefined
    at applyLock (/app/node_modules/bhendi/lib/db.js:612:210)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
   - errors : undefined
  Fri, 23 Nov 2018 09:11:56 GMT audit
  [b0975a9c-1272-4aa2-8c30-fccaf8ee1fe6] Stack trace for response
  error: Error: Cannot read property 'toString' of undefined
    at error (/app/node_modules/bhendi/lib/bhendiUtil.js:51:11)
    at dispatch (/app/node_modules/bhendi/mw/dispatcher.js:486:21)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
  Fri, 23 Nov 2018 09:11:56 GMT audit
  [b0975a9c-1272-4aa2-8c30-fccaf8ee1fe6]
  =========================================================
  Fri, 23 Nov 2018 09:11:56 GMT audit
  [b0975a9c-1272-4aa2-8c30-fccaf8ee1fe6] Failure 500 response
  (POST
  /api/orgs/45fc9667-1886-4b50-a16e-1e02d50aeddc/availability-zone
  s/availability-zone-default/gateway-services)
  Fri, 23 Nov 2018 09:11:56 GMT audit
  [b0975a9c-1272-4aa2-8c30-fccaf8ee1fe6]
  ========================================================
  [b0975a9c-1272-4aa2-8c30-fccaf8ee1fe6] {
    "status": 500,
    "message": [
      "Cannot read property 'toString' of undefined"
    ]
  }
  

Local fix

• Choose a different name for your service and try again to
  register
  

Problem summary

• When the users try to some activity in UI that involves cross
  micro service communication (like login or gw/portal
  registration), they face an issue trying to re-register or
  re-login, with an error message like `Another resource already
  exists`. The root cause of the issue is a delayed response from
  microservice (lur, gw, portal) to apim, and response time
  exceeding 60 secs.
  

Problem conclusion

• The fix is targeted for inclusion in IBM API Management fixpack
  V2018.4.1.2.
  

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

  API CONNECT ENT

• Fixed component ID

  5725Z2201

Applicable component levels

• R18X PSY

     UP