New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not trigger Java Function by Storage trigger: The binding type(s) 'queueTrigger' are not registered #956

Open
romanovs opened this Issue Sep 18, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@romanovs

romanovs commented Sep 18, 2018

I have Functions based on Java, which are triggered by Storage (queue, blob). In the end of August, it discontinued triggering by Storage. Looks like it is connected with the latest changes in the Runtime engine.

I can see this error message in Portal:
"Function ({name}) Error: The binding type(s) 'queueTrigger' are not registered. Please ensure the type is correct and the binding extension is installed."
The same for 'blobTrigger'.

I confirmed I have this settings set:
FUNCTIONS_EXTENSION_VERSION=beta
FUNCTIONS_WORKER_RUNTIME=java

Also confirmed that 'host.json' contains this property:
"version": "2.0"

I opened the Kudu Console and did this:

  1. Following the instruction (https://github.com/Azure/azure-functions-host/wiki/Updating-your-App-(portal)) I faced that there is no 'bin' directory and no 'extensions.csproj'. I created this file manually, redeployed the Function and executed this command:
    'dotnet build extensions.csproj -o bin --no-incremental --packages D:\home.nuget'
    After Function restart, nothing changed: the Function is still not triggered and the Error Message is still present.

  2. Tried to execute this command too, but faced this command can not be executed from Kudu Console:
    'func extensions install --package Microsoft.Azure.WebJobs.Extensions.Storage --version 3.0.0-beta8'

Can you please help me to figure the issue out?

@romanovs

This comment has been minimized.

Show comment
Hide comment
@romanovs

romanovs Sep 18, 2018

I'm sorry if I took your time. It appeared that following the instruction I didn't update the version of ExtensionsMetadataGenerator . Now it looks to work well.

And I'm wondering if we have to do all the steps from the instruction everytime for every new Function App?

romanovs commented Sep 18, 2018

I'm sorry if I took your time. It appeared that following the instruction I didn't update the version of ExtensionsMetadataGenerator . Now it looks to work well.

And I'm wondering if we have to do all the steps from the instruction everytime for every new Function App?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment