Chad, I suppose you meant JDBCDescriptorsStore. No it doesn't use connection pool so you'll have to add your own. But the biggest bottleneck comes from two places:
1. It extends AbstractSimpleService which supports only a single transaction context. 2. All database operations share a single and global jdbc connection. So above means if you have concurrent transactions, one thread will block and rollback after times out. This has been resolved by the new J2EEDescriptorsStore. -tom > -----Original Message----- > From: Chad Brandt [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 02, 2002 6:32 PM > To: [EMAIL PROTECTED] > Subject: JDBCDescriptorStore > > > Does anyone know if the JDBCDescriptorStore use any kind of connection > pooling? I am wondering how performance will be if not. > > Chad > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
