How do I turn off connection pooling?

[pimento]

I want to turn pooling OFF for db connections. I thought I should do so in
jrun-resources, however, JRun metrics logging shows a steady positive number
for {jdbc.activeConnections} and {jdbc.poolSize}. Is there some other config
setting I need to modify to turn off jdbc connection pooling? Do I need to
remove all of the pooling-related items from the config (e.g.
skimmer-frequency)?

Thanks,

-Rick

---

Following is my jrun-resources config:

<data-source>
<dbname>provisioning</dbname>
<driver>macromedia.jdbc.MacromediaDriver</driver>
<url>jdbc:macromedia:sqlserver://xxx</url>
<username>xxx</username>
<password>xxx</password>
<encrypted>true</encrypted>
<encryption-class>jrun.security.JRunCrypterForTwofish</encryption-class>
<native-results>true</native-results>
<remove-on-exceptions>true</remove-on-exceptions>
<pool-statements>false</pool-statements>
<initial-connections>1</initial-connections>
<connection-timeout>1200</connection-timeout>
<transaction-timeout>20</transaction-timeout>
<cache-enabled>false</cache-enabled>
<cache-size>5</cache-size>
<cache-refresh-interval>30</cache-refresh-interval>
<jndi-name>mainDB</jndi-name>
<poolname>Pool</poolname>
<minimum-size>0</minimum-size>
<maximum-size>2147483647</maximum-size>
<user-timeout>20</user-timeout>
<validation-query>select * from jrunValidation</validation-query>
<skimmer-frequency>30</skimmer-frequency>
<shrink-by>5</shrink-by>
<maximum-soft>true</maximum-soft>
<debugging>true</debugging>
<disable-pooling>true</disable-pooling>
<description />
<isolation-level>READ_COMMITTED</isolation-level>
</data-source>

[pimento]

I should have mentioned, I'm running jrun4, updater5 on a linux machine.

I've been watching my metrics logs all day and see the activeConnections and
poolsize growing. Once again, pooling *should* be turned off so I don't know
why it reports a poolsize. Is it possible that somewhere a connection isn't
being closed properly and thus more connections are being created?

This is a relatively new problem that seems to have been introduced shortly
after upgrading to updater5...

-Rick