Issue Details (XML | Word | Printable)

Key: MULE-2
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Ross Mason
Reporter: Ross Mason
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Mule

Components are always lazy loaded

Created: 22/Mar/04 10:44 PM   Updated: 21/Aug/06 09:22 PM
Component/s: Core: Configuration, Core: Containers
Affects Version/s: 0.8
Fix Version/s: 0.9-beta1

Time Tracking:
Not Specified

Labels:
Similar Issues: MULE-1956 Revise Lazy Init for Security Filters


 Description  « Hide
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



 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order
Ross Mason added a comment - 04/May/04 08:10 PM
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.