Foo Developer created FINERACT-2984:
---------------------------------------
Summary: Interoperation account transactions fail for any account
with a transaction (note lookup parses a null id)
Key: FINERACT-2984
URL: https://issues.apache.org/jira/browse/FINERACT-2984
Project: Apache Fineract
Issue Type: Bug
Components: Accounting
Reporter: Foo Developer
Assignee: Foo Developer
An error occurs when calling Interop causing the request to fail with a
java.lang.NumberFormatException.
Error message:
java.lang.NumberFormatException: Cannot parse null string
Stack trace:
java.lang.NumberFormatException: Cannot parse null string
at java.base/java.lang.Long.parseLong(Long.java:556)
at java.base/java.lang.Long.valueOf(Long.java:950)
at
org.apache.fineract.interoperation.service.InteropServiceImpl.getAccountTransactions(InteropServiceImpl.java:227)
Expected Behavior
The method should handle missing or null values safely and return an
appropriate response instead of throwing an unhandled exception.
Actual Behavior
The method attempts to parse a null string into a Long, resulting in a
NumberFormatException and failure to process the account transactions request.
Technical Investigation
Investigate line 227 of InteropServiceImpl.java.
Identify the value being passed to Long.valueOf() when it is null.
Verify whether the value is missing from the request, configuration, or
retrieved data.
Add appropriate null validation and error handling.
Acceptance Criteria
The source of the null value is identified.
Null or missing values are handled appropriately.
Valid account transaction requests continue to work as expected.
Invalid or incomplete inputs return a meaningful error response instead of an
unhandled exception.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
