Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 0.8
-
Fix Version/s: 0.9-beta1
-
Component/s: Core: Configuration, Core: Containers
-
Labels:None
-
Similar Issues:None
Description
Components are not initialised until an event is received for it. This means that if their are going to be any problems initialising a component, the prolem will not show itself straight away. Need to add a new config param that specifies how components are initialised in Mule .i.e.
-Initialise no commponents - current behaviour
-Initialise one commponent - load up the first component in the pool, further copies in the pool will be loaded as needed.
-Initialise all commponents - populate the pool with the max number of components
You can specify a Pool-Initialisation-Policy on the Main Mule configuration. The default is to load one component and then lazy load the others as needed.