tag:support.appharbor.com,2010-11-23:/discussions/problems/2468-background-workersAppHarbor: Discussion 2012-03-22T01:37:35Ztag:support.appharbor.com,2010-11-23:Comment/135525752012-02-09T18:29:31Z2012-02-09T18:29:31ZBackground workers<div><p>Hi Peter</p>
<p>You are correct, background workers are not quite ready yet, but
we'll put you on the beta-tester list.</p>
<p>Polling a url is a workable solution, you might want to take a
look at MomentApp: <a href=
"http://momentapp.com/">http://momentapp.com/</a></p>
<p>... and Phil Haacks webbackgrounder: <a href=
"http://haacked.com/archive/2011/10/16/the-dangers-of-implementing-recurring-background-tasks-in-asp-net.aspx">
http://haacked.com/archive/2011/10/16/the-dangers-of-implementing-r...</a></p>
<p>Michael</p></div>friismtag:support.appharbor.com,2010-11-23:Comment/135525752012-02-10T00:37:42Z2012-02-10T00:37:42ZBackground workers<div><p>Thanks - do you have any rough ETA for the background workers?
Any advice on how they will be implemented so that i dont architect
something the wrong way in the meanwhile. I'm really hoping they
will be regular windows services.</p>
<p>Moment App doesnt support polling unfortunately, just a single
hit. Amazon SNS looks promising though..</p></div>peterknealetag:support.appharbor.com,2010-11-23:Comment/135525752012-02-10T01:04:51Z2012-02-10T01:04:51ZBackground workers<div><p>Hopefully we'll have the beta ready soon, but at this point we
can't give firm estimates on when background workers will be
available for testing.</p>
<p>If you design your background worker as a console application
you should be good to go when we launch the feature! That should
also be even easier to implement than a Windows service.</p>
<p>Best,<br>
Rune</p></div>runetag:support.appharbor.com,2010-11-23:Comment/135525752012-03-09T03:26:05Z2012-03-09T03:26:05ZBackground workers<div><p>Can i just clarify something about how these background
processes will work in practice..</p>
<p>I have a Catamaran plan for my production environment, which i
will now configure to use one web and one background worker. That
much is straightforward.</p>
<p>What should i do about my test environment that i also host with
you on just a Canoe plan. I only use it briefly just to sanity
check my release. Do i need to create two applications? one for the
web worker and one for the background worker?</p>
<p>I'm not trying to get around the limitations of that plan.. i'd
just like an environment where i can try out your new background
workers without affecting production just yet.<br>
Thanks!</p></div>peterknealetag:support.appharbor.com,2010-11-23:Comment/135525752012-03-09T03:29:59Z2012-03-09T03:29:59ZBackground workers<div><p>Hi Peter,</p>
<p>You're only charged for the milliseconds that you use workers
beyond the one that's free in the Canoe plan, so you could just
scale your application up with an additional worker while you do
the sanity check on your test environment and then scale it down as
soon as that is done. That way the cost will be reduced
significantly.</p>
<p>Another option, if you want to avoid any costs on that
application at all, is that you could scale your application so
that you test the background worker first, and then your web worker
afterwards. That'll make it hard to verify certain integration
aspects between the two, but if you're OK with that it might be a
good option.</p>
<p>Best,<br>
Rune</p></div>runetag:support.appharbor.com,2010-11-23:Comment/135525752012-03-09T04:07:04Z2012-03-09T04:07:04ZBackground workers<div><p>Is it okay if i just create a seperate applications?<br>
ie:<br>
Release (1 of each worker type assigned)<br>
Test - Web (1 web worker assigned)<br>
Test - App (1 background worker assigned)</p></div>peterknealetag:support.appharbor.com,2010-11-23:Comment/135525752012-03-09T19:14:20Z2012-03-09T19:14:20ZBackground workers<div><p>Hi Peter, the AppHarbor terms don't allow creating multiple
AppHarbor applications with the intent of scaling an app. It would
also be a hassle for you, since it would be difficult to share
configuration and add-ons between the various AppHarbor
applications involved in making your app work.</p>
<p>Michael</p></div>friismtag:support.appharbor.com,2010-11-23:Comment/135525752012-03-17T11:10:48Z2012-03-17T11:10:48ZBackground workers<div><p>Are all of the configuration variables also applied to the
app.config for the as they are with a web.config?<br>
Thanks for your help</p></div>peterknealetag:support.appharbor.com,2010-11-23:Comment/135525752012-03-17T18:17:38Z2012-03-17T18:17:38ZBackground workers<div><p>Indeed they are.</p>
<p>Michael</p></div>friismtag:support.appharbor.com,2010-11-23:Comment/135525752012-03-17T22:35:14Z2012-03-17T22:35:14ZBackground workers<div><p>Any chance that you could tell me if there are any errors being
thrown by my background worker? I have deployed it a couple of
times but unable to get it working.</p>
<p>My application is: mycodeonline and there should be a console
application called MessageProcessorHost running on my worker
process.</p>
<p>I have it configured to send me an email via SendGrid (using the
same credentials as my website) when it starts up but nothing is
coming through. Its my assumption that either a DLL that it depends
on is not being copied across or that the transform process isnt
correctly merging my default settings in my app.config with those
that i have configured via the Configuration Settings tab in my app
harbour account.</p>
<p>Thanks for your help again! :)</p></div>peterknealetag:support.appharbor.com,2010-11-23:Comment/135525752012-03-21T23:58:26Z2012-03-21T23:58:26ZBackground workers<div><p>Is this a duplicate of this discussion by any chance? <a href=
"http://support.appharbor.com/discussions/problems/3143-background-workers-do-not-seem-to-be-running">
http://support.appharbor.com/discussions/problems/3143-background-w...</a></p>
<p>Michael</p></div>friism