IBM Support

JR44404: REST API IS SLOW AT PROCESSING XML RESPONSES IN COMPARISON TO JSON

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The default response for REST is JSON. By adding Accept:
    appliation/xml to the HTTP response, the result is XML.  As the
    data set requeted increases in size the processing time for XML
    is non-linear, and the rate for JSON responses in liner.
    
    Example calls
    /rest/bpm/wle/v1/processes/query/IBM.PI_PROCESSLIST_ALL
    rest/bpm/wle/v1/tasks/query/IBM.PI_TASKLIST_ALL
    

Local fix

  • use JSON rather than XML. Some connectors only accept XML so
    converting from JSON back to XML is extra work on the client
    side and is prone to error.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Applications using REST to retrieve         *
    *                  information in XML format.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Degrading performance when returning    *
    *                      response in XML format.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using REST calls to query process information, responses
    resulting in XML format are slower compared to JSON. The
    processing of XML with JAXB is performance intensive and hence
    the longer response time.  However, in a high volume
    environment the performance of these queries may worsen over
    time.
    

Problem conclusion

  • Code changes have been integrated to prevent the degration of
    performance over a period of time with high volume of queries.
    The fact that slower processing to XML format compared to JSON
    is unavoidable, but no longer will the system performance
    deteriorate over time.  The fix will be integrated into the
    next fix pack and an Interim ifix is available on v7.5.1.1.
    
    Install/Dependency information is available in the readme.txt
    on FixCentral. When the user goes to the download files page
    in FixCentral, the readme will be available with the fix
    package as a separate download.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR44404

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-15

  • Closed date

    2013-01-18

  • Last modified date

    2013-01-18

  • 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

    BPM STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R750 PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1"}]

Document Information

Modified date:
07 October 2021