Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Incident: Connection error while querying ODataRequestRead – HTTP pool closed

Abierto
  • ¿Algo no está bien?
#1,301 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
java
Área
api, backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Java
Estrellas
41
Forks
33
Merge medio
1 d 8 min
PR fusionados (30 d)
16

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de SAP/cloud-sdk-java

Todos los issues de SAP/cloud-sdk-java

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.