Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-2919

Disable post-boot deployment scanning by default

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Unresolved
    • Minor
    • None
    • None
    • EAP6, EAP7
    • None

    Description

      The deployment-scanner subsystem shouldn't be configured to scan after boot by default, it is consuming resources and in a containerised application this is not something likely to happen. I believe, though, this is something that some applications might require, so it should be possible to enable it through a configuration parameter, but not by default.

      <subsystem xmlns="urn:jboss:domain:deployment-scanner:2.0">
                  <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" auto-deploy-exploded="false" runtime-failure-causes-rollback="${jboss.deployment.scanner.rollback.on.failure:false}"/>
      </subsystem>
      

      Attachments

        Activity

          People

            kwills@redhat.com Ken Wills
            rhn-support-rromerom Ruben Romero Montes
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: