proxool-developer Mailing List for Proxool: Proxy JDBC Connection Pool

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Good morning,
how do I setup Proxool with Hibernate?
Is to make using the persistence.xml or not?
Thanks

Hi Michael,

I'm afraid I'm not in a position to help at the moment. I'd actually
recommend that someone takes the code from this project, puts it somewhere
like Github and applies the patch as necessary. In my opinion, Git offers
the best way forward for this project because it easily allows people like
you to fix it up as you need.

I'm always available to offer advice but I've drifted so far away from this
project, technically, that I'm no longer in a position to support it. Sorry.

-
Bill

On 29 September 2010 04:25, Bazanski, Michal (external) <
mic...@ex...> wrote:

>  Hi All,
>
> we've observed a finalizer problem in our application. After some
> inverstigation we've noticed that all cglib proxy classes have a finalize
> method. Therefore also all statements and connections used by proxool do
> have a finalize method leading to massive bottleneck. Hibernate since also
> using cglib ought to have the same problem. However they've solved it by
> using a finalize method filter (see this JIRA enty: *
> http://opensource.atlassian.com/projects/hibernate/browse/HHH-1103*<http://opensource.atlassian.com/projects/hibernate/browse/HHH-1103>
> ).
>
> Any info about finalizer issues in proxool would be helpful. Right now I do
> not see any solution other than patching the code.
>
> Cheers,
> Michael
>
>
>  Telekom Deutschland GmbH
> Aufsichtsrat: Timotheus Höttges (Vorsitzender)
> Geschäftsführung: Niek Jan van Damme (Sprecher), Thomas Berlemann, Thomas
> Dannenfeldt, Thomas Freude,
> Friedrich Fuß, Christoph Ganswindt, Dr. Christian P. Illek, Dr. Bruno
> Jacobfeuerborn, Dietmar Welslau
> Handelsregister: Amtsgericht Bonn, HRB 59 19
> Sitz der Gesellschaft: Bonn
> WEEE-Reg.-Nr.: DE60800328
>
>
>
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Proxool-developer mailing list
> Pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>
>

Hi All,

we've observed a finalizer problem in our application. After some
inverstigation we've noticed that all cglib proxy classes have a
finalize method. Therefore also all statements and connections used by
proxool do have a finalize method leading to massive bottleneck.
Hibernate since also using cglib ought to have the same problem. However
they've solved it by using a finalize method filter (see this JIRA enty:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1103).

Any info about finalizer issues in proxool would be helpful. Right now I
do not see any solution other than patching the code.

Cheers,
Michael

Telekom Deutschland GmbH 
Aufsichtsrat: Timotheus Hottges (Vorsitzender) 
Geschaftsfuhrung: Niek Jan van Damme (Sprecher), Thomas Berlemann, Thomas Dannenfeldt,
Thomas Freude, 
Friedrich Fu?, Christoph Ganswindt, Dr. Christian P. Illek, Dr. Bruno Jacobfeuerborn, Dietmar Welslau 
Handelsregister: Amtsgericht Bonn, HRB 59 19 
Sitz der Gesellschaft: Bonn 
WEEE-Reg.-Nr.: DE60800328

Hi all,

trying to build proxool on:

$ java -version
java version "1.6.0_12"
Java(TM) SE Runtime Environment (build 1.6.0_12-b04)
Java HotSpot(TM) 64-Bit Server VM (build 11.2-b01, mixed mode)

it wont compile with this error:

compile:
    [javac] Compiling 88 source files to 
/home/omry/dev/vizi/proxool-0.9.1/build/classes
    [javac] 
/home/omry/dev/vizi/proxool-0.9.1/build/src/java/org/logicalcobwebs/proxool/ProxoolDataSource.java:40: 
org.logicalcobwebs.proxool.ProxoolDataSource is not abstract and does 
not override abstract method isWrapperFor(java.lang.Class) in 
java.sql.Wrapper
    [javac] public class ProxoolDataSource implements DataSource, 
