TaskOrchestrationContext parameter in orchestrator throws instantiation error

Question

TaskOrchestrationContext parameter in orchestrator throws instantiation error

Zakary Kurzawski 105

I am working on a durable function and copied the template from the product documentation:
https://learn.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-orchestrations?tabs=java
I changed the body of the orchestrator method to fit my application and get no compile errors.
However, when I run the app locally, I get a runtime error:

[2023-06-20T20:55:36.078Z] ---> Microsoft.Azure.WebJobs.Script.Workers.Rpc.RpcException: Result: Failure

Exception: UnsupportedOperationException: Interface can't be instantiated! Interface name: com.microsoft.durabletask.TaskOrchestrationContext

Stack: java.lang.RuntimeException: Unable to create instance of interface com.microsoft.durabletask.TaskOrchestrationContext.

I am running FUNCTIONS_EXTENSION_VERSION ~4 and Java 11.

Zakary Kurzawski 105

Code copied from the documentation:

@FunctionName("HelloCities")
public String helloCitiesOrchestrator(
        @DurableOrchestrationTrigger(name = "ctx") TaskOrchestrationContext ctx) {
    String result = "";
    result += ctx.callActivity("SayHello", "Tokyo", String.class).await() + ", ";
    result += ctx.callActivity("SayHello", "Seattle", String.class).await() + ", ";
    result += ctx.callActivity("SayHello", "London", String.class).await();
    return result;
}

navba-MSFT 27,545 Microsoft Employee Moderator

@Zakary Kurzawski Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

I understand that you are getting the exception for your Durable Function UnsupportedOperationException: Interface can't be instantiated! Interface name: com.microsoft.durabletask.TaskOrchestrationContext

I leveraged the same sample from our QuickStart docs but unable to reproduce this issue. The same sample worked fine at my end.

https://learn.microsoft.com/en-us/azure/azure-functions/durable/quickstart-java?tabs=bash&pivots=create-option-manual-setup

Below is the output response after the Durable Function was triggered by my POST request:

[2023-06-22T04:34:11.582Z] Executing 'Functions.Capitalize' (Reason='(null)', Id=29b46bbc-581d-4d6e-8a31-64677e789902)

[2023-06-22T04:34:11.590Z] Capitalizing: London

[2023-06-22T04:34:11.591Z] Executed 'Functions.Capitalize' (Succeeded, Id=29b46bbc-581d-4d6e-8a31-64677e789902, Duration=8ms)

[2023-06-22T04:34:11.591Z] Function "Capitalize" (Id: 29b46bbc-581d-4d6e-8a31-64677e789902) invoked by Java Worker

[2023-06-22T04:34:12.863Z] Executing 'Functions.Cities' (Reason='(null)', Id=71747054-c358-4f90-91e2-9a463f6bc7a4)

[2023-06-22T04:34:12.873Z] Function "Cities" (Id: 71747054-c358-4f90-91e2-9a463f6bc7a4) invoked by Java Worker

[2023-06-22T04:34:12.875Z] Executed 'Functions.Cities' (Succeeded, Id=71747054-c358-4f90-91e2-9a463f6bc7a4, Duration=11ms)

[2023-06-22T04:34:13.161Z] Executing 'Functions.Capitalize' (Reason='(null)', Id=837513b5-655b-44a4-a6f9-11b3cd862a86)

[2023-06-22T04:34:13.167Z] Capitalizing: Seattle

[2023-06-22T04:34:13.168Z] Executed 'Functions.Capitalize' (Succeeded, Id=837513b5-655b-44a4-a6f9-11b3cd862a86, Duration=6ms)

[2023-06-22T04:34:13.167Z] Function "Capitalize" (Id: 837513b5-655b-44a4-a6f9-11b3cd862a86) invoked by Java Worker

[2023-06-22T04:34:14.520Z] Executing 'Functions.Cities' (Reason='(null)', Id=9a2e12f7-f4ea-48a1-a6b5-1cd1766445ec)

