Personally I didn't like the ConnectionBroker by JavaExchange because of
unpredictable behavior under heavy conditions. Some requests for a
connection would receive it after a second, others after 20 seconds, and
others would simply time out after 30 seconds, without any rhyme or reason.
This really complicates getting good benchmarks. I believed it has to do
with how the broker deals with multiple threads. You can see this behavior
if you configure a limited number of connections and hit your site with a
stress tester. Then browse your site and look at the log file output that
results, and you'll get a feel of what I'm talking about.
Hope this helps,
Scott
-----Original Message-----
From: Shankar Lal [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 01, 2000 2:08 PM
To: [EMAIL PROTECTED]
Subject: Best Connection Pooling
Which is the best Connection Pooling implementation around - JavaExchanges
ConnectionBroker, Poolman, BitMechanic .
Has anyone used Oracles Connection pool implementation?
Has anyone faced any problems with any of these implementations.
Also can I use a third party connection pooling implementation (like
connection broker) with oracles driver and still use datasources?
Thanks
Shankar
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
