Error parsing jboss-ejb3.xml during deployment after upgrade to EAP 6.4

Solution Verified - Updated -


  • jboss-ejb3.xml parse error during deployment after upgrade to JBoss 6.4.5 from Jboss 6.2.0
ERROR [] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."example.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."example.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "example.war"
        at [jboss-as-server-7.5.5.Final-redhat-3.jar:7.5.5.Final-redhat-3]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService( [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
Caused by: JBAS014185: Exception while parsing jboss-ejb3.xml: /example.war/WEB-INF/jboss-ejb3.xml
Caused by: ParseError at [row,col]:[33,13]
Message: Unexpected element '{}ejb-name' encountered
  • Why there is a parsing error if I upgrade to EAP 6.4.x or later?
  • The jboss-ejb3.xml marked muliple EJB's as clustered but it seems not all are handled correct


  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In