The JVM pooling architecture allows you to have multiple JVM controllers, each of which may have child JVMs.

You would use multiple JVM controllers if:

• You want each application to have its own JVM controller so that it can be started and stopped independently of others.

• Different applications require different settings. For example, you may not want to mix classpaths or JVM settings between different controllers.

• You want to monitor resource usage of the JVM controllers from Fusion Middleware Control. If different JVM controllers are used by different applications and/or groups of users, you can determine how resources are being consumed by your Java Importer code.

• You have multiple development, test, or production environments on the same computer.

• You do not want different applications to share static data.