ObjectFactory {
    [javac]        ^
    [javac] Note: Some input files use or override a deprecated API.
    [javac] Note: Recompile with -Xlint:deprecation for details.
    [javac] 1 error

looks like a new abstract method in java.sql.Wrapper is not overridden 
by proxool.

If you want to patch it and try it out in your app I'm certainly open to
including it Proxool. Anybody else got anything to say on the subject?

2009/6/19 Matt Salafia <msa...@gm...>

> In this specific case, I believe making 'connectionCount' a volatile
> variable satisfies both goals: correctness and performance.  It even
> establishes the 'out-of-thin-air' guarantee you don't have when reading a
> non-synchronized, non-volatile 64-bit value.
>
> I think sacrificing correctness for performance is OK in places where stale
> (although correct) values won't hurt you.  I don't believe it works with the
> variable holding keys to the connection pool.
>
> My application is massively multithreaded.  There are a large number of
> concurrent threads acquiring and releasing connections. The fact that these
> threads will always see the 'connectionCount' increment done in
> Prototyper.buildConnection( ) but might not see any decrements done in
> Prototyper.connectionRemoved( ) seems serious to me.
>
>
>
> On Fri, Jun 19, 2009 at 3:59 PM, Bill Horsman <bi...@lo...>wrote:
>
>> I see your point. We've jumped through a few hoops in Proxool to get the
>> balance right between concurrency and excessive blocking. As you'd expect,
>> our first priority is to ensure the code doesn't break in concurrent
>> situations, but it's closely followed by our second priority: that it must
>> be very fast and not do unnecessary locking. I'm not saying you're right or
>> wrong - just that it would be hasty to grab a lock to read the
>> connectionCount unless we explore the implications.
>>
>> 2009/6/19 Matt Salafia <msa...@gm...>
>>
>>> Possibly, but I don't know - it's indeterminate.  Without the proper
>>> memory visibility semantics (e.g. synchronization, immutability, volatile
>>> et. al.) I think all bets are off.
>>>
>>>
>>>
>>> On Fri, Jun 19, 2009 at 1:32 PM, Bill Horsman <bi...@lo...>wrote:
>>>
>>>> Is that a problem that corrects itself? In other words, is it a
>>>> temporary problem where a connection is refused when it didn't have to be
>>>> but that the connection count does end up being correct? - Bill
>>>>
>>>> 2009/6/19 Matt Salafia <msa...@gm...>
>>>>
>>>>>  It seems Class Prototyper should either acquire the lock on private
>>>>> member 'lock' whenever it reads or modifies 'connectionCount' or make
>>>>> 'connectionCount' a volatile variable.
>>>>>
>>>>> Prototyper.buildConnection( ) acquires the lock to read and modify
>>>>> 'connectionCount' but other methods do not: Prototyper.sweep( ),
>>>>> Prototyper.connectionRemoved( ) and Prototyper.getConnectionCount().
>>>>>
>>>>> I started poking around after my application started seeing
>>>>> ProxoolExceptions indicating the maximum connection count had been reached
>>>>> and discovered what appears to be a memory visibility issue.  If calls to
>>>>> Prototyper.connectionRemoved( ) and Prototyper.buildConnection( ) happen in
>>>>> different threads there could be unwarranted ProxoolExceptions for reaching
>>>>> the maximum connection count - a 'connectionPool' decrement might not be
>>>>> visible to the threads calling Prototyper.buildConnection( ).
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Are you an open source citizen? Join us for the Open Source Bridge
>>>>> conference!
>>>>> Portland, OR, June 17-19. Two days of sessions, one day of
>>>>> unconference: $250.
>>>>> Need another reason to go? 24-hour hacker lounge. Register today!
>>>>>
>>>>> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
>>>>> _______________________________________________
>>>>> Proxool-developer mailing list
>>>>> Pro...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>>>>>
>>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Are you an open source citizen? Join us for the Open Source Bridge
>>>> conference!
>>>> Portland, OR, June 17-19. Two days of sessions, one day of unconference:
>>>> $250.
>>>> Need another reason to go? 24-hour hacker lounge. Register today!
>>>>
>>>> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
>>>> _______________________________________________
>>>> Proxool-developer mailing list
>>>> Pro...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>>>>
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Are you an open source citizen? Join us for the Open Source Bridge
>>> conference!
>>> Portland, OR, June 17-19. Two days of sessions, one day of unconference:
>>> $250.
>>> Need another reason to go? 24-hour hacker lounge. Register today!
>>>
>>> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
>>> _______________________________________________
>>> Proxool-developer mailing list
>>> Pro...@li...
>>> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Are you an open source citizen? Join us for the Open Source Bridge
>> conference!
>> Portland, OR, June 17-19. Two days of sessions, one day of unconference:
>> $250.
>> Need another reason to go? 24-hour hacker lounge. Register today!
>>
>> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
>> _______________________________________________
>> Proxool-developer mailing list
>> Pro...@li...
>> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>>
>>
>
>
> ------------------------------------------------------------------------------
> Are you an open source citizen? Join us for the Open Source Bridge
> conference!
> Portland, OR, June 17-19. Two days of sessions, one day of unconference:
> $250.
> Need another reason to go? 24-hour hacker lounge. Register today!
>
> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
> _______________________________________________
> Proxool-developer mailing list
> Pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>
>

In this specific case, I believe making 'connectionCount' a volatile
variable satisfies both goals: correctness and performance.  It even
establishes the 'out-of-thin-air' guarantee you don't have when reading a
non-synchronized, non-volatile 64-bit value.

I think sacrificing correctness for performance is OK in places where stale
(although correct) values won't hurt you.  I don't believe it works with the
variable holding keys to the connection pool.

My application is massively multithreaded.  There are a large number of
concurrent threads acquiring and releasing connections. The fact that these
threads will always see the 'connectionCount' increment done in
Prototyper.buildConnection( ) but might not see any decrements done in
Prototyper.connectionRemoved( ) seems serious to me.

On Fri, Jun 19, 2009 at 3:59 PM, Bill Horsman <bi...@lo...>wrote:

> I see your point. We've jumped through a few hoops in Proxool to get the
> balance right between concurrency and excessive blocking. As you'd expect,
> our first priority is to ensure the code doesn't break in concurrent
> situations, but it's closely followed by our second priority: that it must
> be very fast and not do unnecessary locking. I'm not saying you're right or
> wrong - just that it would be hasty to grab a lock to read the
> connectionCount unless we explore the implications.
>
> 2009/6/19 Matt Salafia <msa...@gm...>
>
>> Possibly, but I don't know - it's indeterminate.  Without the proper
>> memory visibility semantics (e.g. synchronization, immutability, volatile
>> et. al.) I think all bets are off.
>>
>>
>>
>> On Fri, Jun 19, 2009 at 1:32 PM, Bill Horsman <bi...@lo...>wrote:
>>
>>> Is that a problem that corrects itself? In other words, is it a temporary
>>> problem where a connection is refused when it didn't have to be but that the
>>> connection count does end up being correct? - Bill
>>>
>>> 2009/6/19 Matt Salafia <msa...@gm...>
>>>
>>>>  It seems Class Prototyper should either acquire the lock on private
>>>> member 'lock' whenever it reads or modifies 'connectionCount' or make
>>>> 'connectionCount' a volatile variable.
>>>>
>>>> Prototyper.buildConnection( ) acquires the lock to read and modify
>>>> 'connectionCount' but other methods do not: Prototyper.sweep( ),
>>>> Prototyper.connectionRemoved( ) and Prototyper.getConnectionCount().
>>>>
>>>> I started poking around after my application started seeing
>>>> ProxoolExceptions indicating the maximum connection count had been reached
>>>> and discovered what appears to be a memory visibility issue.  If calls to
>>>> Prototyper.connectionRemoved( ) and Prototyper.buildConnection( ) happen in
>>>> different threads there could be unwarranted ProxoolExceptions for reaching
>>>> the maximum connection count - a 'connectionPool' decrement might not be
>>>> visible to the threads calling Prototyper.buildConnection( ).
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Are you an open source citizen? Join us for the Open Source Bridge
>>>> conference!
>>>> Portland, OR, June 17-19. Two days of sessions, one day of unconference:
>>>> $250.
>>>> Need another reason to go? 24-hour hacker lounge. Register today!
>>>>
>>>> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
>>>> _______________________________________________
>>>> Proxool-developer mailing list
>>>> Pro...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>>>>
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Are you an open source citizen? Join us for the Open Source Bridge
>>> conference!
>>> Portland, OR, June 17-19. Two days of sessions, one day of unconference:
>>> $250.
>>> Need another reason to go? 24-hour hacker lounge. Register today!
>>>
>>> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
>>> _______________________________________________
>>> Proxool-developer mailing list
>>> Pro...@li...
>>> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Are you an open source citizen? Join us for the Open Source Bridge
>> conference!
>> Portland, OR, June 17-19. Two days of sessions, one day of unconference:
>> $250.
>> Need another reason to go? 24-hour hacker lounge. Register today!
>>
>> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
>> _______________________________________________
>> Proxool-developer mailing list
>> Pro...@li...
>> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>>
>>
>
>
> ------------------------------------------------------------------------------
> Are you an open source citizen? Join us for the Open Source Bridge
> conference!
> Portland, OR, June 17-19. Two days of sessions, one day of unconference:
> $250.
> Need another reason to go? 24-hour hacker lounge. Register today!
>
> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
> _______________________________________________
> Proxool-developer mailing list
> Pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>
>

I see your point. We've jumped through a few hoops in Proxool to get the
balance right between concurrency and excessive blocking. As you'd expect,
our first priority is to ensure the code doesn't break in concurrent
situations, but it's closely followed by our second priority: that it must
be very fast and not do unnecessary locking. I'm not saying you're right or
wrong - just that it would be hasty to grab a lock to read the
connectionCount unless we explore the implications.

2009/6/19 Matt Salafia <msa...@gm...>

> Possibly, but I don't know - it's indeterminate.  Without the proper memory
> visibility semantics (e.g. synchronization, immutability, volatile et. al.)
> I think all bets are off.
>
>
>
> On Fri, Jun 19, 2009 at 1:32 PM, Bill Horsman <bi...@lo...>wrote:
>
>> Is that a problem that corrects itself? In other words, is it a temporary
>> problem where a connection is refused when it didn't have to be but that the
>> connection count does end up being correct? - Bill
>>
>> 2009/6/19 Matt Salafia <msa...@gm...>
>>
>>>  It seems Class Prototyper should either acquire the lock on private
>>> member 'lock' whenever it reads or modifies 'connectionCount' or make
>>> 'connectionCount' a volatile variable.
>>>
>>> Prototyper.buildConnection( ) acquires the lock to read and modify
>>> 'connectionCount' but other methods do not: Prototyper.sweep( ),
>>> Prototyper.connectionRemoved( ) and Prototyper.getConnectionCount().
>>>
>>> I started poking around after my application started seeing
>>> ProxoolExceptions indicating the maximum connection count had been reached
>>> and discovered what appears to be a memory visibility issue.  If calls to
>>> Prototyper.connectionRemoved( ) and Prototyper.buildConnection( ) happen in
>>> different threads there could be unwarranted ProxoolExceptions for reaching
>>> the maximum connection count - a 'connectionPool' decrement might not be
>>> visible to the threads calling Prototyper.buildConnection( ).
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Are you an open source citizen? Join us for the Open Source Bridge
>>> conference!
>>> Portland, OR, June 17-19. Two days of sessions, one day of unconference:
>>> $250.
>>> Need another reason to go? 24-hour hacker lounge. Register today!
>>>
>>> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
>>> _______________________________________________
>>> Proxool-developer mailing list
>>> Pro...@li...
>>> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Are you an open source citizen? Join us for the Open Source Bridge
>> conference!
>> Portland, OR, June 17-19. Two days of sessions, one day of unconference:
>> $250.
>> Need another reason to go? 24-hour hacker lounge. Register today!
>>
>> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
>> _______________________________________________
>> Proxool-developer mailing list
>> Pro...@li...
>> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>>
>>
>
>
> ------------------------------------------------------------------------------
> Are you an open source citizen? Join us for the Open Source Bridge
> conference!
> Portland, OR, June 17-19. Two days of sessions, one day of unconference:
> $250.
> Need another reason to go? 24-hour hacker lounge. Register today!
>
> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
> _______________________________________________
> Proxool-developer mailing list
> Pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>
>

Possibly, but I don't know - it's indeterminate.  Without the proper memory
visibility semantics (e.g. synchronization, immutability, volatile et. al.)
I think all bets are off.

On Fri, Jun 19, 2009 at 1:32 PM, Bill Horsman <bi...@lo...>wrote:

> Is that a problem that corrects itself? In other words, is it a temporary
> problem where a connection is refused when it didn't have to be but that the
> connection count does end up being correct? - Bill
>
> 2009/6/19 Matt Salafia <msa...@gm...>
>
>> It seems Class Prototyper should either acquire the lock on private member
>> 'lock' whenever it reads or modifies 'connectionCount' or make
>> 'connectionCount' a volatile variable.
>>
>> Prototyper.buildConnection( ) acquires the lock to read and modify
>> 'connectionCount' but other methods do not: Prototyper.sweep( ),
>> Prototyper.connectionRemoved( ) and Prototyper.getConnectionCount().
>>
>> I started poking around after my application started seeing
>> ProxoolExceptions indicating the maximum connection count had been reached
>> and discovered what appears to be a memory visibility issue.  If calls to
>> Prototyper.connectionRemoved( ) and Prototyper.buildConnection( ) happen in
>> different threads there could be unwarranted ProxoolExceptions for reaching
>> the maximum connection count - a 'connectionPool' decrement might not be
>> visible to the threads calling Prototyper.buildConnection( ).
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Are you an open source citizen? Join us for the Open Source Bridge
>> conference!
>> Portland, OR, June 17-19. Two days of sessions, one day of unconference:
>> $250.
>> Need another reason to go? 24-hour hacker lounge. Register today!
>>
>> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
>> _______________________________________________
>> Proxool-developer mailing list
>> Pro...@li...
>> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>>
>>
>
>
> ------------------------------------------------------------------------------
> Are you an open source citizen? Join us for the Open Source Bridge
> conference!
> Portland, OR, June 17-19. Two days of sessions, one day of unconference:
> $250.
> Need another reason to go? 24-hour hacker lounge. Register today!
>
> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
> _______________________________________________
> Proxool-developer mailing list
> Pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>
>

Is that a problem that corrects itself? In other words, is it a temporary
problem where a connection is refused when it didn't have to be but that the
connection count does end up being correct? - Bill

2009/6/19 Matt Salafia <msa...@gm...>

> It seems Class Prototyper should either acquire the lock on private member
> 'lock' whenever it reads or modifies 'connectionCount' or make
> 'connectionCount' a volatile variable.
>
> Prototyper.buildConnection( ) acquires the lock to read and modify
> 'connectionCount' but other methods do not: Prototyper.sweep( ),
> Prototyper.connectionRemoved( ) and Prototyper.getConnectionCount().
>
> I started poking around after my application started seeing
> ProxoolExceptions indicating the maximum connection count had been reached
> and discovered what appears to be a memory visibility issue.  If calls to
> Prototyper.connectionRemoved( ) and Prototyper.buildConnection( ) happen in
> different threads there could be unwarranted ProxoolExceptions for reaching
> the maximum connection count - a 'connectionPool' decrement might not be
> visible to the threads calling Prototyper.buildConnection( ).
>
>
>
>
> ------------------------------------------------------------------------------
> Are you an open source citizen? Join us for the Open Source Bridge
> conference!
> Portland, OR, June 17-19. Two days of sessions, one day of unconference:
> $250.
> Need another reason to go? 24-hour hacker lounge. Register today!
>
> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
> _______________________________________________
> Proxool-developer mailing list
> Pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>
>

It seems Class Prototyper should either acquire the lock on private member
'lock' whenever it reads or modifies 'connectionCount' or make
'connectionCount' a volatile variable.

Prototyper.buildConnection( ) acquires the lock to read and modify
'connectionCount' but other methods do not: Prototyper.sweep( ),
Prototyper.connectionRemoved( ) and Prototyper.getConnectionCount().

I started poking around after my application started seeing
ProxoolExceptions indicating the maximum connection count had been reached
and discovered what appears to be a memory visibility issue.  If calls to
Prototyper.connectionRemoved( ) and Prototyper.buildConnection( ) happen in
different threads there could be unwarranted ProxoolExceptions for reaching
the maximum connection count - a 'connectionPool' decrement might not be
visible to the threads calling Prototyper.buildConnection( ).

Hello, Bill,

That's a pity. Because I have this huge old project here of thousands
of lines, where SQLExceptions were simply uncaught/unlogged. Now I am
getting all sorts of errors of various species, and it looks like the
only solution is to wrap the try except logger raise blocks around the
.executeUpdate statements all this done with the help of regular
expressions..

Thanks for answer!

-- 
sledge

On Mon, May 25, 2009 at 6:14 PM, Bill Horsman <bi...@lo...> wrote:
> Hi Sledge,
>
> I'm afraid not. I think that's the job of your code to correctly handle all
> SQL exceptions. It's not just about making sure the exception is logged -
> you also need to react to that exception, even if it's just a message to the
> user that "something went wrong".
>
> -
> Bill
>
> 2009/5/22 sledge <sim...@gm...>
>>
>> Hello all, wonderful job!
>>
>> I have set up logging with log4j, but all I am getting are the DEBUG
>> and WARN entries.
>>
>> Is there a way to have all of the SQLExceptions thrown by the DB
>> server logged somewhere. No matter if they get caught in the code or
>> not.
>>
>> Thank you,
>>
>> --
>> sledge
>>
>>
>> ------------------------------------------------------------------------------
>> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
>> is a gathering of tech-side developers & brand creativity professionals.
>> Meet
>> the minds behind Google Creative Lab, Visual Complexity, Processing, &
>> iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
>> Group, R/GA, & Big Spaceship. http://www.creativitycat.com
>> _______________________________________________
>> Proxool-developer mailing list
>> Pro...@li...
>> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>
>
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity professionals.
> Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, &
> iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
> Group, R/GA, & Big Spaceship. http://www.creativitycat.com
> _______________________________________________
> Proxool-developer mailing list
> Pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>
>

Hi Sledge,

I'm afraid not. I think that's the job of your code to correctly handle all
SQL exceptions. It's not just about making sure the exception is logged -
you also need to react to that exception, even if it's just a message to the
user that "something went wrong".

-
Bill

2009/5/22 sledge <sim...@gm...>

> Hello all, wonderful job!
>
> I have set up logging with log4j, but all I am getting are the DEBUG
> and WARN entries.
>
> Is there a way to have all of the SQLExceptions thrown by the DB
> server logged somewhere. No matter if they get caught in the code or
> not.
>
> Thank you,
>
> --
> sledge
>
>
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity professionals.
> Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, &
> iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
> Group, R/GA, & Big Spaceship. http://www.creativitycat.com
> _______________________________________________
> Proxool-developer mailing list
> Pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>

Hello all, wonderful job!

I have set up logging with log4j, but all I am getting are the DEBUG
and WARN entries.

Is there a way to have all of the SQLExceptions thrown by the DB
server logged somewhere. No matter if they get caught in the code or
not.

Thank you,

-- 
sledge

Hello all, wonderful job!

I have set up logging with log4j, but all I am getting are the DEBUG
and WARN entries.

Is there a way to have all of the SQLExceptions thrown by the DB
server logged somewhere. No matter if they get caught in the code or
not.

Thank you,

-- 
sledge

> The key thing about the documentation is incorporating it into the website.

Sourceforge support trac, which links into the svn repository and
provides a wiki. That might be one approach to solving the problem.

R.

Hi Abhishek,

You're quite right, our decision not to use the JDK Proxy is because we
wanted to support JDK 1.2. We haven't reviewed that decision for a few
years, but since it works well the Cglib I don't see much motivation to
change. You could make a case for deprecating JDK 1.2 but it might not be
worth it when there are other fish to fry.

-
Bill

Hi Abhishek,

The key thing about the documentation is incorporating it into the website.
Bundling it with the source can either be text files or as a local set of
static HTML files. As well as the API docs we have examples, configuration
guides, faqs, change logs.

-
Bill

Cool, the priority wise and the time wise, documentation will always suffer
and will always figure below than lets say adding the important feature
(numbre one on priorioty) or improving or correcting the design (second on
priority) in any open source project.

Though chris, for keeping the document under version control can be done. Of
course I am assuming here that all we have ascii/text file and no binaries.
Version control on binary I have heard as such is almost very difficult to
achieve so far.

For adding request queues, that should be an important stuff, though on the
look of it, I too tend to oppose it. User requests might have given you guys
better insight and prespective though. I Might think of and suggest other
features too vis-a-vis othe connectionPools too.

And in regard to design, java.lang.reflect.Proxy hasnt beeen used as I had a
glance on source code. FastArrayList looks bit outdated. Was compatibilityn
to java 1.2 the issue or some other reason behind the design?

----------------------------------------------------------------------------------------------------------------------------------
Hi again.

I don't want to appear as a dusty old conservative here, but I think its
important to point out that Proxool is a very mature product with wery
little development going on. My humble opinion is that we should have very
good reason for doing something as drastical as moving project host and
changing the version control system.

Here are few toughts regarding this:

Sourceforge provides support for Git (
http://apps.sourceforge.net/trac/sourceforge/wiki/Git) and Wiki (
http://apps.sourceforge.net/trac/sourceforge/wiki/Hosted%20Apps), so I fail
to see the motiviation for changing project host on these grounds.

As far as I can see there are several negative aspects of moving project
host:
* User familiarity: The project would be moved away from where it has always
been found.
* Fragmented statistics: Statistics such as download and visiting users
would be interrupted.
* Fragmentetd issue and forum history.
* Need to spend resources on setting up the project in a new environment.
* Loss of SouceForge services such as JDK availability.

A few questions about starting to use Git:
* Will a move to Git would spark a frenzy of new activity?
* Do developers find it particularly hard to develop patches and try them
out locally today?
* Is it particualary hard to incoroprate contributed patches in the Proxool
trunk today?
* What is the ratio of Git-familiarity amongst potential Proxool
contributors today?

Concerning usage of Wiki for documentation I would like to reiterate my
points from my last mail. Please let us discuss this closely before we do
anything, because I would consider it a grat loss to get the documentation
dis-attached from the Proxool versions:
* Wiki is fine for HOWTOs and other secondary documentation
* Formal documentation should be kept under version control to keep it under
adequate quality control and in sync with the version the user actually are
using. This is doubly true if you want Proxool to exists as several forks.
Then you will have two axis of versioning.

To summarise my standings on this in the old OS project voting lingo:
Move project host: -1
Change version control to Git: 0
Start using Wiki for Proxool homepage and secondary docs: +1
Disconnect the formal documentation from version control: -1

Are we sure this is were we want to spend the limited resources available to
Proxool develompent? Personally I think the most important develoment that
could be done is to add support for request queueing when the pool runs out
of connections. A feature I have always oposed, but user feedback has proved
me wrong. I think maye I could spare som time to work on that this spring.

Kind regards
Christian

2009/4/9 Bill Horsman <bi...@lo...>

> Hei Christian!
>
> Good to hear from you :)
>
> Actually, as soon as I sent that last message I realised that I should
have
> been clearer and not confused a Wiki with forking. Let me deal with each
of
> those in turn:
>
> GitHub is an obvious place to host a Git repository. It gives you a Wiki
> that makes it much easier to maintain the documentation. The Wiki is only
> editable by designated collaborators (equivalent to the small group of
> committers we have at SourceForge). It's not the only solution by far but
> it's much easier to change than the present documentation which is just
> static HTML. I'm approaching this from the aspect of that there needs to
be
> almost zero developer effort since I'm not aware of anyone having time to
> work on this. Copy and pasting from the current website into GitHub Wiki
> would be relatively easy.
>
> If anyone is prepared to put the effort in, getting the documentation
under
> source control would be wonderful. It isn't at the moment. I'm open to any
> suggestions.
>
> As to "collaboration through forking", Git makes it simple (even
desirable)
> for external collaborators (ones that we haven't chosen or selected in any
> way) to fork the project and make their own changes as they see fit. Git
> also makes it simple to pull those changes back into the master repository
> (in a controlled way). The whole thing is much more democratic with each
> commit making it back into the project on its own merits.
>
> -
> Bill
>

If you guys want, I can attempt to port it to Github.

On Fri, Apr 10, 2009 at 9:10 AM, Abhishek Manocha <
abh...@gm...> wrote:

> Cool Bill/Chris,
>
> That makes github and forking thing clearer. If I got it right, somebody
> can have forked repository of proxool too hosted on it without effecting
> main branch of proxool (even the documentation) if admin desire so and those
> changes can be included easily too if admin desire so, right?
>
> The big point is still wiki, but going through github I got the impression
> that it should be easy to set up and additional functionalities if we are
> getting should not do any harm. I second for github, rest your call.
>
> On Thu, Apr 9, 2009 at 7:18 PM, <
> pro...@li...> wrote:
>
>> Send Proxool-developer mailing list submissions to
>>        pro...@li...
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>        https://lists.sourceforge.net/lists/listinfo/proxool-developer
>> or, via email, send a message with subject or body 'help' to
>>        pro...@li...
>>
>> You can reach the person managing the list at
>>        pro...@li...
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Proxool-developer digest..."
>>
>>
>> Today's Topics:
>>
>>   1. Staring with the doc pages (Abhishek Manocha)
>>   2. Re: Staring with the doc pages (Bill Horsman)
>>   3. quick Clarification (Abhishek Manocha)
>>   4. Configuring simultaneous-build-throttle and       other
>>      (Abhishek Manocha)
>>   5. house keeping sleep time (Abhishek Manocha)
>>   6. Re: Staring with the doc pages (Christian Nedreg?rd)
>>   7. Re: Staring with the doc pages (Bill Horsman)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Thu, 9 Apr 2009 11:09:17 +0530
>> From: Abhishek Manocha <abh...@gm...>
>> Subject: [Proxool-developer] Staring with the doc pages
>> To: pro...@li...
>> Message-ID:
>>        <310...@ma...>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>>
>> hi All,
>>
>> Started using proxool and found some descrepencies in documentation to
>> satrt
>> with. Just for an example, AdminServlet fully qualifies location in the
>> Configuration doc page is not right. That's not on wiki I presume and whom
>> or how to get that corrected? Pointers?
>>
>> Abhishek Manocha
>> --
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Wed, 8 Apr 2009 22:47:19 -0700
>> From: Bill Horsman <bi...@lo...>
>> Subject: Re: [Proxool-developer] Staring with the doc pages
>> To: pro...@li...
>> Message-ID:
>>        <9b1...@ma...>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> Hello Abhishek,
>>
>> No it's not a Wiki but probably should be. I'm minded to move the whole
>> project to Github - it allows a lot more collaboration through forking and
>> the Wiki works well. Anyone have an opinion on that?
>>
>> -
>> Bill
>>
>> 2009/4/8 Abhishek Manocha <abh...@gm...>
>>
>>
>> > hi All,
>> >
>> > Started using proxool and found some descrepencies in documentation to
>> > satrt with. Just for an example, AdminServlet fully qualifies location
>> in
>> > the Configuration doc page is not right. That's not on wiki I presume
>> and
>> > whom or how to get that corrected? Pointers?
>> >
>> > Abhishek Manocha
>> > --
>> >
>> >
>> >
>> ------------------------------------------------------------------------------
>> > This SF.net email is sponsored by:
>> > High Quality Requirements in a Collaborative Environment.
>> > Download a free trial of Rational Requirements Composer Now!
>> > http://p.sf.net/sfu/www-ibm-com
>> > _______________________________________________
>> > Proxool-developer mailing list
>> > Pro...@li...
>> > https://lists.sourceforge.net/lists/listinfo/proxool-developer
>> >
>> >
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Thu, 9 Apr 2009 12:09:48 +0530
>> From: Abhishek Manocha <abh...@gm...>
>> Subject: [Proxool-developer] quick Clarification
>> To: pro...@li...,
>>        pro...@li...
>> Message-ID:
>>        <310...@ma...>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> hi,
>>
>> Will using
>> <init-param>
>>    <param-name>autoShutdown</param-name>
>>    <param-value>true</param-value>
>>  </init-param>
>>
>> in Servletconfigurator (or letting it default true)
>> remove all the proxool pools may be used by other web applications also in
>> same web server. Can't help, documentation was ambiguous at that point.
>>
>> And the second more important one, how can I make sure that
>> Servletconfigurator is the last one to get destroyed and so the pools
>> remain
>> active in my web app. My scenarios is that I have 4-5 servlets all getting
>> connection from the same pool, I want to make it absolute that
>> pool remains there through ServletConfigurator even if the service of
>> other
>> servlets is not called for a considerable amount of time
>>
>> --Abhishek Manocha
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Thu, 9 Apr 2009 12:41:32 +0530
>> From: Abhishek Manocha <abh...@gm...>
>> Subject: [Proxool-developer] Configuring simultaneous-build-throttle
>>        and     other
>> To: pro...@li...,    proxool-user
>>        <pro...@li...>
>> Message-ID:
>>        <310...@ma...>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> how can i configure
>>
>> simultaneous-build-throttle:
>>  maximum-connection-lifetime:
>>  maximum-active-time:
>>
>> in proxool through proxool.xml or the or web.xml?
>> i mean should it go in init-param of Servletconfigurator or the
>> proxool.xml
>> configuration?
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>>
>> ------------------------------
>>
>> Message: 5
>> Date: Thu, 9 Apr 2009 13:33:01 +0530
>> From: Abhishek Manocha <abh...@gm...>
>> Subject: [Proxool-developer] house keeping sleep time
>> To: pro...@li...,    proxool-user
>>        <pro...@li...>
>> Message-ID:
>>        <310...@ma...>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> in case of scenario of where 10 connections need to be maintained in the
>> pool,
>> what should be the simultaneous-build-throttle and
>> house-keeping-sleep-time
>> in other words what these parameters are for?
>> Does housekeeping threads make connection to db in that case shouldn't I
>> be
>> keeping that high instead of 30s default?
>>
>> Regarding AdminServlet provided for checking out the bottleneck of the
>> connection, I am getting weird connections created at 30 40 secs or so
>> in lots of 2, 3 or 4 connections created at same time, my code is not
>> creating any such connections so the AdminServlet has complicated the
>> matter
>> instead of solving.
>> Can you guys please help me in letting me know how to debug and check
>> which
>> connections are not getting released through AdminServlet
>>
>> Thanks
>> --Abhishek
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>>
>> ------------------------------
>>
>> Message: 6
>> Date: Thu, 9 Apr 2009 15:17:02 +0200
>> From: Christian Nedreg?rd <chr...@em...>
>> Subject: Re: [Proxool-developer] Staring with the doc pages
>> To: Pro...@li...
>> Message-ID:
>>        <fe7...@ma...>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> Hi.
>>
>> Long time no hear :)
>>
>> I haven't familiarized myself with Git yet. Could you elaborate a bit on
>> what you mean by "collaboration through forking" and why that is
>> desirable?
>>
>> In my opinion a Wiki is fine for HOWTOs and other secondary documentation,
>> but I think it's better to keep the formal documentation under version
>> control to keep it under adequate quality control and in sync with the
>> version the user actually are using.
>>
>> Christian
>>
>> On Thu, Apr 9, 2009 at 7:47 AM, Bill Horsman <bi...@lo...
>> >wrote:
>>
>> > Hello Abhishek,
>> >
>> > No it's not a Wiki but probably should be. I'm minded to move the whole
>> > project to Github - it allows a lot more collaboration through forking
>> and
>> > the Wiki works well. Anyone have an opinion on that?
>> >
>> > -
>> > Bill
>> >
>> > 2009/4/8 Abhishek Manocha <abh...@gm...>
>>
>> >
>> >> hi All,
>> >>
>> >> Started using proxool and found some descrepencies in documentation to
>> >> satrt with. Just for an example, AdminServlet fully qualifies location
>> in
>> >> the Configuration doc page is not right. That's not on wiki I presume
>> and
>> >> whom or how to get that corrected? Pointers?
>> >>
>> >> Abhishek Manocha
>> >> --
>> >>
>> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> This SF.net email is sponsored by:
>> >> High Quality Requirements in a Collaborative Environment.
>> >> Download a free trial of Rational Requirements Composer Now!
>> >> http://p.sf.net/sfu/www-ibm-com
>> >> _______________________________________________
>> >> Proxool-developer mailing list
>> >> Pro...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>> >>
>> >>
>> >
>> >
>> >
>> ------------------------------------------------------------------------------
>> > This SF.net email is sponsored by:
>> > High Quality Requirements in a Collaborative Environment.
>> > Download a free trial of Rational Requirements Composer Now!
>> > http://p.sf.net/sfu/www-ibm-com
>> > _______________________________________________
>> > Proxool-developer mailing list
>> > Pro...@li...
>> > https://lists.sourceforge.net/lists/listinfo/proxool-developer
>> >
>> >
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>>
>> ------------------------------
>>
>> Message: 7
>> Date: Thu, 9 Apr 2009 06:48:49 -0700
>> From: Bill Horsman <bi...@lo...>
>> Subject: Re: [Proxool-developer] Staring with the doc pages
>> To: Christian Nedreg?rd <chr...@em...>
>> Cc: Pro...@li...
>> Message-ID:
>>        <9b1...@ma...>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> Hei Christian!
>>
>> Good to hear from you :)
>>
>> Actually, as soon as I sent that last message I realised that I should
>> have
>> been clearer and not confused a Wiki with forking. Let me deal with each
>> of
>> those in turn:
>>
>> GitHub is an obvious place to host a Git repository. It gives you a Wiki
>> that makes it much easier to maintain the documentation. The Wiki is only
>> editable by designated collaborators (equivalent to the small group of
>> committers we have at SourceForge). It's not the only solution by far but
>> it's much easier to change than the present documentation which is just
>> static HTML. I'm approaching this from the aspect of that there needs to
>> be
>> almost zero developer effort since I'm not aware of anyone having time to
>> work on this. Copy and pasting from the current website into GitHub Wiki
>> would be relatively easy.
>>
>> If anyone is prepared to put the effort in, getting the documentation
>> under
>> source control would be wonderful. It isn't at the moment. I'm open to any
>> suggestions.
>>
>> As to "collaboration through forking", Git makes it simple (even
>> desirable)
>> for external collaborators (ones that we haven't chosen or selected in any
>> way) to fork the project and make their own changes as they see fit. Git
>> also makes it simple to pull those changes back into the master repository
>> (in a controlled way). The whole thing is much more democratic with each
>> commit making it back into the project on its own merits.
>>
>> -
>> Bill
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>>
>> ------------------------------
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> High Quality Requirements in a Collaborative Environment.
>> Download a free trial of Rational Requirements Composer Now!
>> http://p.sf.net/sfu/www-ibm-com
>>
>> ------------------------------
>>
>> _______________________________________________
>> Proxool-developer mailing list
>> Pro...@li...
>> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>>
>>
>> End of Proxool-developer Digest, Vol 11, Issue 1
>> ************************************************
>>
>
>

