Setting minimum and maximum number of database connections to the same number causes JVM abort

[CR #354701] In the global.properties.xml file, under limited system resources, setting both the minimum and maximum number of database connections in a pool to the same number results in a JVM abort.

Sun Hotspot JVM Bug ID: 4724356 is currently open with Sun describing similar behavior.

Workaround: Set the minimum number of database connections in a pool to a number less than the maximum number.