[2023-06-22T04:34:14.527Z] Function "Cities" (Id: 9a2e12f7-f4ea-48a1-a6b5-1cd1766445ec) invoked by Java Worker

[2023-06-22T04:34:14.529Z] Executed 'Functions.Cities' (Succeeded, Id=9a2e12f7-f4ea-48a1-a6b5-1cd1766445ec, Duration=9ms)

[2023-06-22T04:34:15.210Z] Executing 'Functions.Capitalize' (Reason='(null)', Id=3dff0400-2776-4d89-996e-75dc96c5b25f)

[2023-06-22T04:34:15.217Z] Capitalizing: Austin

[2023-06-22T04:34:15.217Z] Executed 'Functions.Capitalize' (Succeeded, Id=3dff0400-2776-4d89-996e-75dc96c5b25f, Duration=7ms)

[2023-06-22T04:34:15.217Z] Function "Capitalize" (Id: 3dff0400-2776-4d89-996e-75dc96c5b25f) invoked by Java Worker

[2023-06-22T04:34:16.155Z] Executing 'Functions.Cities' (Reason='(null)', Id=57963dd2-2708-4098-a11e-a95d59be80bd)

[2023-06-22T04:34:16.164Z] Function "Cities" (Id: 57963dd2-2708-4098-a11e-a95d59be80bd) invoked by Java Worker

[2023-06-22T04:34:16.165Z] Executed 'Functions.Cities' (Succeeded, Id=57963dd2-2708-4098-a11e-a95d59be80bd, Duration=9ms)

Here are the versions which I am using:

Core Tools Version: 4.0.5198 Commit hash: N/A (64-bit)

Function Runtime Version: 4.21.1.20667

I am sharing my complete pom.xml here if that helps.

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
  <groupId>com.function</groupId>
    <artifactId>DURABLENAVBA</artifactId>
    <version>1.0-SNAPSHOT</version>
    <packaging>jar</packaging>

    <name>DURABLENAVBA</name>
    
<properties>
  <azure.functions.maven.plugin.version>1.18.0</azure.functions.maven.plugin.version>
  <azure.functions.java.library.version>3.0.0</azure.functions.java.library.version>
  <durabletask.azure.functions>1.0.0</durabletask.azure.functions>
  <functionAppName>DURABLENAVBA</functionAppName>
</properties>

<dependencies>
  <dependency>
    <groupId>com.microsoft.azure.functions</groupId>
    <artifactId>azure-functions-java-library</artifactId>
    <version>${azure.functions.java.library.version}</version>
  </dependency>
  <dependency>
    <groupId>com.microsoft</groupId>
    <artifactId>durabletask-azure-functions</artifactId>
    <version>${durabletask.azure.functions}</version>
  </dependency>
</dependencies>

<build>
  <plugins>
    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-compiler-plugin</artifactId>
      <version>3.8.1</version>
       <configuration>
        <source>8</source>
        <target>8</target>
      </configuration>
    </plugin>
    <plugin>
      <groupId>com.microsoft.azure</groupId>
      <artifactId>azure-functions-maven-plugin</artifactId>
      <version>${azure.functions.maven.plugin.version}</version>
      <configuration>
        <appName>${functionAppName}</appName>
        <resourceGroup>java-functions-group</resourceGroup>
        <appServicePlanName>java-functions-app-service-plan</appServicePlanName>
        <region>westus</region>
        <runtime>
          <os>windows</os>
          <javaVersion>11</javaVersion>
        </runtime>
        <appSettings>
          <property>
            <name>FUNCTIONS_EXTENSION_VERSION</name>
            <value>~4</value>
          </property>
        </appSettings>
      </configuration>
      <executions>
        <execution>
          <id>package-functions</id>
          <goals>
            <goal>package</goal>
          </goals>
        </execution>
      </executions>
    </plugin>
    <plugin>
      <artifactId>maven-clean-plugin</artifactId>
      <version>3.1.0</version>
    </plugin>
  </plugins>
</build>
</project>

