Service Bus trigger not working in Azure portal but works locally with Node.js v4 Azure Functions

Question

I'm using the Node.js v4 programming model for Azure Functions, and I have a Service Bus-triggered function with the following setup:

app.serviceBusQueue('MyFunctionName', {
  queueName: 'myQueueName',
  connection: 'ServiceBusConnectionString',
  handler: azureFunction,
  isSessionsEnabled: true,
});

Host.json:

{
  "version": "2.0",
  "extensionBundle": {
    "id": "Microsoft.Azure.Functions.ExtensionBundle",
    "version": "[4.0.0, 5.0.0)"
  },
  "functionTimeout": "00:04:00",
  "extensions": {
    "serviceBus": {
      "prefetchCount": 10,
      "messageHandlerOptions": {
        "maxConcurrentCalls": 16,
        "autoComplete": true,
        "maxAutoRenewDuration": "00:05:00"
      }
    }
  }
}

Node.js runtime version: 18

Works locally with func start, but messages aren't processed when deployed to Azure portal.

I've verified that:

The connection string is correctly set in Azure's Application Settings (without EntityPath).
The runtime version in both local and Azure portal is v4.
The Function App is running and not in a stopped state.
The queue name and connection match the function definition.

UPDATE: checking insights I could see the error

The 'MyFunctionName' function is in error: The binding type(s) 'serviceBusTrigger' are not registered. Please ensure the type is correct and the binding extension is installed.

Can you share your complete function code? Also, are you using manage type connection string? — Ikhtesam Afrin
– Ikhtesam Afrin, Commented Oct 10, 2024 at 10:07
@IkhtesamAfrin, it is typescript function and I am using Listen type connectionstring. I tested to change to Manage but still not firing the function. — Davide Bracaglia
– Davide Bracaglia, Commented Oct 10, 2024 at 10:30
Please share the screenshot of the environment variable where you have added the connection string @DavideBracaglia — Ikhtesam Afrin
– Ikhtesam Afrin, Commented Oct 10, 2024 at 10:51

Ikhtesam Afrin · Accepted Answer · 2024-10-10 11:19:59Z

1

I have used the given code and have followed below steps to achieve it.

import { app, InvocationContext } from "@azure/functions";

export async function serviceBusQueueTrigger1(message: unknown, context: InvocationContext): Promise<void> {
    context.log('Service bus queue function processed message:', message);
}

app.serviceBusQueue('serviceBusQueueTrigger1', {
    connection: 'ServiceBusConnectionString',
    queueName: 'myqueue',
    handler: serviceBusQueueTrigger1,
    isSessionsEnabled: true
});

Post deployment, I fetched connection string and added in Environment variable as shown below.

enter image description here

Function got triggered upon sending a message in service bus queue.

enter image description here

If it still doesn't fires then check the associated application insight in case of any errors.

enter image description here

answered Oct 10, 2024 at 11:19

Ikhtesam Afrin

6,6902 gold badges4 silver badges11 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Davide Bracaglia Over a year ago

Thanks for the answer. Looking at insights I could see this error: The 'MyFunctionName' function is in error: The binding type(s) 'serviceBusTrigger' are not registered. Please ensure the type is correct and the binding extension is installed.

Ikhtesam Afrin Over a year ago

@DavideBracaglia please share your complete function code

Davide Bracaglia Over a year ago

I tested with same sample code you provieded :) It works locally but not on portal. I was wondering if it has something to do with the fact that we use monorepo. In package.json of the specific project we have @azure/service-bus in dependencies. And if I check the location of service-bus I can see: ├─┬ @edge/[email protected] -> ./apps/b2b │ └── @azure/[email protected] └─┬ @edge/[email protected] -> ./apps/edge └── @azure/[email protected] deduped I use servicebustrigger in edge project.

Ikhtesam Afrin Over a year ago

Did you check the app insights for any errors?

Davide Bracaglia · Accepted Answer · 2024-10-15 07:45:35Z

0

So, after a few hours, I finally discovered what the problem was:

I have a monorepo from which I deploy different function apps. The issue was that the host.json file were not located in the root directory of the function app after deployment.

To check this I went to:

https://<functionAppName>.scm.azurewebsites.net/DebugConsole

Then into site and then wwwroot folder.

Ensure that host.json is there and it is well configured. If it is missing or incorrectly configured, the Azure Functions runtime may not recognize extensions.

answered Oct 15, 2024 at 7:45

Davide Bracaglia

1591 gold badge3 silver badges14 bronze badges

Collectives™ on Stack Overflow

Service Bus trigger not working in Azure portal but works locally with Node.js v4 Azure Functions

2 Answers 2

4 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

4 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related