3 Replies Latest reply on May 10, 2004 6:20 PM by gorano

    Deployment scanner fails

    gorano Newbie

      Hi guys,

      I have run into some trouble. I have developed a system with 3 ear files.
      Admin, ModA and ModB.

      Admin contains a web interface and the model interact via RMI to
      session beans in ModA and ModB.

      Everything was fine until I implemented ModB. The admin interface
      showed all views as expected and Eclipse had no problems to
      redeploy my code.

      I implemented ModB and everything is fine (redeploy) until I access
      one of the views accesing data in ModB.

      If I do this I can't redeploy anymore. Jboss 3.2.3 throws the following
      exception (and repeats every 10 sec) :

      23:20:17,578 ERROR [AbstractDeploymentScanner$ScannerThread] Scanning failed; co
      at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:119)
      at org.jboss.mx.loading.UnifiedClassLoader3.loadClassImpl(UnifiedClassLoader3.j
      at org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:
      at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
      at java.net.FactoryURLClassLoader.loadClass(URLClassLoader.java:575)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
      at org.jboss.net.protocol.URLListerFactory.createURLLister(URLListerFactory.jav
      at org.jboss.net.protocol.URLListerFactory.createURLLister(URLListerFactory.jav
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(Ab
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(Abs

      I have never seen this error before. I am using commit option D and
      caching on my entity beans.

      If I stop and start Jboss it will deploy again until my first access of
      the session bean (that calls some entity beans) in ModB.

      ModA has some Entity beans mapped to the same tables as some entity beans in ModB.

      In production Admin, ModA and ModB will go on different servers (explains the different ears). at the moment all is in one JVM.

      Help! what is causing this. Entity Cahce or maybe the session I create
      via IE??

      Thanks in advance for anyone who have some ideas.