JBOSS Failed to parse XML descriptor error
Problem: Getting error “Failed to parse XML descriptor” when trying to deploy “discover”application war on JBOSS server.
C:\jboss\jboss-eap-6.4\bin>standalone.bat | C:\MVN\ATGLogColorizer_v1_2.exe
ATGLogColorizer v1.2. Copyleft 2007-2008 by Kelly Goetsch. http://atglogcolorizer.sourceforge.net
Calling "C:\jboss\jboss-eap-6.4\bin\standalone.conf.bat"
Setting JAVA property to "C:\Program Files\Java\jdk1.8.0_73\bin\java"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "C:\jboss\jboss-eap-6.4"
JAVA: "C:\Program Files\Java\jdk1.8.0_73\bin\java"
JAVA_OPTS: "-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -XX:+UseCompressedOops -Dprogram.name=standalone.bat -Xms1G -Xmx1G -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.policy-permissions=true -Djboss.modules.system.pkgs=org.jboss.byteman"
===============================================================================
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0
19:41:07,840 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.6.Final-redhat-1
19:41:07,977 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1
19:41:08,036 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) starting
19:41:09,065 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.13.GA-redhat-1
19:41:09,070 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.13.GA-redhat-1
19:41:09,070 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
19:41:09,151 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.3.4.Final-redhat-1
19:41:09,166 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013371: Activating Security Subsystem
19:41:09,170 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
19:41:09,171 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
19:41:09,176 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 39) JBAS011800: Activating Naming Subsystem
19:41:09,185 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 46) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
19:41:09,218 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 37) JBAS012615: Activated the following JSF Implementations: [main, 1.2]
19:41:09,232 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013370: Current PicketBox version=4.1.1.Final-redhat-1
19:41:09,242 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
19:41:09,256 INFO [org.jboss.as.connector.logging] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.31.Final-redhat-1)
19:41:09,342 INFO [org.jboss.as.naming] (MSC service thread 1-7) JBAS011802: Starting Naming Service
19:41:09,362 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) JBAS015400: Bound mail session [java:jboss/mail/Default]
19:41:09,802 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-6) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/127.0.0.1:8080
19:41:09,813 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-6) JBWEB003000: Coyote HTTP/1.1 starting on: http-/127.0.0.1:8080
19:41:09,959 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss\jboss-eap-6.4\standalone\deployments
19:41:09,966 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.4.Final-redhat-1
19:41:09,977 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "jenkins.war" (runtime-name: "jenkins.war")
19:41:09,978 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "discover-authoring.war" (runtime-name: "discover-authoring.war")
19:41:09,979 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on 127.0.0.1:4447
19:41:10,004 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
19:41:10,194 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:9999
19:41:10,803 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."discover-authoring.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."discover-authoring.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "discover-authoring.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_73]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_73]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_73]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018014: Failed to parse XML descriptor "/C:/jboss/jboss-eap-6.4/bin/content/discover-authoring.war/WEB-INF/lib/endeca_assembler-3.1.2.jar/META-INF/utils.tld" at [59,9]
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(TldParsingDeploymentProcessor.java:143)
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:122)
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.deploy(TldParsingDeploymentProcessor.java:84)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
... 5 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[59,9]
Message: Unexpected element '{http://java.sun.com/xml/ns/j2ee}info' encountered
at org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109)
at org.jboss.metadata.parser.jsp.TagMetaDataParser.parse(TagMetaDataParser.java:149)
at org.jboss.metadata.parser.jsp.TldMetaDataParser.parse(TldMetaDataParser.java:226)
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(TldParsingDeploymentProcessor.java:141)
... 8 more
Solution:
Going through couple of discussions on jboss developer forum below
https://developer.jboss.org/thread/204217?_sscc=t https://developer.jboss.org/message/913705#913705 https://developer.jboss.org/thread/201358
The problem was with “endeca_assembler-3.1.2.jar/META-INF/utils.tld” file using <info> tag was creating problem for server to load the war correctly.
C:/jboss/jboss-eap-6.4/bin/content/discover-authoring.war/WEB-INF/lib/endeca_assembler-3.1.2.jar/META-INF/utils.tld
Updating <info> tag to <description> tag fix this issues. 
Once you update the tld in jar to use description, build your war again and deploy it to JBOSS and it will work.