bill pope wrote: > Hi, > I work with Angela and we agree that the question should be refined a > little. We are using the J2eeDataSource implimentation of the > DataSourceComponent interface. Also Angela meant to say a single connection > pool with muliple connections rather than "mutilpe Connection pools". In > multi-user stress testing we seem to have hit a bottle neck and we wondered > if the fact that the J2eeDataSource component was a singleton might be the > problem. Could someone provide us with an explanation as to why it is a > singleton. Is it just a wrapper to get at the pooled db connections and so > the singleton appraoch is required to aid the mangement of the db connection > pool. Sorry if this seems trivial.
The J2EE implementation merely connects to the JNDI system and grabs a reference to the DataSource there. Whether your J2EE implementation supports pooling or not does not affect the J2eeDataSourceComponent. It is a rather simplistic approach. If there is any bottleneck, it is in the J2EE container. The JdbcDataSourceComponent is our responsibility, and we will be happy to address any bottlenecks or issues you see with that. -- "They that give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>