Confused classes

Eric Wong normalperson at
Sat Feb 6 21:01:19 EST 2010

Iñaki Baz Castillo <ibc at> wrote:
> El Sábado, 6 de Febrero de 2010, Warren Konkel escribió:
> > Could it be that class attributes are somehow being co-mingled when
> > unicorn is starting up under high concurrency?  Perhaps a mutex is
> > missing somewhere?
> IMHO all your Unicorn workers are sharing the same DB connection (the same 
> ActiveRecord instances) so the problem arises.
> Take a look to the configuration here:
> You can see there how the ActiveRecord is disconnected at the beggining and 
> started for each worker later.

Yes, you have to reconnect any connected TCP sockets since they have no
defined atomicity semantics when they're shared across processes/threads.

Ruby Mutexes aren't useful at all here, they're only useful with threads
in the same process.  If you need to protect TCP client sockets from
multiple processes, you'll need SysV/POSIX semaphores or file locks
(flock/fcntl), but you're really better off using multiple TCP client
sockets in the first place.

Eric Wong

More information about the mongrel-unicorn mailing list