Subject | Re: Classic Server leaves "ghosts" connections behind - Redux |
---|---|
Author | Eduardo A. Salgado |
Post date | 2005-09-29T18:47:30Z |
--- In firebird-support@yahoogroups.com, "Eduardo A. Salgado"
<eas@o...> wrote:
concurrent users at this time, and each gets three database
connections
(so let us say 120 connections), I am finding 1,900
fb_inet_server.exe
connections in the Windows Task Manager Processes Tab!
Now, this Saturday PM, I will go clean all of them up. But I do not
know where they came from or why they are still there. I have
checked
the main program (Delphi) and it closes every database and destroys
connections the right way.
On our way to at least 10 times the current concurrent users, I am
stummped.
Any other thoughts, please? Anyone? Bueller? Bueller?
-Eduardo
<eas@o...> wrote:
> > When your application is closed, it will free itsactive
> > database connection, which will either commit or rollback any
> > transaction and close the connection. CS will then do whatever itdoes
> > when it gets told to close the connection. (which I am sureinvolves
> > killing the process at some point in time).But I may be doing something REALLY wrong. With just some 35-40
>
> That is what I was hoping for.
concurrent users at this time, and each gets three database
connections
(so let us say 120 connections), I am finding 1,900
fb_inet_server.exe
connections in the Windows Task Manager Processes Tab!
Now, this Saturday PM, I will go clean all of them up. But I do not
know where they came from or why they are still there. I have
checked
the main program (Delphi) and it closes every database and destroys
connections the right way.
On our way to at least 10 times the current concurrent users, I am
stummped.
Any other thoughts, please? Anyone? Bueller? Bueller?
-Eduardo