You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Bharath Gowda (Jira)" <ji...@apache.org> on 2025/09/24 12:07:00 UTC
[jira] [Created] (FINERACT-2380) Fineract client to enable all sorts of http clients
Bharath Gowda created FINERACT-2380:
---------------------------------------
Summary: Fineract client to enable all sorts of http clients
Key: FINERACT-2380
URL: https://issues.apache.org/jira/browse/FINERACT-2380
Project: Apache Fineract
Issue Type: Improvement
Affects Versions: 1.10.1
Reporter: Bharath Gowda
We have load balancing issue between our internal component (called Fineract adapter) to Fineract Read service, due to kube-proxy. It doesn’t recycle the connections when we have steady traffic. Also current okhttpclient doesn’t have option to recycle the connections.
I like to enable Feign ([https://github.com/OpenFeign/feign]) with configuration Time-To-Live (TTL) for HTTP connection pools, So that connections are automatically refreshed to prevent stale connections to load-balanced endpoints
* Implement configurable TTL for PoolingHttpClientConnectionManager
* Support both OkHttpClient and Apache HttpClient 5.x configurations
* Add properties for connection max age settings
* Ensure connections are closed after TTL expires
*Acceptance criteria*
* Introduce the a new module based on the existing fineract-client module, but in this module the generated Fineract client shall be using openFeign (latest version: 13.6)
* Similarly as existing solution services and model classes should be generated by OpenAPI and OpenAPI generation should generate feign library for the generated classes
* Model and generated service APIs should match with existing solutions (same capabilities)
** Same request / response models
** Same exposed APIs and parameter list
* It should use Feign Apache HttpClient as http client implementation
* Generated fineract-client can be used to communicate with Fineract backend
** some initial integration tests
--
This message was sent by Atlassian Jira
(v8.20.10#820010)