Specifying ‘limit=0′ may Cause Service Outage (Fixed)

This bug has been fixed.

Fixed Version

  • Version 9.9.5

Affected Version and Operation

  • Version 9.9.0 or later (SaaS Edition)
  • Sending an API Request (/API/OR/ProcessInstance/list) with specifying limit=0 in parameter.

Bug Details

  • Occurs in operating:
    • Sending a Request of Moitoring API with specifying limit=0 in parameter.
    • Corresponding API
      • /API/OR/Workitem/list
      • /API/OR/Workitem/listCsv
      • /API/OR/Workitem/listCsvUtf16
      • /API/OR/ProcessInstance/list
      • /API/OR/ProcessInstance/listCsv
      • /API/OR/ProcessInstance/listCsvUtf16
  • What will occur
    • ‘limit = 0′ does not function correctly. Behaving as to acquire all the subject matter of the data.
      • Attempting to retrieve all the records which is more than 1000 that exceeding limit of API.
    • As the result, A Memory Shortage error will occur in our Server Computer when the number of the target is too large. The Application will crash.

Workaround・Recovery

  • Please do not specify ‘limit = 0′ to parameter when sending a request using the Monitoring API.
    • The default value of ‘limit’ is ‘1’. When a parameter is not specified it will retrieve only one record.
  • This bug is due to be fixed in the coming release version.