Peter J. Boettcher — Tue, 17 Oct 2000 19:15:36 +0000

davidg,

Unfortunately I don't have a lot of experience using Java Servlets so I can't really help you with that. From my experience using COM+ objects within ASP pages (which are similar to Servlets) is that if you mark them (object) as recyclable or poolable, MTS (Microsoft Transaction Server) can then pool those objects. Whether or not the JDBC supports that I'm not sure.

I'm sorry I can't help you more but my area of expertise is ASP,ASP+,VB,VC++,SQL 7/2000

Regards,
Peter J. Boettcher

pooling connections

davidg — Tue, 17 Oct 2000 17:14:23 +0000

Thanks for your reply, I'll resort to pooling connections then. However I don't think the standard JBDC method getConnection() methods copes with pooling. I think a connection pool manager needs to manage your connections otherwise every time a servlet is run, there is a reconnection to the database - which can be costly. I do know that JDBC2.0 supports connection pooling, but it only has interfaces available so you have to write the basic code. Do you know of any implementations of these interfaces, esp. jconnect/Sybase's version of JDBC?

Peter J. Boettcher — Tue, 17 Oct 2000 15:39:11 +0000

davidg,

It's best to let the system handle the connections. A big mistake a lot of ASP developers make is to store the connection object in an application or session variable, this might appear to be a logical thing to do since it saves you from having to code the connection in every page. The problem with this is, connections stored in those type of variables cannot be pooled, so with a busy site this would slow things down considerably. In any case pool threading offers considable performance gains, especially if you do many similar type of db calls.

Regards,
Peter J. Boettcher