I dont know if anyone can provide an intelligent answer unless we know which DBCP (the pool acts as a factory to create n number of connections) you are using / how it is configured and which Driver classes you are using..I assume classes.zip ?
One more item is to never publish connect strings Maybe if Filip can suggest an alternative? Viel Gluck Martin ______________________________________________ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. > From: [EMAIL PROTECTED] > To: users@tomcat.apache.org > Subject: RE: failure notice > Date: Mon, 24 Nov 2008 18:01:13 +0200 > > Dear, > > I didn't create a connection pool of one connection. The configuration of the > datasource in the first case was as follows: > <Context path="/FamilyHandlerOpt"> > <Resource name="jdbc/VAS_FAF" auth="Container" > type="oracle.jdbc.pool.OracleDataSource" > driverClassName="oracle.jdbc.OracleDriver" > factory="oracle.jdbc.pool.OracleDataSourceFactory" > url="jdbc:oracle:thin:@172.21.201.60:1521:FMLYPRD1" username="family2" > password="family2" maxActive="100" maxIdle="10" maxWait="-1" /> > </Context> > > In the second case, I opened the connections using the same configuration of > the datasource above, kept the connections alive and pooled the threads on > these connections. > The response time of the second case was improved dramatically and the system > scalability was achieved. > > Best regards, > Ahmed Abbas > > -----Original Message----- > From: Christopher Schultz [mailto:[EMAIL PROTECTED] > Sent: Friday, November 14, 2008 6:40 PM > To: Tomcat Users List > Subject: Re: failure notice > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > To whom it may concern, > > aelgamal , wrote: > > The above scenario resulted in very poor scalability during the stress > > testing. When the average response time for 1 thread was x msec, the average > > response time for 2 threads was 2x and 3 threads was 3x and so on. > > How did you configure your data source? > > > When I created a pool of connections (15 connections) in the Servlet and > > kept the connections of this pool alive the scalability improved. The > > average response time for a 150 concurrent threads was slightly higher than > > the average response time for 1 thread. > > How did you configure your data source, here? > > > Please advice why the poor performance when I used tomcat data source. > > Tomcat can be configured to use a data source with a connection pool > size of 1. It's silly, but possible. If this is what you did, then you > simply weren't pooling connections and you should expect that pooling > would certainly improve performance. > > If you're interested in playing with connection pools, help out Filip by > using his new Tomcat connection pool he's testing. I'm sure he'd love > the feedback. > > - -chris > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkkdqfwACgkQ9CaO5/Lv0PBXdACgjq/4JJZKJ+DgNn64szioNSZl > mvgAoMN8Qb9oPjizMzzeXyGJQn6IPQmO > =7ATP > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > _________________________________________________________________ Access your email online and on the go with Windows Live Hotmail. http://windowslive.com/Explore/Hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_access_112008
