11 Replies Latest reply on Sep 19, 2002 11:25 AM by tangaloor

    JBoss 3.0.0RC3 + j2sdk1.4.0

    hskovby

      Hi,

      I am having a problem deploying my entity beans when running j2sdk1.4.0.
      When I deploy running j2sdk1.3.1 the entity beans deploys fine, but on j2sdk1.4.0 I get the following error message:

      19:39:04,687 INFO [MainDeployer] Starting deployment of package: file:/home/hs/JBoss/jboss-3.0.0RC3/server/default/deploy/country.jar
      19:39:05,165 INFO [EjbModule] Creating
      19:39:05,188 INFO [EjbModule] Deploying CountryEJB
      19:39:08,588 ERROR [MainDeployer] could not create deployment: file:/home/hs/JBoss/jboss-3.0.0RC3/server/default/deploy/country.jar
      java.lang.ClassFormatError: dk/diku/ebf/entities/country/CountryBean$Proxy (Repetitive method name/signature)
      at java.lang.ClassLoader.defineClass0(Native Method)
      at java.lang.ClassLoader.defineClass0(ClassLoader.java:509)
      at java.lang.ClassLoader.defineClass0(ClassLoader.java:438)
      at org.jboss.proxy.compiler.Runtime.makeProxyType(Runtime.java:68)
      at org.jboss.proxy.compiler.ProxyCompiler.(ProxyCompiler.java:76)
      at org.jboss.proxy.compiler.Proxies$Impl.newTarget(Proxies.java:580)
      at org.jboss.proxy.compiler.Proxies.newTarget(Proxies.java:77)
      at org.jboss.proxy.compiler.Proxy.newProxyInstance(Proxy.java:49)
      at org.jboss.ejb.plugins.cmp.jdbc.JDBCCreateBeanClassInstanceCommand.(JDBCCreateBeanClassInstanceCommand.java:52)
      at org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createCreateBeanClassInstanceCommand(JDBCCommandFactory.java:97)
      at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.create(JDBCStoreManager.java:358)
      at org.jboss.ejb.plugins.CMPPersistenceManager.create(CMPPersistenceManager.java:155)
      at org.jboss.ejb.EntityContainer.create(EntityContainer.java:337)
      at org.jboss.ejb.Container.invoke(Container.java:789)
      at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1055)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:867)

      Is it possible to run JBoss on j2sdk1.4.0, and if so, does anyone know what is going on?

      Regards,
      Henrik

        • 1. Re: JBoss 3.0.0RC3 + j2sdk1.4.0
          tafypz

          Hi Henrik,

          I'm running RC3 with J2SE 1.4 and i don't have any problem deploying my beans (session + entity CMP2).
          But I have problems with CMR, so using the "same environment" as yours, i don't experience your problem.
          Sorry I didn't manage to reproduce your exception.

          Hope you will solve it.
          Sebastien

          • 2. Re: JBoss 3.0.0RC3 + j2sdk1.4.0
            tonala

            I fimd myself with this same error. Has it ever been resolved? and if so what was done?

            Thanks in advance.

            • 3. Re: JBoss 3.0.0RC3 + j2sdk1.4.0
              dsundstrom

              Yes. Upgrade to 3.0.1.

              • 4. Re: JBoss 3.0.0RC3 + j2sdk1.4.0
                tonala

                I have now installed jboss 3.0.1 and I seem to have new problems.

                The following fragment from the log file shows errors I have never seen before in jboss. The deployment being logged here with 3.0.1 the same deploys faultlessly in 3.0.

                My os is Suse 8.0

                Is there something new in 3.0.1?

                ***

                Depends On Me: , ObjectName: jboss.j2ee:service=EJB,jndiName=perf/NextUIDGenerator
                state: FAILED
                I Depend On:
                Depends On Me: org.jboss.deployment.DeploymentException: expected one true-mapping tag, ObjectName: jboss.j2ee:service=EJB,jndiName=perf/SubSection
                state: FAILED

                ***

                • 5. Re: JBoss 3.0.0RC3 + j2sdk1.4.0
                  dsundstrom

                  There is an unresolved dependancy so your deployment has stalled. I don't know how to resolve this, but I suggest you ask in the EJB/JBoss forum.

                  • 6. Re: JBoss 3.0.0RC3 + j2sdk1.4.0
                    randahl

                    I have seen this bug even in 3.0.2. Any ideas when this will be fixed, it is really a big time show stopper.


                    R.

                    • 7. Re: JBoss 3.0.0RC3 + j2sdk1.4.0
                      dsundstrom

                      The problem was unresolved dependencies. Do you have this?

                      • 8. Re: JBoss 3.0.0RC3 + j2sdk1.4.0
                        randahl

                        No, but I have experienced the "ClassFormatError / Repetitive Method Signature" problem which is mentioned above on JBoss 3.0.2. I have filed this as Bug #607895


                        Randahl

                        • 9. Re: JBoss 3.0.0RC3 + j2sdk1.4.0
                          dsundstrom

                          The class format error is caused by compiling with one major version of the JDK and running in another. If you are runnign in JDK 1.4 you need to you entire application in JDK 1.4. As a side note, I do not recomend that you run JDK 1.4 as it is still very buggy.

                          • 10. Re: JBoss 3.0.0RC3 + j2sdk1.4.0
                            randahl

                            With all do respect, I think you are wrong in the assumption that the ClassFormatError can only be caused by using multiple versions of the JDK. As mentioned in the bug report, the error comes as a result of multiple inheritance. (Check out the bug report).

                            Randahl

                            • 11. Re: JBoss 3.0.0RC3 + j2sdk1.4.0
                              tangaloor

                              I don't know if you guys have figured this out yet, but I talked to my local Oracle DBA (actually works for Oracle, not just knows the product) and it turns out that the 8.1.7 Oracle JDBC drivers don't support JDK 1.4.x. I was getting this same error. If you go to version 9i, it will likely work with 1.4.x. I'm not ready to upgrade, so I'll just stick with 1.3.1. It was nice to find an answer (though not a resolution) to this annoying problem.