From: Warren Konkel <warren.konkel@gmail.com>
To: mongrel-unicorn@rubyforge.org
Subject: Confused classes
Date: Sat, 6 Feb 2010 09:33:13 -0300 [thread overview]
Message-ID: <de9b0f01002060433s3a8cdcf6j7476ef7e83d396ca@mail.gmail.com> (raw)
I switched from mod_passenger to unicorn on a fairly high traffic site
and ran into a strange problem that forced me to move back to
mod_passenger... it seems as if classes would sometimes get mixed up
with each other. If I had two Rails models:
class Foo < ActiveRecord::Base; end
class Bar < ActiveRecord::Base; end
Normally Foo.inspect and Bar.inspect would return:
Foo(field1: integer, field2: integer)
Bar(field3: integer, field4: integer)
When things were "broken" within a process, sometimes I would see:
Foo(field3: integer, field4: integer) <--- note field3/field4
actually belong to Bar, not Foo
And because of that, wacky errors would appear in my logs like:
Foo.find_by_field1(12345) --> not a method
Foo.create(:field1 => 12345) --> column not found
I also noticed the problem with field serializing in ActiveRecord... given:
class Boz < ActiveRecord::Base
serialize :some_data
end
When processes were working correctly, Boz.find(1).some_data would
return an actual object (like a Hash). When things were broken, the
raw serialized string from the database would be returned... almost as
if the Boz class "forgot" that it's supposed to deserialize
"some_data".
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?
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
next reply other threads:[~2010-02-06 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 12:33 Warren Konkel [this message]
2010-02-06 13:06 ` Confused classes Iñaki Baz Castillo
2010-02-07 2:01 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de9b0f01002060433s3a8cdcf6j7476ef7e83d396ca@mail.gmail.com \
--to=warren.konkel@gmail.com \
--cc=mongrel-unicorn@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).