Hi Glen,

The repackaging means that the Cglib is code has been moved into a different
package, one under the proxool namespace. This means that if you use Cglib
outside the Proxool code then you need both proxool-cglib.jar AND
cglib-x.y.z.jar.

The purpose of repackaging is to reduce the dependency on a particular
version of Cglib. If you upgrade to Cgliv 2.whatever then Proxool won't be
effected.

-
Bill

2009/4/10 Glen Peterson <gl...@or...>

> Sorry to be dense, but I didn't understand what this meant in the
> release notes for the latest version of proxool:
>
> "Fixed bundling of Cglib in binary release. Cglib is "repackaged"
> using JarJar. This release just adds the file proxool-cglib.jar to the
> binary release."
>
> Do I need to replace my cglib-2.3.1.jar with proxool-cglib.jar?  Even
> if I don't need to, should I?  What did you change in cglib?
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> High Quality Requirements in a Collaborative Environment.
> Download a free trial of Rational Requirements Composer Now!
> http://p.sf.net/sfu/www-ibm-com
> _______________________________________________
> Proxool-developer mailing list
> Pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>

Sorry to be dense, but I didn't understand what this meant in the
release notes for the latest version of proxool:

"Fixed bundling of Cglib in binary release. Cglib is "repackaged"
using JarJar. This release just adds the file proxool-cglib.jar to the
binary release."

