[DBCP-41] [dbcp][patch] docs lie: NOT maxIdle = 0 for no limit BUT -1

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.2
• Fix Version/s: 1.3

Environment

Operating System: other
Platform: Other

• Bugzilla Id: 35542
• Assignee: Unassigned
• Reporter: Anton Tagunov
• Created: 29/Jun/05 23:57
• Updated: 02/May/13 02:28
• Resolved: 08/Mar/08 22:59

Description

Documnentation for BasicDataSource and in a number of other places say: setMaxIdle( 0 ) for no limit. But GenericObjectPool says that negative (-1 for instance) should be used for this purpose.

In our neighbour project developers tried 0 and pool appeared to be non-functional: a new connection was created each time. They said: oh, well, drop dbcp, it does not work!

I consider this doc update so critical that I'm submitting a patch.

Issue Links

• is depended upon by: POOL-33 [pool][patch] Docs lie: not maxTotal negative for no limit but non-positive