4 Replies Latest reply on Sep 11, 2002 12:31 PM by Randahl Fink Isaksen

    jboss 3.0.1 Deployment problem

    Geoffry Roberts Newbie

      I have been referred to this forum by the Persistence & CMP people.

      First a bit of background:

      I was attempting to deploy a file that had previously deployed without error on jboss 3.0 alpha.

      However, on jboss 3.0 final the following occurred:

      3.0.0RC3/server/default/deploy/hl7.jar
      java.lang.ClassFormatError: net.niat.entity.SuperEntityBean$Proxy (Repetitive method name/signature)

      I had never seen this Repetitive method error before so I asked about it and was advised to upgrade to jboss 3.0.1.

      Things went poorly with 3.0.1 and my hl7.jar so I tried another file (perf.jar) one that deploys perfectly with 3.0 final.

      This is part of the exchange from the other forum:

      >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
      >
      >***
      >
      >dsundstrom
      >
      >Posts: 842
      >From: Minneapolis, MN USA
      >Registered: Dec, 2001
      >
      >Re: JBoss 3.0.0RC3 + j2sdk1.4.0 Posted: Aug 19, 2002 >8:25 AM
      >[Reply to this message] Reply
      >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.

        • 1. Re: jboss 3.0.1 Deployment problem
          Adrian Brock Master

          Actually this is a CMP question.

          Your perf/SubSection is not deploying.
          It is looking for a type mapping for "true".

          Look in server/default/conf/standardjbosscmp-jdbc.xml

          Regards,
          Adrian

          • 2. Re: jboss 3.0.1 Deployment problem
            Geoffry Roberts Newbie

            I have jbosscmp-jdbc.xml as a part of the deployment. It contains the type mappings for mySQL pasted in from the jboss distribution.

            If what you say is true, why would the deployment work on 3.0 and not on 3.0.1? It seems something in jboss has changed.

            Let me ask this if I may. My original question and problem was that on 3.0 I am getting an error:

            3.0.0RC3/server/default/deploy/hl7.jar
            java.lang.ClassFormatError: net.niat.entity.SuperEntityBean$Proxy (Repetitive method name/signature)

            It was in response to this error that Dain advised me to upgrade to 3.0.1, which I did spawning the matters above.

            I can't tell from the message what the problem really is. I tried looking for a duplicate method somewhere but there is none of that.

            Any thoughts? Thanks.

            • 3. Re: jboss 3.0.1 Deployment problem
              Adrian Brock Master

              Can you post some information about the class
              and its interfaces.

              Do you inherit from the same interface twice in
              different parts of the hierarchy?
              I've seen this break some reflection based routines
              when switching to java 1.4, including Sun's jmx
              implementation.
              One easy way to check this is to run javadoc over
              your classes. You will see the method twice, under
              different classes.

              If you do see this problem, it is a bug in the
              ProxyComplier.

              Regards,
              Adrian

              • 4. Re: jboss 3.0.1 Deployment problem
                Randahl Fink Isaksen Novice

                Regarding the ClassFormatError: This is now listed in the bug database as bug #607895.

                In hopes it will be solved soon
                Randahl