Could you potentially increase the timeout in Cherokee to something longer than 20 seconds, or does this not resolve the issue?
Alternatively is it possible to make your spawned process do initialisation in the background, so that the spawned process starts immediately but returns a "Please wait" message while it initialises in the background? On Wed, Feb 22, 2012 at 8:56 AM, David Beitey <[email protected]> wrote: > I thought I had seen something about this previously, but can't seem to > find it now. > > Essentially, on my Cherokee 1.2.101 instance (RHEL 6, x86_64), I have an > Information Source configured with a local interpreter, and this hooked up > to a directory behavior via a reverse proxy handler. Upon startup of > Cherokee, the local interpreter has not yet been spawned. A request comes > in for the given directory and Cherokee spawns the local interpreter - this > spawning takes about 20 seconds or so to load fully. During this time, if > another user comes in and attempts to load a URL against the same behavior, > the spawning process appears to be killed and the spawning starts over > again. > > Is this a known issue with Cherokee? > > As a solution, I know I could make the process run separately to Cherokee, > but it would be nice the keep configured in this way. > > Thanks. > > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee > >
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
