WildFly Modular Service Container: Difference between revisions
Jump to navigation
Jump to search
Migrating from https://home.feodorov.com:9443/wiki/Wiki.jsp?page=JBoss7ModularServiceContainer
No edit summary |
|||
| Line 14: | Line 14: | ||
=Overview= | =Overview= | ||
The Modular Services Container implements new algorithms for checking module and service dependencies at deploy and run time, such that only the services that are needed are loaded and started, and when no longer needed unloaded. This makes unnecessary "slimming" a configuration to get a minimal memory footprint and start time. | The JBoss Modular Services Container (MSC) is essentially an advanced concurrent state machine. It dynamically analyzes the dependencies between all services and attempts to start as many as it can at the same time, while still adhering to the relationship requirements. MSC implements new algorithms for checking module and service dependencies at deploy and run time, such that only the services that are needed are loaded and started, and when no longer needed unloaded. This makes unnecessary "slimming" a configuration to get a minimal memory footprint and start time. | ||
=Version= | =Version= | ||
Revision as of 02:26, 10 March 2016
Internal
Relevance
EAP 6.4
Overview
The JBoss Modular Services Container (MSC) is essentially an advanced concurrent state machine. It dynamically analyzes the dependencies between all services and attempts to start as many as it can at the same time, while still adhering to the relationship requirements. MSC implements new algorithms for checking module and service dependencies at deploy and run time, such that only the services that are needed are loaded and started, and when no longer needed unloaded. This makes unnecessary "slimming" a configuration to get a minimal memory footprint and start time.
Version
18:18:23,208 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1