Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-856

Unable to deploy any Weld application(s) on AIX

XMLWordPrintable

    • Hide

      Attempt to deploy any Weld application on AIX. I trimmed our application down to nothing but a empty WAR file with a beans.xml file and it failed. So it is when Weld is bootstrapping that this occurs.
      I also deployed the Weld number guess example and it failed as well.

      Show
      Attempt to deploy any Weld application on AIX. I trimmed our application down to nothing but a empty WAR file with a beans.xml file and it failed. So it is when Weld is bootstrapping that this occurs. I also deployed the Weld number guess example and it failed as well.

      Deployment of any Weld application fails on AIX. The same application can be deployed on Windows, MACOSX, Linux (tested on Redhat), etc. Seems to be some sort of a classloader issue.

      2011-02-14 14:49:04,760 TRACE [org.jboss.classloader.spi.base.BaseClassLoader] (Thread-7) BaseClassLoader@376a376a

      {bootstrap-classloader:0.0.0$MODULE}

      class not found sun.reflect.GeneratedMethodAccessor124
      2011-02-14 14:49:04,739 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (Thread-7) Error installing to Start: name=vfs:///usr/local/SOA/jboss/server/prelude/deploy/prelude-soa-rest-api.war_WeldBootstrapBean state=Create: org.jboss.weld.exceptions.WeldException: by java.lang.NoClassDefFoundError: org.jboss.weldx.transaction.org$jboss$weld$bean-jboss$classloader:id="vfs:$$$usr$local$SOA$jboss$server$prelude$deployers$resteasy$deployer"-Built-in-UserTransaction_$$_WeldProxy
      at org.jboss.weld.bean.proxy.ProxyFactory.getProxyClass(ProxyFactory.java:285) [:6.0.0.Final]

            [WELD-856] Unable to deploy any Weld application(s) on AIX

            Ales Justin added a comment -

            Still some issues with this:

            Ales Justin added a comment - Still some issues with this: http://seamframework.org/Community/UnableToDeployWeldApplicationOnAix#comment152196

            Ales Justin added a comment -

            https://github.com/weld/core/commit/2db9d06f473d9031c6f46a80615d6c81dd0d6755

            Ales Justin added a comment - https://github.com/weld/core/commit/2db9d06f473d9031c6f46a80615d6c81dd0d6755

            Štěpán Mík (Inactive) added a comment -

            We are experiencing the same problem. Could you please post patched weld library? At least until JBoss brings more permanent solution.

            Štěpán Mík (Inactive) added a comment - We are experiencing the same problem. Could you please post patched weld library? At least until JBoss brings more permanent solution.

            Mike Finkenzeller (Inactive) added a comment -

            After some debugging I actually figured out what it does not like but not yet why.

            The issue is actually the proxyName being used. I changed the proxyName to something simple in ProxyFactory and then the proxies started to generate, the application deployed, and the integration tests worked. That tested the whole stack (RESTEasy, WELD, etc.)

            Changing this in ProxyFactory in method static String getProxyName(Class<?> proxiedBeanType, Set<? extends Type> typeClosure, Bean<?> bean)

            String className = beanId.replace('.', '$').replace(' ', '_').replace('/', '$').replace(';', '$');

            to this.....

            String className = beanId.replace('.', '$').replace(' ', '_').replace('/', '$').replace(';', '$').replace(':','$').replace('[', '$');

            So basically removing the ':' and '[' characters in the proxyName resolved the issue. Interesting.....

            Probably needs to be reviewed, but I can create a patch for it so Weld with deploy on AIX.

            Mike Finkenzeller (Inactive) added a comment - After some debugging I actually figured out what it does not like but not yet why. The issue is actually the proxyName being used. I changed the proxyName to something simple in ProxyFactory and then the proxies started to generate, the application deployed, and the integration tests worked. That tested the whole stack (RESTEasy, WELD, etc.) Changing this in ProxyFactory in method static String getProxyName(Class<?> proxiedBeanType, Set<? extends Type> typeClosure, Bean<?> bean) String className = beanId.replace('.', '$').replace(' ', '_').replace('/', '$').replace(';', '$'); to this..... String className = beanId.replace('.', '$').replace(' ', '_').replace('/', '$').replace(';', '$').replace(':','$').replace('[', '$'); So basically removing the ':' and '[' characters in the proxyName resolved the issue. Interesting..... Probably needs to be reviewed, but I can create a patch for it so Weld with deploy on AIX.

              ajustin@redhat.com Ales Justin
              mikefinkenzeller Mike Finkenzeller (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: