EAP 7 can create a deployment marker file unexpectedly even if scanEnabled="false" is specified in the deployment-scanner subsystem

Solution Verified - Updated

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.0.x
    • 7.1.x

Issue

I specified scanEnabled="false" in the deployment-scanner subsystem to disable deployment scan. When I deployed an application through the management CLI and the same filename to the application exists under the deployment scanner directory "deployments", a deployment marker file is created unexpectedly.

Resolution

[JBEAP-15999](https://issues.jboss.org/browse/JBEAP-15999 "This content is not included.GSS FileSystemDeploymentService#handleNotification() can create an unneeded deployment marker file even if scanEnabled="false" is specified") is raised for this issue. This behavior will be fixed in the future releases (tentatively, EAP 7.2.1 or later).

However, this behavior itself does not have any other negative impact than creating an unneeded marker file. So, you can simply ignore this.

If you do not like such behavior and do not need deployment scanner, you can disable (= remove) the deployment-scanner subsystem instead of setting scanEnabled="false":

/subsystem=deployment-scanner:remove()
SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.