The last couple of months we've seen sporadic connection issues from our 
Heroku app to MongoHQ. It's usually about 10-20 a day, and a typical error 
looks like this (from Exceptional):

VersionsController# (Timeout::Error) "execution expired"

/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:797:in
 
`read'
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:797:in
 
`receive_message_on_socket' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:667:in
 
`receive_header' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:657:in
 
`receive' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:435:in
 
`block in receive_message' <internal:prelude>:10:in `synchronize' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:433:in
 
`receive_message' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/cursor.rb:384:in
 
`block in send_initial_query'
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:543:in
 
`instrument' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/cursor.rb:383:in
 
`send_initial_query' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/cursor.rb:348:in
 
`refresh' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/cursor.rb:72:in
 
`next_document' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/db.rb:492:in
 
`command' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:636:in
 
`check_is_master' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:455:in
 
`connect' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:512:in
 
`checkout_reader' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:428:in
 
`receive_message' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/cursor.rb:384:in
 
`block in send_initial_query' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:543:in
 
`instrument' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/cursor.rb:383:in
 
`send_initial_query' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/cursor.rb:348:in
 
`refresh' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/cursor.rb:72:in
 
`next_document' 
/app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/collection.rb:229:in
 
`find_one'


I've been in contact with MongoHQ support regarding this, but they haven't 
found a solution yet. There's a thread over at their support forums where we 
try to find the cause for this. If you've experienced the same thing, please 
join in with your experiences and possible workarounds:
http://support.mongohq.com/discussions/problems/233-connection-failure-issues

-martin

-- 
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to heroku@googlegroups.com.
To unsubscribe from this group, send email to 
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

Reply via email to