Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
sequel-talk
+ new post
About this group
Join this group
Message from discussion How to automatically reconnect after network issues or database server restart?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Rodrigo Rosenfeld Rosas  
View profile  
 More options Oct 26 2012, 3:44 pm
From: Rodrigo Rosenfeld Rosas <rr.ro...@gmail.com>
Date: Fri, 26 Oct 2012 17:44:51 -0200
Local: Fri, Oct 26 2012 3:44 pm
Subject: Re: How to automatically reconnect after network issues or database server restart?
Print | View thread | Show original | Report this message | Find messages by this author

Em 26-10-2012 17:42, Jeremy Evans escreveu:

> On Friday, October 26, 2012 12:16:02 PM UTC-7, Rodrigo Rosenfeld Rosas
> wrote:

>     Just to let you know, it seems a Monitor is reentrant if you want
>     to take this path:

>     http://japgolly.blogspot.com.br/2012/04/ruby-mutex-reentrancy.html
>     <http://japgolly.blogspot.com.br/2012/04/ruby-mutex-reentrancy.html>

> I'm aware of the difference, Mutex is being used on purpose for
> performance (Monitor is about 2.5x slower).

> One other limitation with the current code is that it does the
> connection validation while holding the pool mutex, which means that
> no other threads can checkout a connection while this connection is
> being validated.  That's very bad.  I've modified things so the
> checking is done while not holding the mutex (in addition to
> precaching the SQL).

> I'm just running the changes through a final set of tests, hopefully
> it will be pushed within 15 minutes.

Great, specially because I tried using a Monitor instead of Mutex and
now "rails server" segfaults on JRuby 1.7 :P

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google