Issue

• to upgrade the EAP version to the next minor release it is not possible to use the CLI patch command, Therefor we created our own upgrade procedure with a combination of remote shell commands and CLI scripts. The overall automated upgrade process works by:

  • Shut down the existing server
  • Rename the directory where the current jboss instance is
  • Install a new, vanilla instance
  • Copy the standalone directory from the old instance to the new one
  • Copy any additional modules from old instance to new one
  • Start up the new instance
  • Apply some configuration changes via CLI
    The problem here is that we might upgrade one of the modules which are referenced in the configuration, like database driver used from one or more datasources and referenced for a login module.
    So if we start the server to apply the configuration changes we'll have errors because of the changed modules.

  Is it possible to use CLI without starting any subsystem and public connections to prevent from startup errors or application traffic?