0 Replies Latest reply on May 5, 2016 11:07 AM by Robert Pepersack

    Slimming WildFly 9

    Robert Pepersack Newbie

      I read in the WildFly documentation, I read that WildFly is built on a modular service container that enables services on-demand when your application requires them. Does this mean that there is no point to "slim" WildFly by removing extensions and their corresponding subsystems from standalone.xml?  In my development environment, I have removed clustering, JPA, and mail from my standalone.xml file with no consistent change to WildFly's services used and memory footprint.


      Is there another approach I can use to reduce the amount of memory WildFly uses?


      Thanks.