I see that you had mentioned that you had done some modifications in your function. Since the sample provided in our article works fine, Could you please provide us with the minimal modifications that generate this error? Thanks!

Please let me know if you have any queries.

navba-MSFT 27,545 Reputation points Microsoft Employee Moderator

2023-06-26T04:10:21.11+00:00

@Zakary Kurzawski Just following up to check if the above suggestions helped. If you have any further query do let us know. I would be happy to help.
Zakary Kurzawski 105 Reputation points

2023-06-26T20:18:02.4966667+00:00

@navba-MSFT , Thanks for following up.
I have updated my pom to be more inline with what you have and am still getting the error. It looks like the error might be occurring when the TaskOrchestrationContext interface class is getting passed into the Gson method com.google.gson.internal.ConstructorConstructor.newUnsafeAllocator().

The one thing that I am seeing that differs from the set up that you posted is the Core Tools and Function Runtime versions. I have the following:
Azure Functions Core Tools

Core Tools Version: 4.0.4653 Commit hash: N/A (64-bit)

Function Runtime Version: 4.6.1.18388

How do I go about upgrading these to be the versions that you are running:
Core Tools Version: 4.0.5198 Commit hash: N/A (64-bit)

Function Runtime Version: 4.21.1.20667

I did a little research on how to update them but I cannot remember if I installed them using npm on the command line or the installer exe. Does that matter in how I would go about doing this?
Zakary Kurzawski 105 Reputation points

2023-06-26T20:18:53.9066667+00:00

Here is the stack trace of the error that I am getting:
Exception: UnsupportedOperationException: Interface can't be instantiated! Interface name: com.microsoft.durabletask.TaskOrchestrationContext

Stack: java.lang.RuntimeException: Unable to create instance of interface com.microsoft.durabletask.TaskOrchestrationContext. Registering an InstanceCreator or a TypeAdapter for this type, or adding a no-args constructor may fix this problem.

[2023-06-26T19:54:24.827Z] at com.google.gson.internal.ConstructorConstructor$16.construct(ConstructorConstructor.java:275)

[2023-06-26T19:54:24.827Z] at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:211)

[2023-06-26T19:54:24.827Z] at com.google.gson.Gson.fromJson(Gson.java:991)

[2023-06-26T19:54:24.828Z] at com.google.gson.Gson.fromJson(Gson.java:956)

[2023-06-26T19:54:24.828Z] at com.google.gson.Gson.fromJson(Gson.java:905)

[2023-06-26T19:54:24.828Z] at com.microsoft.azure.functions.worker.binding.DataOperations.convertFromJson(DataOperations.java:158)

[2023-06-26T19:54:24.829Z] at com.microsoft.azure.functions.worker.binding.DataOperations.apply(DataOperations.java:114)

[2023-06-26T19:54:24.829Z] at com.microsoft.azure.functions.worker.binding.DataSource.computeByType(DataSource.java:56)

[2023-06-26T19:54:24.829Z] at com.microsoft.azure.functions.worker.binding.RpcStringDataSource.computeByType(RpcStringDataSource.java:5)

[2023-06-26T19:54:24.830Z] at com.microsoft.azure.functions.worker.binding.DataSource.computeByName(DataSource.java:42)

[2023-06-26T19:54:24.830Z] at com.microsoft.azure.functions.worker.binding.RpcStringDataSource.computeByName(RpcStringDataSource.java:5)

[2023-06-26T19:54:24.830Z] at com.microsoft.azure.functions.worker.binding.BindingDataStore.getDataByName(BindingDataStore.java:62)

[2023-06-26T19:54:24.831Z] at com.microsoft.azure.functions.worker.broker.ParameterResolver.resolve(ParameterResolver.java:59)

[2023-06-26T19:54:24.831Z] at com.microsoft.azure.functions.worker.broker.ParameterResolver.resolve(ParameterResolver.java:42)

[2023-06-26T19:54:24.831Z] at com.microsoft.azure.functions.worker.broker.EnhancedJavaMethodExecutorImpl.execute(EnhancedJavaMethodExecutorImpl.java:53)

