the active_record connection seems to be broken if only use normal
fork
On Oct 14, 10:08 pm, Frederick Cheung <[EMAIL PROTECTED]>
wrote:
> On Oct 14, 2:07 pm, swachian <[EMAIL PROTECTED]> wrote:> I have such a
> problem as well. Spawn forks well in mongrel, but fails
> > in passenger.
> > However, it can be run spawn in thread mode if you have set the
> > config.active_record.allow_concurrency=true .
>
> Something "stupid" like system("...") might work (because that's both
> forking and execing)
>
> Fred
>
> > On Sep 16, 2:51 am, Robert Matei <[EMAIL PROTECTED]>
> > wrote:
>
> > > Robert Matei wrote:
> > > > Right now I'm debating between:
> > > > - trying to fix BackgrounDRb
> > > > - installing Backgroundjob, which is self-spawning and hopefully more
> > > > reliable
> > > > - using spawn, either with forking or threading
>
> > > Well, it appears none of my alternatives would even work...
> > > - Spawn with forking doesn't seem to work under Passenger
> > > - Spawn with threading doesn't either (apparently need another Apache or
> > > something?)
> > > - Backgroundjob doesn't seem to have any provisions for running
> > > concurrenttasks...
>
> > > Any ideas? :(
> > > --
> > > Posted viahttp://www.ruby-forum.com/.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
