Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-18863

Duplicate deployment scanner on Windows if set to custom

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.2.1.CR1
    • 4.2.1.CR1
    • server
    • Hide

      1. Setup a server using runtime detection (in my case I used the eap 6.3 server bundled with JBDS installer and autodetected)
      2. Open the server editor and set custom deployment folders; save
      3. Create a dynamic web project
      4. Start the server - notice that two deployment scanners were added after server start:

      15:39:29,028 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in 8385ms - Started 151 of 189 services (56 services are lazy, passive or on-demand)
15:39:29,780 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory E:\deployments\deploy
15:39:30,041 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory E:\deployments\deploy
      Show
      1. Setup a server using runtime detection (in my case I used the eap 6.3 server bundled with JBDS installer and autodetected) 2. Open the server editor and set custom deployment folders; save 3. Create a dynamic web project 4. Start the server - notice that two deployment scanners were added after server start: 15:39:29,028 INFO [org.jboss.as] (Controller Boot Thread ) JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in 8385ms - Started 151 of 189 services (56 services are lazy, passive or on-demand) 15:39:29,780 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory E:\deployments\deploy 15:39:30,041 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory E:\deployments\deploy

      Today I tried to verify a bug on Windows (JBIDE-18697) and in doing so, I noticed this bug:
      I tried deploying a dynamic web project to a custom folder with eap 6.3 on Windows 7. And I ended up with two custom deployment scanners in standalone.xml:

              <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
            <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/>
            <deployment-scanner name="jbosstoolsscanner1" path="E:/deployments/deploy" scan-interval="5000" deployment-timeout="600"/>
            <deployment-scanner name="jbosstoolsscanner2" path="E:\deployments\deploy" scan-interval="5000" deployment-timeout="600"/>
        </subsystem>

      Notice that those two added scanners are the same except for file delimiters - "/" vs. "\"

              rob.stryker Rob Stryker (Inactive)
              exd-mmalina Martin Malina
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: