WildFly Modular Service Container

TODO

TODO parse this https://developer.jboss.org/wiki/AS7InternalArchitectureOverview

External

• AS7 Internal Architecture Overview https://developer.jboss.org/wiki/AS7InternalArchitectureOverview
• Extending JBoss AS 7 https://docs.jboss.org/author/display/AS72/Extending+JBoss+AS+7

Internal

• WildFly
• WildFly Class Loading

Relevance

EAP 6.4

Overview

The JBoss Modular Services Container (MSC) is a 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 dependency 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.

Modular class loading is at the core of MSC.

Application server functionality, such as messaging or handling HTTP requests, is implemented in extensions to the MSC core.

Version

18:18:23,208 INFO  [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1

Source

GitHub: https://github.com/jboss-msc

Maven Repository: https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/msc/jboss-msc/

Maven

<dependency>
    <groupId>org.jboss.msc</groupId>
    <artifactId>jboss-msc</artifactId>
    <version>1.1.6.Final-redhat-1</version>
</dependency>

The following is needed for CurrentServiceContainer:

<dependency>
    <groupId>org.jboss.as</groupId>
    <artifactId>jboss-as-server</artifactId>
    <version>7.5.9.Final-redhat-2</version>
</dependency>

Implementation Details

Modular Service Container Implementation Details