gethemant at gmail.com
Sat Jan 26 21:03:19 EST 2008
On Sat, Jan 26, 2008 at 8:25 PM, Meech <meechman at gmail.com> wrote:
> I thought you did not _have_ to exit your workers, that they could just hang
> out and process requests. And most of my stale, open connections are the
> result of ask_status calls, not sure these hit (or need) a worker? I'll
> try it though.
> Thanks. I haven't really run into any barriers yet, I'm just used to
> watching netstat to make sure all the various pieces and parts are awake and
> listening. My work rig is Windows, and I find myself checking netstat a
> lot because backgroundrb (under cygwin) starts successfully (or rather
> without any errors) but doesn't always really start. Don't have this
> problem on my home 'nix box.
> My application dynamically shows and hides links, actions, etc and my 1st
> revision polled MiddleMan directly everytime -- rather than caching it in an
> @instance variable. So for each request MiddleMan.ask_status could get hit
> 10-15 times depending on records, auth, etc.
> After refreshing the page a few times, I see 50+ connections just hanging
> around and that's just with me. I'm just wondering what this will be like
> when it hits production.
> I'll put in a ticket...
Don't worry about "what happens in production in issue?". I have
rarely let any known/reproducible bug open for more than a week. So,
we will this straightened.
More information about the Backgroundrb-devel