Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Incident: Connection error while querying ODataRequestRead – HTTP pool closed

Aperta
#1,301 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
java
Ambito
api, backend

Direzione di ricerca

Start with the attached error_trace.log and the SDK call shown in the issue, then trace where the HTTP connection pool is created and shut down during concurrent OData reads. Confirm the lifecycle causing Connection pool shut down and document a reproducible explanation or verified fix for the reported CAPm deployment scenario.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

question
Ask the Question

We are experiencing an intermittent issue on different days and especially during periods of higher concurrent request loads in a CAPm service deployed on SAP BTP Cloud Foundry. This problem occurs on a large scale and prevents execution flows from completing successfully.  The application is deployed on SAP BTP Cloud Foundry and uses SAP Cloud SDK for OData consumption (always with destination service)

The error is:

HTTP 500 Error
GET EventHandler /odata/v2/lm/LMManagement/LibrettoMisura?$filter=Lcl eq '123456'

The logs show an error while executing the READ event of the LMManagement.LibrettoMisura entity. The immediate cause recorded is:

ODataConnectionException: Connection failed
Caused by: java.lang.IllegalStateException: Connection pool shut down

(A trace log with detailed information is attached. error_trace.log)

The error occurs at the following line of code when using the SAP SDK:

Image

The message indicates that the HTTP connection pool had already been closed when the request attempted to query the OData service.

Why would the SDK shut down the HTTP connection pool when our application does not explicitly close the destination, HTTP client, or any related connection resources? We are not performing any close() operation in the service code.

Thank for your support.

Lingua principale
Java
Stelle
41
Fork
33
Merge medio
22h 16m
PR unite (30g)
19

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di SAP/cloud-sdk-java

Tutte le issue di SAP/cloud-sdk-java

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.