9 Replies Latest reply on Apr 28, 2004 11:16 AM by Sherman Wood

    A deploy error

    peter_y_wang Newbie

      I got the following errors when deploying nukes-1.0.0-src

      19:40:33,559 ERROR [STDERR] java.lang.NoSuchFieldError: minMergeDocs
      19:40:33,559 ERROR [STDERR] at org.jboss.nukes.core.modules.index.Index.getW
      riter(Index.java:351)
      19:40:33,559 ERROR [STDERR] at org.jboss.nukes.core.modules.index.Index.acce
      ss$200(Index.java:36)
      19:40:33,559 ERROR [STDERR] at org.jboss.nukes.core.modules.index.Index$Writ
      erTask.run(Index.java:540)
      19:40:33,559 ERROR [STDERR] at EDU.oswego.cs.dl.util.concurrent.QueuedExecut
      or$RunLoop.run(QueuedExecutor.java:88)
      19:40:33,559 ERROR [STDERR] at java.lang.Thread.run(Thread.java:536)

      Can anyone help?

        • 1. Re: A deploy error
          kenny1 Newbie

          I have a similar problem, as follows
          java.lang.NoSuchMethodError: org.apache.bcel.generic.InstructionFactory.createNe
          wArray(Lorg/apache/bcel/generic/Type;S)Lorg/apache/bcel/generic/Instruction;
          at org.jboss.proxy.compiler.ProxyImplementationFactory.createProxyMethod
          (ProxyImplementationFactory.java:319)
          at org.jboss.proxy.compiler.ProxyCompiler.getCode(ProxyCompiler.java:167
          )
          at org.jboss.proxy.compiler.Runtime.makeProxyType(Runtime.java:66)
          at org.jboss.proxy.compiler.ProxyCompiler.(ProxyCompiler.java:76)
          at org.jboss.proxy.compiler.Proxies$Impl.newTarget(Proxies.java:603)
          at org.jboss.proxy.compiler.Proxies.newTarget(Proxies.java:78)
          at org.jboss.proxy.compiler.Proxy.newProxyInstance(Proxy.java:49)
          at org.jboss.ejb.plugins.cmp.jdbc.JDBCCreateBeanClassInstanceCommand.<in
          it>(JDBCCreateBeanClassInstanceCommand.java:62)
          at org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createCreateBeanCla
          ssInstanceCommand(JDBCCommandFactory.java:123)
          at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.startStoreManager(JDB
          CStoreManager.java:463)
          at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManage
          r.java:388)
          at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManag
          er.java:152)
          at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:342)
          at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1
          92)
          at sun.reflect.GeneratedMethodAccessor65.invoke(Unknown Source)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
          sorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:324)
          at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
          nDispatcher.java:284)
          at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
          at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
          ler.java:976)
          at $Proxy15.start(Unknown Source)
          at org.jboss.system.ServiceController.start(ServiceController.java:394)
          at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
          sorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:324)
          at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
          nDispatcher.java:284)
          at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
          at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
          at $Proxy82.start(Unknown Source)
          at org.jboss.ejb.EjbModule.startService(EjbModule.java:331)
          at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1
          92)
          at sun.reflect.GeneratedMethodAccessor65.invoke(Unknown Source)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
          sorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:324)
          at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
          nDispatcher.java:284)
          at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
          at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
          ler.java:976)
          at $Proxy15.start(Unknown Source)
          at org.jboss.system.ServiceController.start(ServiceController.java:394)
          at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
          sorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:324)
          at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
          nDispatcher.java:284)
          at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
          at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
          at $Proxy12.start(Unknown Source)
          at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:544)
          at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
          at org.jboss.deployment.MainDeployer.start(MainDeployer.java:824)
          at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:642)
          at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
          at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
          sorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:324)
          at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
          nDispatcher.java:284)
          at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
          at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
          at $Proxy6.deploy(Unknown Source)
          at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
          tScanner.java:302)
          at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
          canner.java:476)
          at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
          doScan(AbstractDeploymentScanner.java:201)
          at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
          loop(AbstractDeploymentScanner.java:212)
          at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
          run(AbstractDeploymentScanner.java:191)
          23:53:00,305 INFO [StatelessSessionInstancePool] Started jboss.j2ee:jndiName=nu
          kes/bb/rw/Utils,plugin=pool,service=EJB


          I also have tried building from cvs2004-03-13 (following the InstallUninstallUpgrade wiki), still no luck. The build stops and gives a fatal error on some xslt transformation. I hope someone could enlight me.

          • 2. Re: A deploy error
            Sherman Wood Apprentice



            Kenny,

            You have a different problem(s) than peter_y_wang.

            For the stack trace problem, it looks like you have some mismatch between what JBoss is expecting and BCEL. Are you using the vanilla jboss-3.2.3_nukes-1.0.0.zip?

            For the problems deploying from a CVS snapshot, try the plain DB setup without the installer. See:

            http://jboss.org/wiki/Wiki.jsp?page=NukesDBSetup

            • 3. Re: A deploy error
              kenny1 Newbie

              Sgwood,
              Yes, I am using the jboss-3.2.3_nukes-1.0.0.zip, but I have no clue of BCEL (from Jakarta?). If so, I don't have it installed. If not, how could I get around this?

              • 4. Re: A deploy error
                Sherman Wood Apprentice


                bcel comes with JBoss (server/default/lib/bcel.jar). It just looks like you have incompatible versions of JBoss EJB and bcel in the classpath.

                How did you start JBoss? In a shell window, running:

                <nukes_install_dir>/jboss-3.2.3_nukes-1.0.0/bin/run ?


                Sherman

                • 5. Re: A deploy error
                  kenny1 Newbie

                   

                  "sgwood" wrote:

                  bcel comes with JBoss (server/default/lib/bcel.jar). It just looks like you have incompatible versions of JBoss EJB and bcel in the classpath.

                  How did you start JBoss? In a shell window, running:

                  <nukes_install_dir>/jboss-3.2.3_nukes-1.0.0/bin/run ?
                  Sherman


                  This is exactly what I did. And I also try deleting bcel.jar and see what happens. It turns out throwing the same exception... So I suspect jboss either never found bcel.jar in the first place or there is a conflict with other jars.
                  For your information, my CLASSPATH = %JAVA_HOME%\lib\tools.jar;
                  and that's it. Should cause a conflict at all..

                  Anyway, I am still trying to find out what goes wrong. If this problem persists, I might go back building from cvs again.... although that may be a hassle (at least to me)... Thanks Sherman.

                  • 6. Re: A deploy error
                    kenny1 Newbie

                    Found out my problem was having xalan.jar in %JAVA_HOME%/jre/lib/endorsed, which contains bcel that is not up-to-date. Removing it makes Nukes on Jboss work finally. Thanks Sherman.

                    • 7. Re: A deploy error
                      peter_y_wang Newbie

                      Found out my problem was because I’m running both nukes and portlet on my JBoss. There are some conflict in configuration. When I removed portlets and reinstalled JBoss3.2.3 the problem disappeared.

                      Maybe there was an incompatible version of JBoss EJB that come with my portlet. Now I decided to run them separately.

                      • 8. Re: A deploy error
                        Marc Golinelli Newbie

                        I experience such deployment error in our project with jboss3.2.2 due to the latest version of Xalan 2.6.0 which contains bcel that is not up-to-date.
                        Does that means that it is impossible to upgrade Xalan version with jboss 3.2.2 and JDK 1.4 ?

                        Besides, for access jboss.server.data.dir access error, you may specify the -Dboss.server.data.dir=/path/to/server/data system property in your Jboss startup script to solve the problem.
                        see http://jboss.org/index.html?module=bb&op=viewtopic&t=47339

                        Regards,

                        • 9. Re: A deploy error
                          Sherman Wood Apprentice

                          Nukes is for JBoss 3.2.3. There are some differences in the MBean implementation between 3.2.2 and 3.2.3.


                          Sherman