Do I need to replace my cglib-2.3.1.jar with proxool-cglib.jar?  Even
if I don't need to, should I?  What did you change in cglib?

Hi Chr,

All good points, friend.

One of the things I like about Git is the democracy. People can fork it and
explore their own ideas. The important thing is that it becomes very easy to
reincorporate those ideas back into the original. In SVN, a fork almost
always diverges.

BUT, Git is a change. It's a lot more different than the difference between
CVS and SVN. Understanding it is almost easier if you've never used CVS or
SVN. It is beautful and far superior, imho, but that doesn't necessarily
mean we should switch.

OK. So let's leave things as we are. I'd hate to cause any pain just because
I like Git. I don't think there's any reason why someone can't put it into
Git if they want anyway. I don't mind either way.

Aside from the queued connections, I think the biggest thing missing from
Proxool is the documentation. It's not under version control now and never
has been. All that happens is that a snapshot of it is captured as HTML and
bundled inside the distribution for a version.  At the moment, there's no
easy way for someone to contribute any documentation and it's a pain in the
arse for even me to change it. Any body got any ideas and any one got any
time to put the documentation somewhere sensible?

-
Bill

Hi again.

I don't want to appear as a dusty old conservative here, but I think its
important to point out that Proxool is a very mature product with wery
little development going on. My humble opinion is that we should have very
good reason for doing something as drastical as moving project host and
changing the version control system.

