Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-7490

WildFly deployment scanner triggers infinite redeployment loop when source code and WildFly directories are mounted from Windows into Docker

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Deployment Scanner
    • None
    • Hide
      • Install Rancher Desktop on a Windows machine.
      • Enable container runtime (containerd or dockerd) in Rancher Desktop.
      • Prepare a Linux-based WildFly container image.
      • Prepare the following directories on the Windows host:
        • Source code repository
        • WildFly server directory (including standalone, deployments, etc.)
      • Start the WildFly container using Rancher Desktop with Windows-mounted volumes:
        • Mount the source code repository into the container.
        • Mount the WildFly server directory into the container.
      • Ensure the WildFly deployment scanner is enabled (default configuration).
      • Start the WildFly server inside the container.
      • Observe that:
        • Applications are deployed successfully during startup.
        • Web contexts are registered correctly.
      • Wait for a short period without making any file changes.
      • Observe that:
        • The deployment scanner detects file changes even though no files were modified.
        • Web contexts are unregistered.
        • Applications are repeatedly undeployed and redeployed.
      • Observe that this process continues indefinitely, resulting in an infinite redeployment loop.
      Show
      Install Rancher Desktop on a Windows machine. Enable container runtime (containerd or dockerd) in Rancher Desktop. Prepare a Linux-based WildFly container image. Prepare the following directories on the Windows host: Source code repository WildFly server directory (including standalone , deployments , etc.) Start the WildFly container using Rancher Desktop with Windows-mounted volumes: Mount the source code repository into the container. Mount the WildFly server directory into the container. Ensure the WildFly deployment scanner is enabled (default configuration). Start the WildFly server inside the container. Observe that: Applications are deployed successfully during startup. Web contexts are registered correctly. Wait for a short period without making any file changes. Observe that: The deployment scanner detects file changes even though no files were modified. Web contexts are unregistered. Applications are repeatedly undeployed and redeployed. Observe that this process continues indefinitely, resulting in an infinite redeployment loop.

      WildFly is running inside a Docker container with two Windows-mounted volumes:

      1. Source code repository
      2. WildFly server directory (including deployments)

      When the server starts:

      • WildFly initially deploys applications successfully and registers the web contexts.
      • After a short delay, the deployment scanner detects file changes even though no actual changes were made.
      • Based on these false change detections, WildFly unregisters the web contexts and redeploys the applications.
      • This leads to an infinite redeployment loop.

      This issue:

      • Does not occur when WildFly is run directly on Windows
      • Only occurs when the source code repo and WildFly directory are mounted into Docker from a Windows host

      Environment

      • Host OS: Windows
      • Container Runtime: Docker Desktop
      • Volumes:
        • Windows-mounted source code repository
        • Windows-mounted WildFly server directory
      • Application Server: WildFly
      • Deployment Scanner: Enabled{}

      • Request

      Please clarify why the deployment scanner detects file changes on mounted Windows volumes when no files are modified, and provide recommended configuration or workaround.

              ehugonne1@redhat.com Emmanuel Hugonnet
              shikhasb Shikha Sunil Bhagwanani
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: