+1 for adding this to next release. We need to ensure that ApplicationHolder is thread safe. Currently we are not properly using locks when building the application model (in certain places).
Also we need to clearly separate the usages of ApplicationHolder and ApplicationManager. I can see that both of these classes are used interchangeably. ApplicationHolder should only be used within the autoscaler component. Also autoscaler must only use ApplicationHolder to lookup application data. ApplicationManager should only be used by the messaging component to build the application model via MB messages. That means only other components (excluding AS) are allowed to use ApplicationManager (perhaps except for rare cases). Same goes for TopologyManager and TopologyHolder (currently we only have two classes with the name TopologyManager - this should be refactored). Except in this case cloud controller is allowed to use TopologyHolder and rest of the components should be using TopologyManager. On Mon, Aug 24, 2015 at 5:11 PM, Reka Thirunavukkarasu <r...@wso2.com> wrote: > Hi All, > > Can we add $subject in the next release as it will improve the performance > of multiple applications execution at the same time? If we have > hierarchical locking atleast at the application level, then any application > can be executed independently. Also, it will improve the performance as > some calls are w.r.t registry in the ApplicationHolder. > > Thanks, > Reka > > -- > Reka Thirunavukkarasu > Senior Software Engineer, > WSO2, Inc.:http://wso2.com, > Mobile: +94776442007 > > > -- Akila Ravihansa Perera WSO2 Inc.; http://wso2.com/ Blog: http://ravihansa3000.blogspot.com