Here are few toughts regarding this:

Sourceforge provides support for Git (
http://apps.sourceforge.net/trac/sourceforge/wiki/Git) and Wiki (
http://apps.sourceforge.net/trac/sourceforge/wiki/Hosted%20Apps), so I fail
to see the motiviation for changing project host on these grounds.

As far as I can see there are several negative aspects of moving project
host:
* User familiarity: The project would be moved away from where it has always
been found.
* Fragmented statistics: Statistics such as download and visiting users
would be interrupted.
* Fragmentetd issue and forum history.
* Need to spend resources on setting up the project in a new environment.
* Loss of SouceForge services such as JDK availability.

A few questions about starting to use Git:
* Will a move to Git would spark a frenzy of new activity?
* Do developers find it particularly hard to develop patches and try them
out locally today?
* Is it particualary hard to incoroprate contributed patches in the Proxool
trunk today?
* What is the ratio of Git-familiarity amongst potential Proxool
contributors today?

Concerning usage of Wiki for documentation I would like to reiterate my
points from my last mail. Please let us discuss this closely before we do
anything, because I would consider it a grat loss to get the documentation
dis-attached from the Proxool versions:
* Wiki is fine for HOWTOs and other secondary documentation
* Formal documentation should be kept under version control to keep it under
adequate quality control and in sync with the version the user actually are
using. This is doubly true if you want Proxool to exists as several forks.
Then you will have two axis of versioning.

To summarise my standings on this in the old OS project voting lingo:
Move project host: -1
Change version control to Git: 0
Start using Wiki for Proxool homepage and secondary docs: +1
Disconnect the formal documentation from version control: -1

Are we sure this is were we want to spend the limited resources available to
Proxool develompent? Personally I think the most important develoment that
could be done is to add support for request queueing when the pool runs out
of connections. A feature I have always oposed, but user feedback has proved
me wrong. I think maye I could spare som time to work on that this spring.

Kind regards
Christian

2009/4/9 Bill Horsman <bi...@lo...>

> Hei Christian!
>
> Good to hear from you :)
>
> Actually, as soon as I sent that last message I realised that I should have
> been clearer and not confused a Wiki with forking. Let me deal with each of
> those in turn:
>
> GitHub is an obvious place to host a Git repository. It gives you a Wiki
> that makes it much easier to maintain the documentation. The Wiki is only
> editable by designated collaborators (equivalent to the small group of
> committers we have at SourceForge). It's not the only solution by far but
> it's much easier to change than the present documentation which is just
> static HTML. I'm approaching this from the aspect of that there needs to be
> almost zero developer effort since I'm not aware of anyone having time to
> work on this. Copy and pasting from the current website into GitHub Wiki
> would be relatively easy.
>
> If anyone is prepared to put the effort in, getting the documentation under
> source control would be wonderful. It isn't at the moment. I'm open to any
> suggestions.
>
> As to "collaboration through forking", Git makes it simple (even desirable)
> for external collaborators (ones that we haven't chosen or selected in any
> way) to fork the project and make their own changes as they see fit. Git
> also makes it simple to pull those changes back into the master repository
> (in a controlled way). The whole thing is much more democratic with each
> commit making it back into the project on its own merits.
>
> -
> Bill
>

