only happens on the el cheapo Azure boxes
and not my dev machine
it seems UpdateState is falling behind on hight throughput
Persist claims this shouldn't happen (obv)
Hi guys, I need some help with IIS and actor system. Last night, I receive Information regarding "Remoting shutdowon" from my asp.net application, and then my windows service which connects through akka remote throws AssociationError. The problem is that once the remote shutdown in asp.net application, it doesn't come back until I hit the IIS with a http request. Is there anyway I can make sure that the actor system will be restart in this case?
you basically have to configure IIS to never, ever, under any circumstances, recycle your ASP.NET application if it goes idle
*out
which would be weird
protip though: your Windows Service should only push to the web app if people are actually using it
if no one is using it and you do a server-push, nothing happens
so I'd design your service relationship that knowing that
that the two services don't always have to both be up - IIS does weird shit and is yet another example of Microsoft trying way too hard to think for the developer
so rather than hack IIS, design your Windows Service so it's still "up" and not constantly trying to call someone who isn't home
that's just my 0.02
never seen it happen locally
I'm the Akka.Remote and Cluster worker bee ;)
no that's what this chatroom is for
@Aaronontheweb BTW, find what is wrong with IIS. Need to set idle to zero as well as regular time interval in recycle option...
do it*
@cduhard correct!
well actually not sure about @Zetanova but I thinkso
*they're
is 1.1 the next release?
like tomorrow possibly
maybe my issue has been addressed