[2023-06-26T19:54:24.832Z] at com.microsoft.azure.functions.worker.broker.JavaFunctionBroker.invokeMethod(JavaFunctionBroker.java:61)

[2023-06-26T19:54:24.832Z] at com.microsoft.azure.functions.worker.handler.InvocationRequestHandler.execute(InvocationRequestHandler.java:33)

[2023-06-26T19:54:24.832Z] at com.microsoft.azure.functions.worker.handler.InvocationRequestHandler.execute(InvocationRequestHandler.java:10)

[2023-06-26T19:54:24.832Z] at com.microsoft.azure.functions.worker.handler.MessageHandler.handle(MessageHandler.java:45)

[2023-06-26T19:54:24.833Z] at com.microsoft.azure.functions.worker.JavaWorkerClient$StreamingMessagePeer.lambda$onNext$0(JavaWorkerClient.java:92)

[2023-06-26T19:54:24.833Z] at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)

[2023-06-26T19:54:24.833Z] at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)

[2023-06-26T19:54:24.834Z] at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

[2023-06-26T19:54:24.834Z] at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

[2023-06-26T19:54:24.834Z] at java.base/java.lang.Thread.run(Thread.java:834)

[2023-06-26T19:54:24.835Z] Caused by: java.lang.UnsupportedOperationException: Interface can't be instantiated! Interface name: com.microsoft.durabletask.TaskOrchestrationContext

[2023-06-26T19:54:24.835Z] at com.google.gson.internal.UnsafeAllocator.assertInstantiable(UnsafeAllocator.java:118)

[2023-06-26T19:54:24.835Z] at com.google.gson.internal.UnsafeAllocator$1.newInstance(UnsafeAllocator.java:49)

[2023-06-26T19:54:24.836Z] at com.google.gson.internal.ConstructorConstructor$16.construct(ConstructorConstructor.java:272)
navba-MSFT 27,545 Reputation points Microsoft Employee Moderator

2023-06-27T15:15:36.0333333+00:00

@Zakary Kurzawski Thanks for getting back.

Thanks for sharing the detailed callstack. I am checking the error in the background.
Regarding your question about updating the Core Tools Version and Functions runtime version refer the below articles by uninstalling and reinstalling to required version:*
*
https://github.com/Azure/azure-functions-core-tools
https://learn.microsoft.com/en-us/azure/azure-functions/functions-run-local?tabs=windows%2Cportal%2Cv2%2Cbash&pivots=programming-language-java#install-the-azure-functions-core-tools

I see that you had mentioned that you have updated the body of the orchestrator method in your app. Since the sample provided in our docs article works fine, Could you please provide us with the minimal modifications that generate this error? Awaiting your reply.

Zakary Kurzawski 105

@navba-MSFT Thanks. I will look at the articles and update my versions.

I have only modified the method name and the function name in my code.
Everything else is the same as the sample in the documentation :

@FunctionName("ADSEFInboundOrchestrator")
	public String adsefInboundOrchestrator(
	        @DurableOrchestrationTrigger(name = "ctx") TaskOrchestrationContext ctx) {
	    String result = "";
	    result += ctx.callActivity("SayHello", "Tokyo", String.class).await() + ", ";
	    result += ctx.callActivity("SayHello", "Seattle", String.class).await() + ", ";
	    result += ctx.callActivity("SayHello", "London", String.class).await();
	    return result;
	}

Zakary Kurzawski 105 Reputation points

2023-06-27T20:15:44.4333333+00:00

@navba-MSFT I updated core tools on my local environment and that fixed the issue. No more errors and the durable function is now running as expected.
Thanks for all your help.

Accepted answer

0 additional answers

Your answer

Zakary Kurzawski 105 Reputation points

2023-06-20T21:00:18.64+00:00

Code copied from the documentation:

