3 Replies Latest reply on May 5, 2006 10:53 AM by peterj

    NullPointerException in ScannerThread

    ryandavid

      Hello,
      I am using jboss 3.2.3 wih Java 1.4.2_03 on Linux.

      My server hosts about 20-25 applications.

      Sometimes, after a long period I note this error on the server log

      2006-05-04 14:50:10,348 ERROR [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Scanning failed; continuing
      java.lang.NullPointerException
      at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:119)
      at org.jboss.mx.loading.UnifiedClassLoader3.loadClassImpl(UnifiedClassLoader3.java:169)
      at org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:123)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:282)

      The only (and ugly !) solution is to restart jboss.

      I checked that all permissions in the deploy directory are corrects. Have you any idea of the reason ?

      Thanks
      Bye

        • 1. Re: NullPointerException in ScannerThread
          peterj

          Are you by any chance deploying an application at about the time you get this error? If so, and if it takes more than a millisecond or 2 to copy the app, then there is a good chance that the hot deployer will attempt to deploy the application before it is fully copied, resulting in the error that you noticed. One way to avoid this problem is to copy your app to a temporary directory on the same disk partition as the app server, and then move the app to the deploy directory.

          If you are not making use of hot deployment, you can always turn it off.

          • 2. Re: NullPointerException in ScannerThread
            ryandavid

            As always I copied the new ear file with '#' suffix. Then I renamed the file removing the '#' character.

            This could be the reason ?

            Anyway do you know how to stop this error without restart jboss ?

            • 3. Re: NullPointerException in ScannerThread
              peterj

              It could be. My copy and then move suggestion should prevent the error.