LI81326: GATEWAYSCRIPT POLICIES WITHIN LARGE APIS THAT USE MULTIPLE GETVARIABLE OR GETCONTEXT FUNCTION CALLS MAY BE LATENT

APAR status

• Closed as program error.

Error description

• The getContext function, which may be called directly or is
  called indirectly from the getvariable function call, was
  parsing a JSON object with metadata from the API on every
  invocation. The larger the API, the longer the latency of a
  single call. The more calls within a GatewayScript policy to
  these
  functions, the longer the policy latency.
  

Local fix

Problem summary

• <span style="background-color:rgb(255, 255, 255)">GatewayScript
  code, either API Connect framework code or customer written code
  in a GatewayScript policy, that issue multiple apim.getContext
  and apim.getvariable function calls would experience unnecessary
  latency as the functions were </span><span
  style="background-color:rgb(255, 255, 255)">parsing a JSON
  object with metadata from the API on every </span><span
  style="background-color:rgb(255, 255, 255)">invocation. The
  larger the API, the longer the latency of a </span><span
  style="background-color:rgb(255, 255, 255)">single call. The
  more calls within the policy to these </span><span
  style="background-color:rgb(255, 255, 255)">functions, the
  longer the policy latency. This JSON object is now parsed once
  and cached with subsequent calls simply returning the cached
  object.</span>
  

Problem conclusion

• <span style="background-color:rgb(255, 255, 255)">A fix will be
  delivered in the API Connect 5.0.8.8 GA </span><span
  style="background-color:rgb(255, 255, 255)">and 2018.4.1.10 GA
  releases.</span>
  

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

• R508 PSY

     UP