2 Replies Latest reply on Feb 23, 2006 12:54 PM by Norton

    Scanning failed; continuing

    Norton Newbie

      Hi, all,

      I'm am trying to upgrade my application from JBoss 3.0.6 to 3.2.8 on RedHat running JDK 1.4.2_10.

      When I first start up JBoss with my applications in the deploy directory, my 5 ears deploy fine and my applications work as expected. During development, I have an ant build process that rebuilds my ears and redeploys them as exploded ears. Since these are all exploded ears, I delete the old ear directory before copying the new ear dir into the deploy directory. The build process has always worked well in 3.0.6. However, with 3.2.8, the first and second deploy ears fine, but with the third ear, JBoss starts reporting the following error:

      09:42:44,463 ERROR [AbstractDeploymentScanner$ScannerThread] Scanning failed; continuing
      java.net.MalformedURLException: org.jboss.net.protocol.file.FileURLLister
      at org.jboss.net.protocol.URLListerFactory.createURLLister(URLListerFactory.java:72)
      at org.jboss.net.protocol.URLListerFactory.createURLLister(URLListerFactory.java:53)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:387)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:213)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:224)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:203)

      The server goes into an infinite loop reporting this error every few seconds until I restart it. Since my build process goes on, all my rebuilt ears get copied into the deploy directory and when I restart, everything is fine.

      Can someone please tell me what might cause the above error?

      This third ear is significant in size and I noticed that during the deploy, JBoss sometimes reports that it can't find the application.xml file. This is likely because the JBoss deployer picked up the ear before the application.xml file was copied over. I would guess that this could be related to the above error, but it has never been a problem in 3.0.6. In 3.0.6, the application.xml file is eventually found without my intervention and the ear works as expected. Is there any way to make sure application.xml exists before JBoss picks it up?

      Any help with this error is appreciated. Restarting the server every time we deploy into production isn't a problem, but obviously will defeat the convenience of hot deployment in development.