@FunctionName("HelloCities") public String helloCitiesOrchestrator( @DurableOrchestrationTrigger(name = "ctx") TaskOrchestrationContext ctx) { String result = ""; result += ctx.callActivity("SayHello", "Tokyo", String.class).await() + ", "; result += ctx.callActivity("SayHello", "Seattle", String.class).await() + ", "; result += ctx.callActivity("SayHello", "London", String.class).await(); return result; }
navba-MSFT 27,545 Reputation points Microsoft Employee Moderator

2023-06-26T04:10:21.11+00:00

@Zakary Kurzawski Just following up to check if the above suggestions helped. If you have any further query do let us know. I would be happy to help.
Zakary Kurzawski 105 Reputation points

2023-06-26T20:18:02.4966667+00:00

@navba-MSFT , Thanks for following up.
I have updated my pom to be more inline with what you have and am still getting the error. It looks like the error might be occurring when the TaskOrchestrationContext interface class is getting passed into the Gson method com.google.gson.internal.ConstructorConstructor.newUnsafeAllocator().

The one thing that I am seeing that differs from the set up that you posted is the Core Tools and Function Runtime versions. I have the following:
Azure Functions Core Tools

Core Tools Version: 4.0.4653 Commit hash: N/A (64-bit)

Function Runtime Version: 4.6.1.18388

How do I go about upgrading these to be the versions that you are running:
Core Tools Version: 4.0.5198 Commit hash: N/A (64-bit)

Function Runtime Version: 4.21.1.20667

I did a little research on how to update them but I cannot remember if I installed them using npm on the command line or the installer exe. Does that matter in how I would go about doing this?
navba-MSFT 27,545 Reputation points Microsoft Employee Moderator

2023-06-27T15:15:36.0333333+00:00

@Zakary Kurzawski Thanks for getting back.

Thanks for sharing the detailed callstack. I am checking the error in the background.
Regarding your question about updating the Core Tools Version and Functions runtime version refer the below articles by uninstalling and reinstalling to required version:*
*
https://github.com/Azure/azure-functions-core-tools
https://learn.microsoft.com/en-us/azure/azure-functions/functions-run-local?tabs=windows%2Cportal%2Cv2%2Cbash&pivots=programming-language-java#install-the-azure-functions-core-tools

I see that you had mentioned that you have updated the body of the orchestrator method in your app. Since the sample provided in our docs article works fine, Could you please provide us with the minimal modifications that generate this error? Awaiting your reply.
Zakary Kurzawski 105 Reputation points

2023-06-27T15:47:46.07+00:00

@navba-MSFT Thanks. I will look at the articles and update my versions.

I have only modified the method name and the function name in my code.
Everything else is the same as the sample in the documentation :

@FunctionName("ADSEFInboundOrchestrator") public String adsefInboundOrchestrator( @DurableOrchestrationTrigger(name = "ctx") TaskOrchestrationContext ctx) { String result = ""; result += ctx.callActivity("SayHello", "Tokyo", String.class).await() + ", "; result += ctx.callActivity("SayHello", "Seattle", String.class).await() + ", "; result += ctx.callActivity("SayHello", "London", String.class).await(); return result; }
Zakary Kurzawski 105 Reputation points

2023-06-27T20:15:44.4333333+00:00

@navba-MSFT I updated core tools on my local environment and that fixed the issue. No more errors and the durable function is now running as expected.
Thanks for all your help.

Answer 1

navba-MSFT 27,545 Microsoft Employee Moderator

@Zakary Kurzawski While I had a closer look at the exception callstack and compared it with your Core tools version. Seems like your core tools version is too old and the logics to support durable function java is not included in this version of host. That seems to be the reason causing this issue.

Could you please use the latest core tools and try again ? Hope this helps.

navba-MSFT 27,545 Reputation points Microsoft Employee Moderator

2023-06-28T03:14:41.1633333+00:00

@Zakary Kurzawski Thanks for confirming that the above plan resolved your issue.

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Share via

TaskOrchestrationContext parameter in orchestrator throws instantiation error

0 additional answers

Your answer