Donate Share

Proxool: Proxy JDBC Connection Pool

Code

Programming Languages: Java

License: Apache Software License

Repositories

browse code, statistics, last commit on 2008-08-23 cvs -d:pserver:anonymous@proxool.cvs.sourceforge.net:/cvsroot/proxool login

cvs -z3 -d:pserver:anonymous@proxool.cvs.sourceforge.net:/cvsroot/proxool co -P modulename

Show:

What's happening?

  • Connection automatically removed

    Hi, I use proxool-0.9.1.jar and in my case I open a connection that needs to make a lot of insert statement. But after 5-6 minutes I receive this exception: 1-set-2009 16.15.55 org.logicalcobwebs.proxool.HouseKeeper sweep.

    2009-09-01 15:33:34 UTC by eziopontiggia

  • ProxoolDataSource.setHouseKeepingSleepTime(int)

    ProxoolDataSource.setHouseKeepingSleepTime(int): The parameter "int" should be "long".

    2009-07-26 00:48:54 UTC by nobody

  • 0.91 problem

    When I use 0.90RC3 or 0.83 jar, my code works fine. But if I upgrade to 0.91, my code will cause a severe problem. I found that 0.91's file size is much smaller than other. It's good thing. But it should still contain all necessary classes. Log: Servlet.service() for servlet action threw exception java.lang.ClassNotFoundException: org.logicalcobwebs.cglib.proxy.Callback at...

    2009-07-15 05:38:00 UTC by nobody

  • thread-safety issue in ConnectionPoolManager.getInstance()

    In v0.9.1 ConnectionPoolManager.getInstance() uses the double-checked locking idiom, which is not thread-safe. See http://www.cs.umd.edu/~pugh/java/memoryModel/DoubleCheckedLocking.html for a description of the problem. The section titled "Making it work for static singletons" describes a safe and inexpensive alternative.

    2009-04-28 21:45:06 UTC by nobody

  • Thread safety

    Thanks for a great tool. Looking at the source code, I get the impression there might still be a few small issues with thread safety. Please correct me if I'm wrong, since I'm not intimately familiar with the design or the implementation. I've looked at the code of version 0.9.1 and the code in CVS. - ConnectionPool.java, line 184: If another thread or even multiple threads have...

    2008-12-01 13:24:23 UTC by lafortune

  • testException can loop on NPE

    The following code seems to fail to advance the iterator causing the loop to not never exit when an exception with a null message is encountered. FatalSqlExceptionHelper:117 if (t.getMessage() != null && t.getMessage().indexOf((String) i.next()) > -1) { I have patched the code in the following way to treat all Errors, RuntimeExceptions and Exceptions with null messages as...

    2008-11-06 10:51:30 UTC by icarusxx

  • Proxool: Proxy JDBC Connection Pool

    billhorsman committed patchset 882 of module proxool to the Proxool: Proxy JDBC Connection Pool CVS repository, changing 3 files.

    2008-08-23 10:08:08 UTC by billhorsman

  • Proxool: Proxy JDBC Connection Pool

    billhorsman committed patchset 881 of module proxool to the Proxool: Proxy JDBC Connection Pool CVS repository, changing 3 files.

    2008-08-19 19:17:11 UTC by billhorsman

  • Deadlock while threads interrupted outside proxool

    This happens when threads were interrupted elsewhere while acquiring read lock of a org.logicalcobwebs.concurrent.WriterPreferenceReadWriteLock instance(or attempt method as well, not tested). This is caused by code of line 167 and 177: 167 if (Thread.interrupted()) throw new InterruptedException(); 177 cancelledWaitingReader(); The method acquire() will break out when a...

    2008-08-04 15:17:53 UTC by burningice2008

  • ProxyConnection.reallyClose should rollback before close

    Some JDBC implementations - like Oracle - perform an implicit commit before closing a connection, therefore Proxool should always - or at least configurable -rollback the connection before closing it. Otherwise an inconsistent state might be written to the database if the Pool is shutdown via ShutdownHook.

    2008-04-16 10:58:37 UTC by nobody

Our Numbers