Uploaded image for project: 'Apache Fineract'
  1. Apache Fineract
  2. FINERACT-1927

Incorrect exception info in BatchAPI response

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 1.9.0
    • 1.9.0
    • Savings

    Description

      Steps to reproduce

      1. Have multiple withdraw and deposit commands for the same savings account in a batchAPI request
      2. Run it in multiple threads multiple times on the same Fineract instance, to achieve 
        org.eclipse.persistence.exceptions.OptimisticLockException

      Current behaviour

      Response body non deterministic, and non related to OptimisticLockException:

      [
      {
      "statusCode": 500,
      "body": "{\"Exception\": java.lang.NullPointerException}"
      }
      ]

      [
      {
      "statusCode": 500,
      "body": "{\"Exception\": java.lang.NullPointerException: Cannot invoke \"java.lang.Integer.intValue()\" because the return value of \"org.apache.fineract.batch.domain.BatchResponse.getStatusCode()\" is null}"
      }
      ]
       

      Expected behavior

      The body should refer to the exception that occurred.

       

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            peter.santa Peter Santa
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment