microsoft / microsoft/durabletask-java

GRPC error when calling DurableClientContext.getClient

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

還沒有人認領這個 Issue。

P2
主要語言
Java
星號
29
分支
18
平均合併
1 天 10 小時
30 天內合併 PR
2

描述

Hi,

I'm experimenting with writing a Java Durable function and have been getting this strange error message when I try and kick off an orchestration using DurableClientContext.getClient.

The issue is transient.
I'm using Java 17.
All the durable function packages are up to date.
The error occurs running locally on windows as-well as on an Azure Function app in the cloud (linux).

The weird thing is the orchestrations all seem to run so I'd like to know if this is safe to ignore.

The error message looks like this:
[2024-02-20T07:21:36.332Z] Feb 20, 2024 6:21:36 PM io.grpc.internal.ManagedChannelOrphanWrapper$ManagedChannelReference cleanQueue [2024-02-20T07:21:36.333Z] SEVERE: *~*~*~ Previous channel ManagedChannelImpl{logId=157, target=localhost:4001} was not shutdown properly!!! ~*~*~* [2024-02-20T07:21:36.333Z] Make sure to call shutdown()/shutdownNow() and wait until awaitTermination() returns true.

and it stems from this call where I am about to kick-off a new orchestration.
[2024-02-20T07:21:36.334Z] java.lang.RuntimeException: ManagedChannel allocation site [2024-02-20T07:21:36.334Z] at io.grpc.internal.ManagedChannelOrphanWrapper$ManagedChannelReference.<init>(ManagedChannelOrphanWrapper.java:102) [2024-02-20T07:21:36.334Z] at io.grpc.internal.ManagedChannelOrphanWrapper.<init>(ManagedChannelOrphanWrapper.java:60) [2024-02-20T07:21:36.335Z] at io.grpc.internal.ManagedChannelOrphanWrapper.<init>(ManagedChannelOrphanWrapper.java:51) [2024-02-20T07:21:36.335Z] at io.grpc.internal.ManagedChannelImplBuilder.build(ManagedChannelImplBuilder.java:655) [2024-02-20T07:21:36.336Z] at io.grpc.ForwardingChannelBuilder2.build(ForwardingChannelBuilder2.java:261) [2024-02-20T07:21:36.336Z] at com.microsoft.durabletask.DurableTaskGrpcClient.<init>(DurableTaskGrpcClient.java:51) [2024-02-20T07:21:36.337Z] at com.microsoft.durabletask.DurableTaskGrpcClientBuilder.build(DurableTaskGrpcClientBuilder.java:61) [2024-02-20T07:21:36.337Z] at com.microsoft.durabletask.azurefunctions.DurableClientContext.getClient(DurableClientContext.java:59)

Is it safe to ignore? Should it be logged out?

Thanks,

Graeme

貢獻指南

開啟貢獻指南

從這裡開始

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

研究方向

從 com.microsoft.durabletask.azurefunctions.DurableClientContext.getClient 開始,追蹤它如何透過 DurableTaskGrpcClientBuilder 建立 com.microsoft.durabletask.DurableTaskGrpcClient。在本機重現 ManagedChannel 警告,並將用戶端生命週期與 gRPC 的關閉指南進行比較;完成標準是判定 channel 是否被不當地保持開啟,以及是否應該防止該警告或以不同方式記錄該警告。

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

評估

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

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

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