On 6/6/07, Madhu Sasidhar, MD <[EMAIL PROTECTED]> wrote: > Sean > I had the same problem. Also, if you do not explicitly start and commit > transactions, the gap between my Oldest Active and Next Transaction was > growing (since the Server will commit/rolllback transactions only when the
Yes, make connections as short as possible. Using explicit transactions can help. > associated connection is closed). This is what I did: > 1. Set the server to detect "dropped connections" faster. The default is > something like 2 hours. This allows me the server to automatically close > connections when a client goes offline unexpectedly. > 2. I call the FbConnection.ClearAllPools Method at appropriate places in my > application. > 3. FB server has limitations on the maximum number of concurrent connections > it can handle - it may also depend on the OS you are using as well as other > applications that are running on server. I have application with about 200 conc. connectrions and no problem. About 2-5 from one app. -- Jiri {x2} Cincura http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider