microsoft / microsoft/durabletask-java
GRPC error when calling DurableClientContext.getClient
还没有人认领这个 Issue。
- 主要语言
- 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
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 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