Proxool: Proxy JDBC Connection Pool Icon

UNMAINTAINED!

As of 2016-06-20, this project may now be found at https://github.com/proxool/proxool.

User Ratings

★★★★★
★★★★
★★★
★★
3
0
1
0
0
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 3 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 3 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 3 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 1 / 5
Write a Review

User Reviews

  • 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5

    In 2015, if you do not have a connection pool solution you should NOT start here. This project is not maintained. There is no support for a thread to wait if a connection is not available. Under load proxool will exceed the max connections and create more. However, it will NOT clean these up and it will leak. If you set the connection max high enough you probably won't run into this problem. But it's design gaps are very noticeable. Even the last proxool 0.9 is not necessarily drop in plug and play from 0.8.3. We had issues in changes proxool code did around jndi into 0.9. Suggest you look elsewhere for a project that is maintained and has a better design. It was good for it's time, but is not production suitable for high load environments today.

    Posted 12/16/2015
  • 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5

    Thanks for Proxool, it's the best!

    Posted 06/25/2013
  • 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5

    really good

    Posted 12/30/2011
  • 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5

    Works great!

    Posted 08/11/2009

Thanks for helping keep SourceForge clean.

Screenshot instructions:
Windows
Mac
Red Hat Linux   Ubuntu

Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies
X

Briefly describe the problem (required):

Upload screenshot of ad (required):
Select a file, or drag & drop file here.

Please provide the ad click URL, if possible:

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks