azure-worker-roles

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 API The server failed to authenticate the request

*爱你&永不变心* 提交于 2019-11-29 19:29:31
问题 I have a task ( I tried with worker role and to upload a console app and run the .exe) that should run once a day and gather Azure Metrics of some of my VMs. This works flawlessly locally but on a cloud service I get this Error: Unhandled Exception: Microsoft.WindowsAzure.CloudException: ForbiddenError: The server failed to authenticate the request. Verify that the certificate is valid and associated with this subscription. at Microsoft.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSucces .

WCF service in Azure worker role slow on first request after being idle

家住魔仙堡 提交于 2019-11-29 15:43:32
We have an Azure worker role that exposes a RESTful WCF service (using System.ServiceModel.Web) through a ServiceHost. The performance is irreproachable on massive traffic, but it seems like the response time is significantly higher (more than five seconds) on the first request when the role has been idle for some time. Does anyone know what might cause this? David Makogon The default AppPool timeout is 20 minutes. Might you be running into this? If so, you can add something like this to a startup script to change the timeout: %windir%\system32\inetsrv\appcmd set config -section

How many roles can you have per Azure instance

╄→гoц情女王★ 提交于 2019-11-29 15:26:57
问题 I know that you can only have 1 web role per instance but does this apply to Background roles as well? In more detail can 1 instance run a background role and a web role? 回答1: I think the terminology used in your question is confusing the other responders. In Windows Azure compute, you have a cloud service. A cloud service can be thought of as your overall architecture, or at least the front end, the middle tier, etc (any tier where there is compute as opposed to storage). For example your

azure role not starting after windows update 10February

ⅰ亾dé卋堺 提交于 2019-11-29 13:12:42
After installation of windows update on 10th February 2016, the azure roles are not starting in emulator (Full/Express). The logs show below [00005748:00006624, 2016/02/14, 12:03:24.391, FATAL] Role process exited with exit code of -2147024809 [00005748:00006624, 2016/02/14, 12:03:24.397, INFO ] Stopping role: deployment25(0).AzureCloudService2.WebRole1_IN_0. Notify: False Recycle: False StopTimeout: 30 [00005748:00006624, 2016/02/14, 12:03:24.398, IMPRT] State of deployment25(0).AzureCloudService2.WebRole1_IN_0 changed from RoleStateBusy to RoleStateStopping. [00005748:00006624, 2016/02/14,

Azure Roles and Instances

霸气de小男生 提交于 2019-11-29 10:42:28
Can I have a Web Role and a Worker role run on the same instance, or do I have to obtain 2 separate hosting instances and pay twice the amount I would otherwise? I have a WCF Web API that I want to host on Azure. I also have a Worker Role that listens to a Queue in Azure Storage. Every time a message is added to the Queue, it will obtain that and run a small task depending on the message. I was wondering if I can just run these two on the same instance or not. David Makogon "Worker Role" and "Web Role" are just simple templates for "Windows Server 2008 with IIS running" and "Windows Server

FTP to Azure Blob Storage

做~自己de王妃 提交于 2019-11-29 07:37:37
问题 I had to setup secure FTP to Azure Blob Storage using popular FTP clients (like FileZilla, for example). After doing lot of research, I came across a link that says: Deployed in a worker role, the code creates an FTP server that can accept connections from all popular FTP clients (like FileZilla, for example) for command and control of your blob storage account. Following the instructions of the link, I had implemented the same and deployed the worker role on Azure production environment and

Quartz.Net Jobs in Azure WebRole

别说谁变了你拦得住时间么 提交于 2019-11-29 07:25:12
I'm currently porting a WCF Service Project over to an Azure Role. Until now the library containing the service also hosted a Quartz.Net JobFactory for some lightweight background processing (perdiodically cleaning up stale email confirmation tokens). Do I have to move that code into a seperate worker role? BitKFu No you don't have to setup a separate worker role. You simply have to start a background thread in your OnStart() Method of your Web Role. Give that thread a Timer object that executes your method after the given timespan. Due to this you can avoid a new worker role. class

The type initializer for 'Microsoft.WindowsAzure.ServiceRuntime.RoleEnvironment' threw an exception

半城伤御伤魂 提交于 2019-11-29 04:35:06
I am trying to use Windows Azure Caching to store sessions in a MVC4 application. I build a application following steps from Link but when i try to make object of DataCache using below code line. DataCache cache = new DataCache("default"); Errors occurs: Microsoft.WindowsAzure.ServiceRuntime.dll not found or version mismatched, I updated my Windows Azure Emulator version to 2.0.0 and install WindowsAzure.Caching package version 2.0.0.0 using NuGet package installer. Now the error changes to "The type initializer for 'Microsoft.WindowsAzure.ServiceRuntime.RoleEnvironment' threw an exception." I

Worker Role vs Web Job

廉价感情. 提交于 2019-11-28 15:55:08
问题 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? 回答1: 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