Cool Bill/Chris,

That makes github and forking thing clearer. If I got it right, somebody can
have forked repository of proxool too hosted on it without effecting main
branch of proxool (even the documentation) if admin desire so and those
changes can be included easily too if admin desire so, right?

The big point is still wiki, but going through github I got the impression
that it should be easy to set up and additional functionalities if we are
getting should not do any harm. I second for github, rest your call.

On Thu, Apr 9, 2009 at 7:18 PM, <
pro...@li...> wrote:

> Send Proxool-developer mailing list submissions to
>        pro...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://lists.sourceforge.net/lists/listinfo/proxool-developer
> or, via email, send a message with subject or body 'help' to
>        pro...@li...
>
> You can reach the person managing the list at
>        pro...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Proxool-developer digest..."
>
>
> Today's Topics:
>
>   1. Staring with the doc pages (Abhishek Manocha)
>   2. Re: Staring with the doc pages (Bill Horsman)
>   3. quick Clarification (Abhishek Manocha)
>   4. Configuring simultaneous-build-throttle and       other
>      (Abhishek Manocha)
>   5. house keeping sleep time (Abhishek Manocha)
>   6. Re: Staring with the doc pages (Christian Nedreg?rd)
>   7. Re: Staring with the doc pages (Bill Horsman)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 9 Apr 2009 11:09:17 +0530
> From: Abhishek Manocha <abh...@gm...>
> Subject: [Proxool-developer] Staring with the doc pages
> To: pro...@li...
> Message-ID:
>        <310...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> hi All,
>
> Started using proxool and found some descrepencies in documentation to
> satrt
> with. Just for an example, AdminServlet fully qualifies location in the
> Configuration doc page is not right. That's not on wiki I presume and whom
> or how to get that corrected? Pointers?
>
> Abhishek Manocha
> --
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 2
> Date: Wed, 8 Apr 2009 22:47:19 -0700
> From: Bill Horsman <bi...@lo...>
> Subject: Re: [Proxool-developer] Staring with the doc pages
> To: pro...@li...
> Message-ID:
>        <9b1...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello Abhishek,
>
> No it's not a Wiki but probably should be. I'm minded to move the whole
> project to Github - it allows a lot more collaboration through forking and
> the Wiki works well. Anyone have an opinion on that?
>
> -
> Bill
>
> 2009/4/8 Abhishek Manocha <abh...@gm...>
>
> > hi All,
> >
> > Started using proxool and found some descrepencies in documentation to
> > satrt with. Just for an example, AdminServlet fully qualifies location in
> > the Configuration doc page is not right. That's not on wiki I presume and
> > whom or how to get that corrected? Pointers?
> >
> > Abhishek Manocha
> > --
> >
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by:
> > High Quality Requirements in a Collaborative Environment.
> > Download a free trial of Rational Requirements Composer Now!
> > http://p.sf.net/sfu/www-ibm-com
> > _______________________________________________
> > Proxool-developer mailing list
> > Pro...@li...
> > https://lists.sourceforge.net/lists/listinfo/proxool-developer
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 3
> Date: Thu, 9 Apr 2009 12:09:48 +0530
> From: Abhishek Manocha <abh...@gm...>
> Subject: [Proxool-developer] quick Clarification
> To: pro...@li...,
>        pro...@li...
> Message-ID:
>        <310...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> hi,
>
> Will using
> <init-param>
>    <param-name>autoShutdown</param-name>
>    <param-value>true</param-value>
>  </init-param>
>
> in Servletconfigurator (or letting it default true)
> remove all the proxool pools may be used by other web applications also in
> same web server. Can't help, documentation was ambiguous at that point.
>
> And the second more important one, how can I make sure that
> Servletconfigurator is the last one to get destroyed and so the pools
> remain
> active in my web app. My scenarios is that I have 4-5 servlets all getting
> connection from the same pool, I want to make it absolute that
> pool remains there through ServletConfigurator even if the service of other
> servlets is not called for a considerable amount of time
>
> --Abhishek Manocha
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 4
> Date: Thu, 9 Apr 2009 12:41:32 +0530
> From: Abhishek Manocha <abh...@gm...>
> Subject: [Proxool-developer] Configuring simultaneous-build-throttle
>        and     other
> To: pro...@li...,    proxool-user
>        <pro...@li...>
> Message-ID:
>        <310...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> how can i configure
>
> simultaneous-build-throttle:
>  maximum-connection-lifetime:
>  maximum-active-time:
>
> in proxool through proxool.xml or the or web.xml?
> i mean should it go in init-param of Servletconfigurator or the proxool.xml
> configuration?
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 5
> Date: Thu, 9 Apr 2009 13:33:01 +0530
> From: Abhishek Manocha <abh...@gm...>
> Subject: [Proxool-developer] house keeping sleep time
> To: pro...@li...,    proxool-user
>        <pro...@li...>
> Message-ID:
>        <310...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> in case of scenario of where 10 connections need to be maintained in the
> pool,
> what should be the simultaneous-build-throttle and house-keeping-sleep-time
> in other words what these parameters are for?
> Does housekeeping threads make connection to db in that case shouldn't I be
> keeping that high instead of 30s default?
>
> Regarding AdminServlet provided for checking out the bottleneck of the
> connection, I am getting weird connections created at 30 40 secs or so
> in lots of 2, 3 or 4 connections created at same time, my code is not
> creating any such connections so the AdminServlet has complicated the
> matter
> instead of solving.
> Can you guys please help me in letting me know how to debug and check which
> connections are not getting released through AdminServlet
>
> Thanks
> --Abhishek
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 6
> Date: Thu, 9 Apr 2009 15:17:02 +0200
> From: Christian Nedreg?rd <chr...@em...>
> Subject: Re: [Proxool-developer] Staring with the doc pages
> To: Pro...@li...
> Message-ID:
>        <fe7...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi.
>
> Long time no hear :)
>
> I haven't familiarized myself with Git yet. Could you elaborate a bit on
> what you mean by "collaboration through forking" and why that is desirable?
>
> In my opinion a Wiki is fine for HOWTOs and other secondary documentation,
> but I think it's better to keep the formal documentation under version
> control to keep it under adequate quality control and in sync with the
> version the user actually are using.
>
> Christian
>
> On Thu, Apr 9, 2009 at 7:47 AM, Bill Horsman <bi...@lo...
> >wrote:
>
> > Hello Abhishek,
> >
> > No it's not a Wiki but probably should be. I'm minded to move the whole
> > project to Github - it allows a lot more collaboration through forking
> and
> > the Wiki works well. Anyone have an opinion on that?
> >
> > -
> > Bill
> >
> > 2009/4/8 Abhishek Manocha <abh...@gm...>
> >
> >> hi All,
> >>
> >> Started using proxool and found some descrepencies in documentation to
> >> satrt with. Just for an example, AdminServlet fully qualifies location
> in
> >> the Configuration doc page is not right. That's not on wiki I presume
> and
> >> whom or how to get that corrected? Pointers?
> >>
> >> Abhishek Manocha
> >> --
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> This SF.net email is sponsored by:
> >> High Quality Requirements in a Collaborative Environment.
> >> Download a free trial of Rational Requirements Composer Now!
> >> http://p.sf.net/sfu/www-ibm-com
> >> _______________________________________________
> >> Proxool-developer mailing list
> >> Pro...@li...
> >> https://lists.sourceforge.net/lists/listinfo/proxool-developer
> >>
> >>
> >
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by:
> > High Quality Requirements in a Collaborative Environment.
> > Download a free trial of Rational Requirements Composer Now!
> > http://p.sf.net/sfu/www-ibm-com
> > _______________________________________________
> > Proxool-developer mailing list
> > Pro...@li...
> > https://lists.sourceforge.net/lists/listinfo/proxool-developer
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 7
> Date: Thu, 9 Apr 2009 06:48:49 -0700
> From: Bill Horsman <bi...@lo...>
> Subject: Re: [Proxool-developer] Staring with the doc pages
> To: Christian Nedreg?rd <chr...@em...>
> Cc: Pro...@li...
> Message-ID:
>        <9b1...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hei Christian!
>
> Good to hear from you :)
>
> Actually, as soon as I sent that last message I realised that I should have
> been clearer and not confused a Wiki with forking. Let me deal with each of
> those in turn:
>
> GitHub is an obvious place to host a Git repository. It gives you a Wiki
> that makes it much easier to maintain the documentation. The Wiki is only
> editable by designated collaborators (equivalent to the small group of
> committers we have at SourceForge). It's not the only solution by far but
> it's much easier to change than the present documentation which is just
> static HTML. I'm approaching this from the aspect of that there needs to be
> almost zero developer effort since I'm not aware of anyone having time to
> work on this. Copy and pasting from the current website into GitHub Wiki
> would be relatively easy.
>
> If anyone is prepared to put the effort in, getting the documentation under
> source control would be wonderful. It isn't at the moment. I'm open to any
> suggestions.
>
> As to "collaboration through forking", Git makes it simple (even desirable)
> for external collaborators (ones that we haven't chosen or selected in any
> way) to fork the project and make their own changes as they see fit. Git
> also makes it simple to pull those changes back into the master repository
> (in a controlled way). The whole thing is much more democratic with each
> commit making it back into the project on its own merits.
>
> -
> Bill
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> High Quality Requirements in a Collaborative Environment.
> Download a free trial of Rational Requirements Composer Now!
> http://p.sf.net/sfu/www-ibm-com
>
> ------------------------------
>
> _______________________________________________
> Proxool-developer mailing list
> Pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>
>
> End of Proxool-developer Digest, Vol 11, Issue 1
> ************************************************
>

