Re: tomcat4.0 and poolman

[Gustavo Saramago]

I wonder why the JDBC specification delegates the responsability for implementing connection pools to the driver vendor. The result is the we got implementation classes like OracleConnectionPoolDataSource, that reduce the portability of the code.   Why can't we have a standard implementation of connection pools instead of depending on third party products ?   ----- Original Message ----- From: Hardeep Singh To: [EMAIL PROTECTED] Sent: Wednesday, September 19, 2001 7:13 AM Subject: Re: tomcat4.0 and poolman Hi,   I have used Poolman with Tomcat. Poolman itself does not recommend the use of the JDBC driver interface. It is better to use the DataSource way of accessing poolman. read the poolman help files for details. Using this way has also other advantages like portability to different appservers.   Hardeep ----- Original Message ----- From: sachin walia To: [EMAIL PROTECTED] Sent: Wednesday, September 19, 2001 12:29 PM Subject: tomcat4.0 and poolman hi i am trying to use poolman 2.0.4 with tomcat 4.0..   in my application i am using poolman's driver to wrap over mysql jdbc driver to make it XA compliant..   the problem is that it works well in standalone application but when i try to run a jsp page in which poolman's jdbc driver is invoked from container the tomcat gets shutdown due to the use of System.exit command extensively in com.codestudio.sql.PoolMan class..   does any one have any workaround for this problem because if i try to modif the code after removing thows commands a lot of exceptions r thrown..   please suggest..   urgent..   sachin walia