"Failed to parse source" Problem starting webapp when migrating from 4.2.1GA to 5.1 EAS

[rajaswin07]

Hello,  I am migrating from JBOSS 4.2.1 GA to JBOSS 5.1 EAP.  I have spent an unbelievable amount of time on this.  Our app use web_app 2.3 dtd and works fine in JBOSS 4.2.1.  However it appears that 5.1 EAP requires that we declare namespaces and I figured I would as well migrate to web_app 2.5 namespace.  I made many changes to the web.xml to confirm to 2.5 namespace.  It looks like I have fixed all the issues in web.xml.  However our app does not start up.  I am frustrated that the error message is not descriptive enough.  All I see is the following error which tells me nothing.  Searching on the internet or in the forums has been useless.  Any help will be much much appreciated. 

2013-07-23 15:43:11,472 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Parse: name=vfsfile:/C:/pgfiles/jboss-eap-5.1/jboss-as/server/default/deploy/idm.war/ state=PreParse mode=Manual requiredState=Parse

org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/C:/pgfiles/jboss-eap-5.1/jboss-as/server/default/deploy/idm.war/

at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)

at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:362)

at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:322)

at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:294)

at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:234)

at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)

at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)

at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)

at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)

at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)

at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)

at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)

at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)

at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)

at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)

at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)

at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)

at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)

at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)

at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403)

at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)

at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)

at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)

at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)

at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)

at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308)

at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256)

at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)

at org.jboss.Main.boot(Main.java:221)

at org.jboss.Main$1.run(Main.java:556)

at java.lang.Thread.run(Thread.java:662)

Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Element {http://java.sun.com/xml/ns/j2ee}ejb-jar is not bound as a global element.

at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)

at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)

at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:189)

at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:166)

at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137)

at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121)

at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:304)

at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:286)

at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:203)

at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:348)

... 33 more

Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Element {http://java.sun.com/xml/ns/j2ee}ejb-jar is not bound as a global element.

at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:660)

at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)

at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)

at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)

at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)

at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)

at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)

at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)

at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)

at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)

at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)

at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

... 42 more

[rajaswin07]

Can anyone help me?  Even if I am doing something stupid can someone please point me in the right direction?  Is there a flag that I can turn on to get more diagnostic information?  That would be a big help.  Thank you

[peterj]

Usually the error message is kind enought to tell you which XML file is being parsed that it does not like. But I suspect that one of your XML config files has an <ejb-jar> element out of place, Scan the XML files in your idm.war to find the offending <ejb-jar> element. AS 5.x and later are more picky about XML files being correctly formed - XML files that were acceptable in 4.2.x and earlier but not syntactically correct will not work in 5.x and later. If you are not sure how to fix the issue, post the offending XML file here.

[rajaswin07]

Thanks Peter for taking the time to respond.

If I knew the offending xml I would have fixed it by now.  If you see the error message you will notice that the name of the xml file is not mentioned and that is the source of my frustration.  If there is someone from the JBOSS server team perhaps they can tell me how to enhance logging so that I figure out what xml file is causing the issue.

Also we dont use EJB's.

Thanks again

[peterj]

You don't have a tool to search all of your xml files for specific text? Try Notepad++, it has a convenient "find in files" capability. Of course you will need to unpack the WAR file first before Noetpad++ can access the xml files.

The server.log contains debug logging statements, if it doesn't list the xml file name, then there isn't any logging configuration that will display the name.

[rajaswin07]

Hello Peter,  I have grepped through the entire war file and found one reference to ejb-jar and that too in the comments section.

We use log4j for our logging configuration.

Also this WAR file works jsut fine in 4.2.1.  In 5.1 EAS we have the issue noted above.

Thoughts?

[peterj]

I dug through the DTDs and XSDs and the only reference I saw to ejb-jar was for the ejb-jar.xml file. And you said you aren't using EJBs so you would not have that file. So the error has me stumped.

My next step would be to get the sources and look at the lines mentioned in the stack trace to see if that gives any clues. If it didn't I would add some logging statements to print out the XML file being parsed and rebuild the AS and try again.

[rajaswin07]

Thank you again Peter.  Let me muck around and see what I determine.