Topic
7 replies Latest Post - ‏2012-11-06T13:27:35Z by SystemAdmin
FrederikDeBacker
FrederikDeBacker
3 Posts
ACCEPTED ANSWER

Pinned topic ModellerException during EBA deploy in WAS liberty profile

‏2012-10-22T07:27:50Z |
Hello,

I am trying to deploy an EBA into WAS 8.5 liberty profile and I get the below exception:

AUDIT CWWKZ0304E: An exception was generated when trying to resolve the contents of the application . The exception text from the OSGi framework is: org.apache.aries.application.modelling.ModellerException: org.apache.aries.application.InvalidAttributeException: APPMODELLING0002E: An internal error occurred. A bundle manifest must contain exactly one Bundle-SymbolicName entry. The following entry was found null.

Deployment of this EBA into WAS 8.0 was ok. Any idea what could be the issue here. I verified all the bundles in the EBA and they all have a valid Bundle-SymbolicName manifest header.

Thanks in advance,

Frederik.
  • Emily Jiang
    Emily Jiang
    10 Posts
    ACCEPTED ANSWER

    Re: ModellerException during EBA deploy in WAS liberty profile

    ‏2012-10-22T08:35:08Z  in response to FrederikDeBacker
    This is quite odd as Liberty and tWAS share the same modeller. Can you collect the trace with trace string of org.apache.aries.application.modelling.*=all? Alternatively, attach your MANIFEST.MF here.
    Thanks
    Emily
    • Emily Jiang
      Emily Jiang
      10 Posts
      ACCEPTED ANSWER

      Re: ModellerException during EBA deploy in WAS liberty profile

      ‏2012-10-22T08:59:39Z  in response to Emily Jiang
      What I meant was that the libery profile and full profile share the same modeller codebase.
      • FrederikDeBacker
        FrederikDeBacker
        3 Posts
        ACCEPTED ANSWER

        Re: ModellerException during EBA deploy in WAS liberty profile

        ‏2012-10-22T12:39:38Z  in response to Emily Jiang
        Hi Emily,

        Please find the trace in attach.

        kr,

        Frederik.

        Attachments

        • Emily Jiang
          Emily Jiang
          10 Posts
          ACCEPTED ANSWER

          Re: ModellerException during EBA deploy in WAS liberty profile

          ‏2012-10-26T11:12:09Z  in response to FrederikDeBacker
          After looking at your trace, it seems the server complains about the bundle of com.springsource.org.aspectj.weaver-1.6.5.RELEASE.jar. Can you paste this bundle's Manifest.mf here? For some reason, the modeller thinks the value of the header of Bundle-SymbolicName is invalid.

          Thanks
          Emily
          • FrederikDeBacker
            FrederikDeBacker
            3 Posts
            ACCEPTED ANSWER

            Re: ModellerException during EBA deploy in WAS liberty profile

            ‏2012-10-30T10:48:51Z  in response to Emily Jiang
            Emily,

            Please find the manifest.mf in attach.

            kr,

            Frederik.
            • Emily Jiang
              Emily Jiang
              10 Posts
              ACCEPTED ANSWER

              Re: ModellerException during EBA deploy in WAS liberty profile

              ‏2012-10-31T21:40:56Z  in response to FrederikDeBacker
              Hi Frederik,

              Your manifest.mf looks correct to me. Try to restart your server with --clean to clear any cache. Just guess the jar might be corrupted for some reason. Please let me know whether you hit the same problem.

              Thanks
              Emily
              • SystemAdmin
                SystemAdmin
                590 Posts
                ACCEPTED ANSWER

                Re: ModellerException during EBA deploy in WAS liberty profile

                ‏2012-11-06T13:27:35Z  in response to Emily Jiang
                The AspectJ manifest contains a Name header that causes issues with the Aries Bundle Manifest Processor (org.apache.aries.util.manifest.ManifestProcessor) used by Websphere Liberty Profile.

                Name: org.aspectj/weaver/

                It's unclear why this header is present in the bundle manifest or why the Aries ManifestProcessor has special handling for it. (As soon as the ManifestProcessor encounters the Name field it stops normal processing of manifest headers).

                For now, removing the Name header from the Manifest will solve the issue.

                As far as a final solution is concerned, it's not clear to me yet if

                a) there's an error in the manifest of aspectj weaver (coming from the Spring bundle repository).
                b) there's a bug in the Aries ManifestProcessor.