On 31/01/2015 20:03, Phil Steitz wrote: > I am about ready (at last) to start rolling RCs for DBCP 2.1. I > just opened an issue [1] that I am on the fence about and would like > feedback on. I am not sure, actually, that it is an improvement to > force initial requests to queue waiting for the pool to be > pre-filled (what the patch now does). There is a small chance that > with the current code, a client can get a DS with null logWriter, > but it is immediately set thereafter. I am happy to close [1] as > INVALID if others agree that current behavior is better. > > Review and feedback on [2] would also be appreciated.
I skim read the patch. I wonder about the portability / usefulness of the default values for the disconnection codes but a) I don't have a better set to suggest right now and b) they are configurable anyway so no objections from me. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