2002	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (3)	Dec (54)
2003	Jan (15)	Feb (56)	Mar (9)	Apr (6)	May (12)	Jun (4)	Jul	Aug (9)	Sep (21)	Oct (10)	Nov (19)	Dec (29)
2004	Jan (11)	Feb (12)	Mar (53)	Apr (7)	May (15)	Jun (6)	Jul (6)	Aug	Sep (11)	Oct (7)	Nov (3)	Dec (3)
2005	Jan (1)	Feb (2)	Mar	Apr	May	Jun (1)	Jul (4)	Aug (2)	Sep (10)	Oct (4)	Nov	Dec (1)
2006	Jan	Feb	Mar (1)	Apr (2)	May (1)	Jun (5)	Jul	Aug	Sep	Oct	Nov (2)	Dec
2007	Jan (4)	Feb (1)	Mar	Apr (2)	May (4)	Jun (2)	Jul (2)	Aug (2)	Sep	Oct	Nov (1)	Dec (7)
2008	Jan	Feb	Mar (2)	Apr	May (2)	Jun	Jul (5)	Aug (3)	Sep (5)	Oct	Nov (2)	Dec (2)
2009	Jan	Feb	Mar (1)	Apr (18)	May (4)	Jun (6)	Jul	Aug (1)	Sep	Oct	Nov	Dec
2010	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep (2)	Oct	Nov	Dec
2011	Jan	Feb	Mar	Apr (1)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

proxool-developer Mailing List for Proxool: Proxy JDBC Connection Pool

UNMAINTAINED!

proxool-developer — Developer's discussion list