Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-11860

Persistent deployments are lost on restart with '--read-only-server-config'

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 13.0.0.Final
    • None
    • None
    • Hide
      • start Wildfly with `--read-only-server-config` flag
      • deploy an artefact (e.g. through JBoss CLI)
      • observe how in `standalone_xml_history/read-only-config.last.xml` the deployment is correctly added
      • restart Wildfly
      • observe how the the file containing the deployment information was moved into another directory (e.g. `20190318-144809600`)
      Show
      start Wildfly with `--read-only-server-config` flag deploy an artefact (e.g. through JBoss CLI) observe how in `standalone_xml_history/read-only-config.last.xml` the deployment is correctly added restart Wildfly observe how the the file containing the deployment information was moved into another directory (e.g. `20190318-144809600`)

      I wanted to use the `read-only-server-config` feature in order to be able to have `standalone.xml` managed by configuration management. Additionally, I need the ability to restart Wildfly and have the same state afterwards. Unfortunately, in this case the artefacts that were deployed are not deployed anymore after the restart.

              bstansbe@redhat.com Brian Stansberry
              maxim-sermin Maxim Sermin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: