Fwd: Connection Pool crashing problems?

Forgot to cc list.


---------- Forwarded message ----------
From: Brian Bruns <brian.bruns@xxxxxxxxx>
Date: Sun, 12 Dec 2004 10:30:13 -0500
Subject: Re: [freetds] Connection Pool crashing problems?
To: craigs <s.craig@xxxxxxxxxxxxx>


I just applied a one liner (and your patch as well) to CVS.  Please
give it a try and let me know if it works.  As a bonus, this should
make it much easier to add TDS7/8 support to the pool.

Cheers,

Brian



On Fri, 10 Dec 2004 11:24:59 +0000, craigs <s.craig@xxxxxxxxxxxxx> wrote:
> thats one hell of a film! thanks for looking into it, next year we have
> predicted that we will average over 3000 clients hitting the pool every
> hour so it would be good if we could track it down sooner rather than later.
>
>
>
> Brian Bruns wrote:
>
> >The good: I was able to get it to crash on the same line.
> >The bad: Looks like a buffer overflow
> >The ugly: This means it originated elsewhere in the code and is
> >therefore hard to track down.
> >
> >Still plugging away at it, i'll let you know what i find.
> >
> >On Fri, 10 Dec 2004 10:30:24 +0000, craigs <s.craig@xxxxxxxxxxxxx> wrote:
> >
> >
> >> here is a detailed list of what we are running! we have a suse 9.2 linux
> >>server, using tds version 4.2 for connection pooling, snapshot
> >>freetds-0.64.dev.20041207, client programs written in C using db-lib.  the
> >>pool goes down at least a few times every hour, we are using 3 max
> >>connections and receiving approx 1200 clients an hour and each client does
> >>at least 2 querys and an insert with few doing 1 or 2 more.
> >>
> >> we have written a process watcher that watchs the connection pool and
> >>restarts it if it crashes, before we added a patch it would take the
> >>connection pool nearly a minute to come back up, it wouldnt release the
> >>socket, or the socket had to wait to time out, now the pool comes back up
> >>again within a few seconds.
> >>
> >> Brian Bruns wrote:
> >>
> >>
> >> Craig, Wanna send along the patch for that? I'll merge it. I've been
> >>planning on spending some time on this, and may get around to it this
> >>weekend. What is your server/version? I'll try to do some load testing and
> >>see if I can reproduce your error locally, and failing that scan the code
> >>for something. Brian On Thu, 09 Dec 2004 09:17:32 +0000, craigs
> >><s.craig@xxxxxxxxxxxxx> wrote:
> >>
> >>
> >> Frediano Ziglio wrote:
> >> Il mer, 2004-12-08 alle 13:52, craigs ha scritto:
> >> Brian Bruns wrote: Program received signal SIGSEGV, Segmentation fault.
> >>0x0804b5b0 in pool_process_users (pool=0x804d008, fds=0xbfffdbd0) at
> >>user.c:131 131 if (FD_ISSET(puser->tds->s, fds)) { is this any help? Shaun.
> >>Yes, probably puser->tds == NULL or puser->tds->s < 0. In other words
> >>connection closed freddy77 Any ideas why the connection is closing, would it
> >>be on my C clients side or maybe something to do with ms sql. when it does
> >>crash it takes nearly a minute to come up again which can cause problems for
> >>ourselfs, we have added a line in pool_main_loop which releases the socket
> >>as soon it crashes, our up time again has been greatly reduced because of
> >>this line, would this be of any use to anyone?
> >> _______________________________________________ FreeTDS mailing list
> >>FreeTDS@xxxxxxxxxxxxxxxxx http://lists.ibiblio.org/mailman/listinfo/freetds
> >>_______________________________________________ FreeTDS mailing list
> >>FreeTDS@xxxxxxxxxxxxxxxxx http://lists.ibiblio.org/mailman/listinfo/freetds
> >>_______________________________________________ FreeTDS mailing list
> >>FreeTDS@xxxxxxxxxxxxxxxxx http://lists.ibiblio.org/mailman/listinfo/freetds
> >>
> >>
> >>
>
>