This topic explains why the business process container is unavailable until all enterprise applications are started.
When the business process container is started or restarted, no messages in the internal queue are processed until all enterprise applications are started. It is not possible to change this behavior. The time that business process container is unavailable during a restart depends on how long it takes until all enterprise applications are started. This behavior is necessary to prevent the business process engine from navigating processes with associated enterprise applications that are not running.
Starting to process messages in the internal queue before all applications are started would result in ClassNotFound exceptions.
Last updated: Thu Apr 27 14:54:56 2006
(c) Copyright IBM Corporation 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)