Carrier threads pinned on object.wait() for Generativeaiinterferenceclient
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 243
- Forks
- 171
- Avg merge
- 30m
- Merged PRs (30d)
- 4
Description
observed thread pinning happening for GenerativeAiInferenceClient for Helidon 4x version for AI calls for OCI sdk.
#2270 "[0x453f951d 0x5e59747f] WebServer socket" virtual
java.base/java.lang.Object.wait0(Native Method)
java.base/java.lang.Object.wait(Object.java:366)
java.base/java.lang.Object.wait(Object.java:339)
com.oracle.bmc.http.internal.SyncFutureWaiter$Waiter.waitAndWork(SyncFutureWaiter.java:61)
com.oracle.bmc.http.internal.SyncFutureWaiter.listenForResult(SyncFutureWaiter.java:32)
com.oracle.bmc.http.internal.ClientCall.callSync(ClientCall.java:1101)
com.oracle.bmc.generativeaiinference.GenerativeAiInferenceClient.chat(GenerativeAiInferenceClient.java:114)
#1582 "[0x453f951d 0x74dfd5cd] WebServer socket" virtual
java.base/java.lang.Object.wait0(Native Method)
java.base/java.lang.Object.wait(Object.java:366)
java.base/java.lang.Object.wait(Object.java:339)
com.oracle.bmc.http.internal.SyncFutureWaiter$Waiter.waitAndWork(SyncFutureWaiter.java:61)
com.oracle.bmc.http.internal.SyncFutureWaiter.listenForResult(SyncFutureWaiter.java:32)
com.oracle.bmc.http.internal.ClientCall.callSync(ClientCall.java:1101)
com.oracle.bmc.generativeaiinference.GenerativeAiInferenceClient.embedText(GenerativeAiInferenceClient.java:143)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Helidon 4.x workload and inspect the listed OCI SDK stack frames, especially SyncFutureWaiter.waitAndWork, ClientCall.callSync, and the GenerativeAiInferenceClient chat and embedText entry points. Compare the observed carrier-thread pinning with the SDK's synchronous-call implementation; done requires a confirmed cause and a tested resolution or a clear report of the limiting component.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100