Jboss AS 7 not deploying giving Exception : org.dom4j.DocumentException

[kabichill]

17:03:54,612 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

17:03:56,175 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

17:03:56,426 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting

17:04:05,461 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

17:04:05,462 INFO  [org.xnio] XNIO Version 3.0.3.GA

17:04:05,591 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA

17:04:05,814 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA

17:04:06,050 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

17:04:08,053 INFO  [org.jboss.as.connector] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

17:04:09,231 INFO  [org.jboss.as.security] (MSC service thread 1-1) JBAS013100: Current PicketBox version=4.0.7.Final

17:04:10,446 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)

17:04:11,369 INFO  [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service

17:04:12,233 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080

17:04:12,510 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]

17:04:14,446 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA

17:04:16,402 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory C:\Backup\Eclipse\Share\Jboss\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\standalone\deployments

17:04:16,523 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on localhost/127.0.0.1:4447

17:04:16,525 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /127.0.0.1:9999

17:04:18,297 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/MySqlDS]

17:04:19,139 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "Virtuoso.war"

17:06:24,498 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry activation.jar in "/C:/Backup/Eclipse/Share/Jboss/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/bin/content/Virtuoso.war/WEB-INF/lib/mail-1.4.jar"  does not point to a valid jar for a Class-Path reference.

17:06:26,146 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'

17:06:27,491 INFO  [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for Virtuoso

17:06:32,995 INFO  [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011402: Starting Persistence Unit Service 'Virtuoso.war#Virtuoso'

17:06:33,623 INFO  [org.hibernate.annotations.common.Version] (MSC service thread 1-2) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}

17:06:33,651 INFO  [org.hibernate.Version] (MSC service thread 1-2) HHH000412: Hibernate Core {4.0.1.Final}

17:06:33,699 INFO  [org.hibernate.cfg.Environment] (MSC service thread 1-2) HHH000206: hibernate.properties not found

17:06:33,703 INFO  [org.hibernate.cfg.Environment] (MSC service thread 1-2) HHH000021: Bytecode provider name : javassist

17:06:33,764 INFO  [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-2) HHH000204: Processing PersistenceUnitInfo [

    name: Virtuoso

    ...]

17:06:47,428 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.persistenceunit."Virtuoso.war#Virtuoso": org.jboss.msc.service.StartException in service jboss.persistenceunit."Virtuoso.war#Virtuoso": Failed to start service

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_20]

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_20]

    at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_20]

Caused by: org.hibernate.MappingException: Error while parsing file: orm.xml

    at org.hibernate.ejb.Ejb3Configuration.addClassesToSessionFactory(Ejb3Configuration.java:1255)

    at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:1047)

    at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:692)

    at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:72)

    at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)

    at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)

    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]

    ... 3 more

Caused by: org.hibernate.InvalidMappingException: Unable to read XML

    at org.hibernate.internal.util.xml.MappingReader.readMappingDocument(MappingReader.java:106)

    at org.hibernate.cfg.Configuration.add(Configuration.java:474)

    at org.hibernate.cfg.Configuration.add(Configuration.java:470)

    at org.hibernate.cfg.Configuration.add(Configuration.java:643)

    at org.hibernate.cfg.Configuration.addInputStream(Configuration.java:681)

    at org.hibernate.ejb.Ejb3Configuration.addClassesToSessionFactory(Ejb3Configuration.java:1247)

    ... 10 more

Caused by: org.dom4j.DocumentException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory Nested exception: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory

    at org.dom4j.io.SAXReader.read(SAXReader.java:484)

    at org.hibernate.internal.util.xml.MappingReader.readMappingDocument(MappingReader.java:76)

    ... 15 more

17:06:47,648 INFO  [org.jboss.as] (MSC service thread 1-1) JBAS015951: Admin console listening on http://127.0.0.1:9990

17:06:47,650 ERROR [org.jboss.as] (MSC service thread 1-1) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 176712ms - Started 278 of 478 services (123 services failed or missing dependencies, 76 services are passive or on-demand)

17:06:47,847 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "Virtuoso.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"Virtuoso.war#Virtuoso\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"Virtuoso.war#Virtuoso\": Failed to start service"}}

17:06:47,854 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report

JBAS014777:   Services which failed to start:      service jboss.persistenceunit."Virtuoso.war#Virtuoso": org.jboss.msc.service.StartException in service jboss.persistenceunit."Virtuoso.war#Virtuoso": Failed to start service

17:06:48,011 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"Virtuoso.war#Virtuoso\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"Virtuoso.war#Virtuoso\": Failed to start service"}}}}

17:06:52,899 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment Virtuoso.war in 5003ms

Caused by: org.dom4j.DocumentException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory Nested exception: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory

any solutions for this .??

Thanks in Advance

[nickarls]

Take out any dom4j libs you have bundled in the WAR lib

[sfcoy]

Are you trying to use the built-in hibernate implementation or are you using an implementation that you have added to your Virtuoso.war?

Ideally, you would remove all traces of Hibernate and it's dependencies (including dom4j!) from your web application.

[kabichill]

i am using my own implementation of hibernate . and i cant remove all traces of hiberate because it is highly essential. are there ways to avoid adding dependency to dom4j jar alone ?

[nickarls]

http://badr-elhouari.blogspot.fi/2011/10/how-to-use-hibernate-3-as-jpa-provider.html

is an article on how to use Hibernate 3 as a provider, it might also apply. jboss-deployment-structure.xml can be used for filtering out stuff but it should not be required in this case if you use your own hibernate altogether)

[sfcoy]

A web application I worked on recently that was using Hibernate 3.3.2.GA and friends worked perfectly on JBoss AS 7.1.3 with the following jboss-classloading.xml file in it's WEB-INF directory:

{code:xml}<?xml version="1.0" encoding="UTF-8"?>
<classloading xmlns="urn:jboss:classloading:1.0"
    domain="yourapp-web" 
    parent-domain="DefaultDomain"
    export-all="NON_EMPTY"
    import-all="true"
    parent-first="false"
    excluded="org.apache.log4j,org.slf4j"
    >
    <!-- Forces the use of JBoss provided log4j and slf4j implementations -->
</classloading>{code}

Your mileage may vary...

[kabichill]

i am not able to remove dom4j jar from the build path , if i remove while packaging , it is showing dom4j jar missing error so war file is not created

[nickarls]

If you are building with maven, you can scope the dom4j to "provided". It will compile against it doesn't get included. Dependencies on the AS-side will then come by  transitivity rules (e.g. from Hibernate dependency) or then you can add then yourself with the jboss-deployment-structure.xml or a Dependencies: row in the manifest

[kabichill]

Thanks Nicklas that worked added the scope provided and Exception : org.dom4j.DocumentException went away

          <dependency>

                <groupId>dom4j</groupId>

                <artifactId>dom4j</artifactId>

                <version>1.6.1</version>

               <scope>provided</scope>

            </dependency>

thanks for ur support