Re: [c3p0-users] Is this forum still active ?

[John & D. S. <jds...@gm...>]

Stefan,

You said:

> Thanks for your clarifications. I would be pleased if you could add the
> answers to the relevant messages, so that I can comment on them.

I don't know what you mean.  Do you mean that you want me to reply to
each individual email that you sent to this list?  I get c3p0 emails
in digest form, and replying to each email individually would be very
inconvenient for me.

I tried to answer 5 of your questions.  Did you get the answers you needed?

John...

P.S. Here are the questions I understood, and their answers again, in
case that is convenient for you.

>> 1) how to integrate C3P0 with Active Directory for the retrieval of DB
>> user/pwd
>> That would probably require custom instantiation of a c3p0 data
>> source, reading settings from Active Directory and explicitly
>> configuring your pool using the methods on DataSources.
>>
>> 2) using JMX to get information about the pooled connections
>> There are lots of JMX beans exposed.  We didn't try to write code to
>> navigate them all, we just find the ones we wanted to watch, and then
>> wrote code that looked at the settings on that one, watching for
>> problems.
>>
>> 3) "acquire test -- pool is already maxed out" showing up in app logs
>> Your logging settings are set to have too much detail in your logs.
>>
>> 4) determine a correct value for the maxPoolSize property
>> This is an equation that has the following factors:
>> - how many web request threads are allowed by your servlet container
>> - how long do you expect to hold onto a JDBC connection when you check one
>> out
>> - how much of your web request time is spent doing something that does
>> NOT need a JDBC connection
>> Then you could guess at a reasonable value for the min and max
>> connection pool size.
>> Then you could measure whether this works.  We had to add
>> instrumentation around how long it took to get a connection and start
>> alerting if it took longer than a certain threshold.  Then we adjusted
>> our pool configuration based on whether we got alerts.  Most the
>> problems I've seen have been related to our Oracle database not
>> responding to login requests in a timely manner.
>>
>> 5) CVS repository of C3PO
>> There is no CVS repository, download the "c3p0-src" package from
>> sourceforge.net.
>>
>> Somebody else asked:
>> 6) how to get the sql exception thrown by the native sql driver
>> We had to patch c3p0 to do this (based on c3p0-0.9.1-pre11).  Steve
>> didn't like our patch, so he didn't apply it.  I'm including it here
>> for the benefit of anyone who cares.  This also includes doing "new
>> Hashtable()" which is required if you're using an old Oracle AQ driver
>> that has a dirty cast in it and doesn't deal with
>> Collections.EMPTY_MAP.