Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Incident: Connection error while querying ODataRequestRead – HTTP pool closed

未關閉
#1,301 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
35/100
Issue 類型
缺陷
描述清晰度
需要釐清
活躍度
活躍
技術堆疊
java
領域
api, backend

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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.

主要語言
Java
星號
41
分支
33
平均合併
22 小時 16 分鐘
30 天內合併 PR
19

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

SAP/cloud-sdk-java 的其他 Issue

查看 SAP/cloud-sdk-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。