XWiki Platform

Failed to deploy on JBoss AS7 with Taglib errors

Details

  • Difficulty:
    Unknown
  • Documentation:
  • Documentation in Release Notes:
  • Similar issues:
    XWIKI-7987Failed to deploy on JBoss AS7 with SLF4J class cast exception
    XWIKI-7989Fail to import Default XE XAR in JBoss AS7
    XWIKI-1027Support deployment on Jboss 4.x
    XWIKI-8565Rendering cache does not work on JBOSS AS7
    XWIKI-4123Deployment of XWiki 1.9.2 fails on Glassfish 2.1
    XWIKI-8667{{code}} macro fails with "java.lang.ArrayIndexOutOfBoundsException" in JBoss AS
    XWIKI-5946Extension manager fails on JBoss AS 5
    XWIKI-7984Jboss AS 7 does not like jython
    XWIKI-1744Use JBoss Cache by default in XWiki
    XWIKI-3093Container managed Datasource not working (JBOSS 4.2.2, Xwiki 1.6.2)

Description

The xwiki release war is not compatible with jboss AS 7. You end up with this error message. 

16:30:16,310 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."xwiki.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xwiki.war".POST_MODULE: Failed to process phase POST_MODULE of deployment "xwiki.war"
        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.7.0_04]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_04]
        at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_04]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.ClassNotFoundException: org.apache.struts.taglib.MessageTag from [Module "deployment.xwiki.war:main" from Service Module Loader]
        at org.jboss.as.jaxrs.deployment.JaxrsComponentDeployer.deploy(JaxrsComponentDeployer.java:65)
        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
        ... 5 more
Caused by: java.lang.ClassNotFoundException: org.apache.struts.taglib.MessageTag from [Module "deployment.xwiki.war:main" from Service Module Loader]
        at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
        at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
        at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
        at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
        at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
        at org.jboss.as.jaxrs.deployment.JaxrsComponentDeployer.deploy(JaxrsComponentDeployer.java:63)
        ... 6 more

When solved, this error leads to troubles with slf4j.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
David Delbecq added a comment - - edited

To solve issue, (works for me), do all the following:

1) remove all Tlds in WEB-INF/*.tld
2) comment out or remove the tld section in web.xml (any way, those tld are unerelated to struts version used, they point to classes that have been moved away)

  <!--
  <jsp-config>
    <taglib>
      <taglib-uri>/WEB-INF/struts-bean.tld</taglib-uri>
      <taglib-location>/WEB-INF/struts-bean.tld</taglib-location>
    </taglib>

    <taglib>
      <taglib-uri>/WEB-INF/struts-html.tld</taglib-uri>
      <taglib-location>/WEB-INF/struts-html.tld</taglib-location>
    </taglib>

    <taglib>
      <taglib-uri>/WEB-INF/struts-logic.tld</taglib-uri>
      <taglib-location>/WEB-INF/struts-logic.tld</taglib-location>
    </taglib>
  </jsp-config>-->

3) create a file WEB-INF/jboss-deployment-structure.xml with this content:

<jboss-deployment-structure>
    <deployment>
        <!-- Exclusions allow you to prevent the server from automatically adding some dependencies     -->
        <exclusions>
            <module name="org.slf4j" />
            <module name="org.slf4j.impl" />
            <module name="org.hibernate" />
        </exclusions>
    </deployment>
</jboss-deployment-structure>
Show
David Delbecq added a comment - - edited To solve issue, (works for me), do all the following: 1) remove all Tlds in WEB-INF/*.tld 2) comment out or remove the tld section in web.xml (any way, those tld are unerelated to struts version used, they point to classes that have been moved away) <!-- <jsp-config> <taglib> <taglib-uri> /WEB-INF/struts-bean.tld </taglib-uri> <taglib-location> /WEB-INF/struts-bean.tld </taglib-location> </taglib> <taglib> <taglib-uri> /WEB-INF/struts-html.tld </taglib-uri> <taglib-location> /WEB-INF/struts-html.tld </taglib-location> </taglib> <taglib> <taglib-uri> /WEB-INF/struts-logic.tld </taglib-uri> <taglib-location> /WEB-INF/struts-logic.tld </taglib-location> </taglib> </jsp-config> --> 3) create a file WEB-INF/jboss-deployment-structure.xml with this content: <jboss-deployment-structure> <deployment> <!-- Exclusions allow you to prevent the server from automatically adding some dependencies --> <exclusions> <module name= "org.slf4j" /> <module name= "org.slf4j.impl" /> <module name= "org.hibernate" /> </exclusions> </deployment> </jboss-deployment-structure>
Hide
Permalink
Vincent Massol added a comment -

Taglibs removed since we don't use/need them.

Show
Vincent Massol added a comment - Taglibs removed since we don't use/need them.
Hide
Permalink
Vincent Massol added a comment -

David, just one question, why did you have to exclude:

<module name="org.hibernate" />

It works fine for me without this exclusion.

Thanks

Show
Vincent Massol added a comment - David, just one question, why did you have to exclude: <module name="org.hibernate" /> It works fine for me without this exclusion. Thanks
Hide
Permalink
David Delbecq added a comment -

Automatism.

I remember i had problems in the past with jboss 5 + hibernate from container.
I know from experience that webapplications do not like to be forced to use a specific hibernate version that might be different from the one embedded in webapp. So, since xwiki was providing an hibernate implementation, i didn't want the jboss one to be in the way.

Show
David Delbecq added a comment - Automatism. I remember i had problems in the past with jboss 5 + hibernate from container. I know from experience that webapplications do not like to be forced to use a specific hibernate version that might be different from the one embedded in webapp. So, since xwiki was providing an hibernate implementation, i didn't want the jboss one to be in the way.

People

  • Assignee:
    Vincent Massol
    Reporter:
    David Delbecq
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
    Date of First Response: