[FINERACT-1927] Incorrect exception info in BatchAPI response

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.9.0
• Fix Version/s: 1.9.0
• Component/s: Savings
• Labels: BeanSalad
• Assignee: Unassigned
• Reporter: Peter Santa
• Created: 03/May/23 14:45
• Updated: 07/Jan/24 10:53
• Resolved: 06/Dec/23 15:23

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.

 

Issue Links

• is a child of: FINERACT-1874 Release Apache Fineract 1.9.0
• links to: GitHub Pull Request #3471