Workflow timedout due to activity BLOCKED on Feature.get


We are observing random workflow timeouts and we have the following stack trace.

workflow-method-30DBBBA2B0B145C0BF6BB3EAC73EC1CC@AXkBAgA-TR-ggwc--89671688-e671-4461-ba60-7251ed17f99f: (BLOCKED on Feature.get)
sun.reflect.GeneratedMethodAccessor732.invoke(Unknown Source)

Additional info
SDK: Java Sdk 1.7.1
Server: 1.9.2
Activities: Local activities
Exported the history to a json file - seems to be of 1.2MB size. How do I share this file?

First look seems you have local activity that is never completing. Worth getting thread dump
of the process and take a look to confirm this.

Another thing to look at is if your local activity keeps retrying forever, there is an open issue here regarding local activity startToClose timeout as well as this one regarding completion callback issues.

Could you show parts of your code where you invoke local activities? Please show local activity config as well.

Exported the history to a json file - seems to be of 1.2MB size. How do I share this file?

could you dm it to me by chance?

Tagging @spikhalskiy

Hey @ravikiran,

Please reach out in Temporal Slack to me (@Dmitry) and let’s investigate together. There are several reports of this issue randomly appearing with Local Activities in the last year where people usually don’t follow-up with information and I would love to work with you to dig it out and make it fixed.

The local activity is performing a http request with a timeout configured. So we get a timeout exception and cannot enter a “never completing” state. I do not see any exceptions so retry is not seen.

For those that aren’t in Slack, this issue has been fixed in Java SDK v1.14.0