IT20811: RESPONSETIME AND PERFORMANCE ISSUES ARE ENCOUNTERED WHEN USING THE READ USERACCOUNT API

APAR status

• Closed as program error.

Error description

• The updated readUserAccount call takes approximately 60 seconds
  in the debug.jar applied second node, and it takes 215 seconds
  in the first node.
  
  On the other hand, there is no significant performance
  improvement in the other calls. For example, the
  readTradingPartner call takes 215 and 210 seconds in the first
  and second node respectively.
  
  
  While small-sized GET API calls such as, readMailbox call takes
  approximately 30 seconds in both nodes and readMailboxMessages
  call takes 3-4 seconds. So, there is no difference in the
  response time between the two nodes.
  
  
  With the GET API call. The call completed in 30 seconds in the
  first node and 70-75 seconds on the second node.
  It also  showed all the information about the user account,
  along with the suppressed ones.
  

Local fix

• STRRTC - 539766
  GB / GB
  Circumvention: None
  

Problem summary

• Users Affected:
  ALL B2B API users who are using userAccount API.
  
  Problem Description:
  User Account API shows slowness for the default read call
  and specific API User object read call.
  
  Platform Affected:
  All
  

Problem conclusion

• Resolution Summary:
  A code fix is provided.
  
  Delivered In:
  5020602_5
  5020603_3
  

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

  STR B2B INTEGRA

• Fixed component ID

  5725D0600

Applicable component levels

• R526 PSY

     UP