RMI API multi-process configuration
To prevent a fatal exception within the transformation logic that runs the map and causes the calling process to terminate, you can use the multi-process configuration option.
The maps are run in processes created from the RMI Server process.
This option offers the best protection, since a fatal exception in one map will not adversely affect other maps.
The downside of this approach is that adapter connections are not shared across map processes. This means that a connection that is started in one process for a particular map can be reused only by maps that run in that same process. This might be an issue if many different maps are run that connect to a wide array of resources, such as different databases.