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
finaglers
Home
+ new post
About this group
Join this group
Message from discussion finagle (and util and ostrich) on scala 2.9.1
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
 
tsuna  
View profile  
 More options Mar 29 2012, 8:22 pm
From: tsuna <tsuna...@gmail.com>
Date: Thu, 29 Mar 2012 17:22:09 -0700
Local: Thurs, Mar 29 2012 8:22 pm
Subject: Re: finagle (and util and ostrich) on scala 2.9.1
Print | View thread | Show original | Report this message | Find messages by this author

On Tue, Dec 6, 2011 at 10:43 AM, Steve Jenson <ste...@twitter.com> wrote:
> On Tue, Dec 6, 2011 at 10:35 AM, tsuna <tsuna...@gmail.com> wrote:
>> On Tue, Dec 6, 2011 at 10:27 AM, Steve Jenson <ste...@twitter.com> wrote:
>>> I believe I fixed this querulous issue a few weeks ago and we're using
>>> it in production without seeing connection leaks or Timer issues.

>> OK, I'd be curious to see the fix.  I spent several hours (!)
>> debugging this issue and navigating all the layers of Querulous, and
>> from I could tell it was properly calling "close()" on each DBCP
>> connection after each query.  Yet for some reason DBCP kept creating
>> new connections all the time.  I probably did something wrong/stupid
>> somewhere (as linked from the issue above, my code at the time is
>> available on https://gist.github.com/1344664).

> I updated the ticket with the specific fixes.

>> I liked being able to use Querulous, but I generally found it hard to
>> use, undocumented, and having too many layers (in addition of DBCP /
>> JDBC).  My little pooling / asynchronous layer is only 288 SLOC and
>> doesn't bring in DBCP or other dependencies than just the dreaded JDBC
>> stuff.

> Is it on github?

I just Gisted the code as some other people requested it:
https://gist.github.com/2245176

I don't know if this is something Finagle would be interested in
integrating to help people use clusters of MySQL servers in their
Finagle apps.  Ideally it would be better to have a MySQL client
written with Finagle, to be asynchronous from the ground up and avoid
dealing with all the JDBC bullshit.

--
Benoit "tsuna" Sigoure
Software Engineer @ www.StumbleUpon.com


 
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