Yeah, I wasn't trying to make a vote for moving, simply taking notice
and making an informed decision. I haven't done any perf testing
recently to compare the two, so I'm not in a good position to recommend
one over the other.
---- Cris J H
Jason Shao wrote:
On Oct 8, 2007, at 12:38 PM, Cris J Holdorph wrote:
I'd have stronger opinions if I was using an environment other then
Tomcat. However, in the Tomcat environment I don't see that it
matters much either way. In higher end app-server environments, it's
probably appropriate to let that server control the pools.
Even so, you can configure spring to use JNDI datasources on a per
installation environment if you need to. So I see no harm in
converting if you feel strongly.
Another thing to look at for a few minutes though, might be the recent
flurry in the Sakai community trying to convert from Commons
Connection Pooling to C3PO, which they did in response to a bug they
hit in commons pooling.
There's still some work to be done on the Sakai side -- UMich thinks
disabling inactive session in DBCP will avoid the deadlocking bug, and
Rutgers is actually going back to dbcp since there were other
sideaffects related to different default values for autocommit and
transactionIsolationLevel (likely Sakai specific though)
Proxool seems to get some votes too -- though Juergen was complaining on
TSS that there aren't any really good, clear OS choices for pools.
Jason
--
Jason Shao
Application Developer
Rutgers University, Office of Instructional & Research Technology
v. 732-445-8726 | f. 732-445-5539 | [EMAIL PROTECTED] |
http://jay.shao.org
--
You are currently subscribed to [email protected] as: [EMAIL
PROTECTED]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
