azure-webjobs

WebJob SDK not working when running in a Service Fabric application

白昼怎懂夜的黑 提交于 2019-11-30 05:21:39
问题 I want to use the WebJob SDK in a stateless service running as a Service Fabric application. Unfortunately I’m not able to get it running properly. Below is part of a test code that reproduces the problem. The “ProcessMethod“ is never invoked. The triggered function “ProcessNotificationsInQueue“ is also never executed (yes, there are items in the queue). The “Health State” of the application is set to “Error” in the Service Fabric Explorer although the application is still running. The

Rename an Azure Function

江枫思渺然 提交于 2019-11-30 04:10:48
How to rename an Azure Function ? I want to replace a default 'HttpTriggerCSharp1' name to my own. At the moment unfortunately this name is included in the function url and there is no option to change it: https://functions-xxx.azurewebsites.net/api/HttpTriggerCSharp1 4c74356b41 The UI does not directly support renaming a Function, but you can work around this using the following manual steps: Stop your Function App. To do this, go under Function app settings / Go To App Service Settings, and click on the Stop button. Go to Kudu Console: Function app settings / Go to Kudu (article about that )

Long running Web Job being aborted by Azure

倾然丶 夕夏残阳落幕 提交于 2019-11-30 03:53:43
I have a Web Job within an Azure website that is being aborted. Its rather long running, taking perhaps 30 mins. It pulls in a lot of data from an Azure SQL database and basically compiles figures used for reporting. Looking at the output logs it would appear that Azure aborts the job with no warning mid way through execution. There is no indication as to why. Is there a way to prevent Azure from aborting a Web Job? The website is hosted within a standard azure website. Thanks Check the stopping_wait_time parameter within webjob-publish-settings.json. The value of the parameter is used in

Deploy subfolders for Azure WebJob

南笙酒味 提交于 2019-11-30 03:29:17
问题 I'm deploying a WebJob to Azure using Visual Studio, but none of the subdirectories in the build output folder of the project are copied to Azure (as per looking in the FTP folder and by virtue of the app not executing correctly). Is there any way to get the deploy to copy all the files and folders across? More info: the subdirectories are from a referenced project and the files do have "Copy Always" set. They do appear in the output build directory of the WebJob project UPDATE: So it seems

Azure webjobs vs scheduler

拥有回忆 提交于 2019-11-30 02:46:02
A very simple question: Why would someone use the Azure Scheduler if Azure WebJobs are free? I couldnt find any topic regarding "azure webjobs vs azure scheduler" The main difference is that the webjob contains everything that the scheduler can do: Scheduler can make HTTP calls WebJob can do that and more (run SQL commands, etc) Sentinel It's 2016. The below answers are no longer accurate. WebJobs now also has a built-in scheduler and the schedule can be defined by a cron expression. When publishing to Azure, you can choose if you want to have the WebJob sparked off by the Scheduler or by the

The 'DefaultConnection-Web.config Connection String' argument cannot be null or empty. VS2013

佐手、 提交于 2019-11-30 02:41:16
When I deploy my project with "Publish as Azure WebJob" using Visual Studio 2013/update 4, I get the error in the title. RickAndMSFT Fixed by removing the following markup from the .pubxml file. You must exit/restart VS after removing the markup (or VS will add it back in). <ItemGroup> <MSDeployParameterValue Include="$(DeployParameterPrefix)DefaultConnection-Web.config Connection String" /> </ItemGroup> Hakan Fıstık Reason of the problem Change and/or add the name of the connection string in the web.config . Solution Select the website project, right click on it, and click publish. Press the

Use connectionstring in WebJob on Azure

无人久伴 提交于 2019-11-30 02:02:23
问题 Is there an easy way to share connection string between website and WebJob on Azure? The only way I found already is to read web.config from console application, but it doesn't look good for me. 回答1: The Azure website and WebJob are sharing the application settings/connection strings set on the Azure portal. So assuming you're using a .NET console application as a WebJob, just use ConfigurationManager to get your connection string (to help test it, just have your app.config have the same

Worker Role vs Web Job

流过昼夜 提交于 2019-11-29 20:07:52
From what I understand both run small repeatable tasks in the cloud. What reasons and in what situations might I want to choose one over the other? Some basic information: WebJobs are good for lightweight work items that don't need any customization of the environment they run in and don't consume very much resources. They are also really good for tasks that only need to be run periodically, scheduled, or triggered. They are cheap and easy to setup/run. They run in the context of your Website which means you get the same environment that your Website runs in, and any resources they use are

Azure WebJob Command Timeout

感情迁移 提交于 2019-11-29 17:14:44
问题 We are having issue with Azure Web Jobs. We created a C# console application, zipped it, and created the new Web Job. It's a c# console app that will constantly hit one of our web services to process items in queue. Whenever we run the Web Job, we are getting the following error: 'cmd /c xxxxxxxx....' aborted due to no output and CPU activity for 121 seconds. You may increase SCM_COMMAND_IDLE_TIMEOUT setting to solve the issue When we increased the SCM_COMMAND_IDLE_TIMEOUT to 600 (10 minutes)

Azure WebJobs and Deployment Slots

匆匆过客 提交于 2019-11-29 16:33:02
问题 What will happen when I deploy a continuously running Azure WebJob with a QueueTrigger (queue connection defined in app.config) into a Deployment Slot (for example "Staging")? Will it start to run and listen to messages in the queue or will only start in the Production slot? My fear is that if will just start processing messages from the queue even tough its not in the Production slot yet. If this is the case, should the queue connectionstring be moved from app.config into Azure Website