We understand the implications of setting "max-connection-usage" too low. At this point we are a little desparate to stop production errors even if we suffer a performance hit.
As a side note, using the resource monitor in the Admin Console we are getting about 28000 "NumConnAcquired" per day.
Thanks for your help.
Here is the config from domain.xml
<jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-sec
onds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="oracle.jdbc.pool.OracleCon
nectionPoolDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="true" is-isolation-level-guaranteed="false" lazy-connec
tion-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="100" max-wait-time-in-millis="60000" nam
e="fsprodPool" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.ConnectionPoolDataSource" statement-timeout-in-seconds="-1" steady-pool-si
ze="8" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
<description>fsprodPool</description>
<property name="URL" value="jdbc:oracle:thin:@some.server"/>
<property name="user" value="name>
<property name="password" value="pass"/>
</jdbc-connection-pool>
[Message sent by forum member 'bryanut' (bryanut)]
http://forums.java.net/jive/thread.jspa?messageID=321046