Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Application server setup fail



You are installing Pega 7.1.7 on JBoss 6.1 on linux platform and seeing prweb deployment issues in jboss server log

Operating System - Red Hat Linux 6.4 x64 Bit
Database - Oracle 12c
Java JDK version - 1.7.0_71
Product - Pega 7.1.7
Application Web server - JBoss Enterprise Application Platform - Version 6.1.0.GA

Error Messages

14:46:11,733 INFO [] (MSC service thread 1-2) JBAS015876: Starting deployment of "prweb.war" (runtime-name: "prweb.war")
14:46:11,889 ERROR [] (MSC service thread 1-8) MSC000001: Failed to start service jboss.module.service."deployment.prweb.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.prweb.war".main: JBAS018759: Failed to load module: deployment.prweb.war:main
at [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService( [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$ [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker( [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor$ [rt.jar:1.7.0_71]
at [rt.jar:1.7.0_71]
Caused by: org.jboss.modules.ModuleLoadException: Error loading module from /pega/jboss-eap-6.1/modules/system/layers/base/com/oracle/main/module.xml
at org.jboss.modules.ModuleXmlParser.parseModuleXml( [jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.ModuleXmlParser.parseModuleXml( [jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.LocalModuleFinder$ [jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.LocalModuleFinder$ [jboss-modules.jar:1.2.0.Final-redhat-1]
at Method) [rt.jar:1.7.0_71]
at org.jboss.modules.LocalModuleFinder.findModule( [jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.ModuleLoader.findModule( [jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.ModuleLoader.loadModuleLocal( [jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.ModuleLoader.preloadModule( [jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.Module.addPaths( [jboss-modules.jar:1.2.0.Final-redhat-1]
at [jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.Module.relinkIfNecessary( [jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.ModuleLoader.loadModule( [jboss-modules.jar:1.2.0.Final-redhat-1]
at [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
... 5 more
Caused by: ParseError at [row,col]:[6,99]
Message: Unexpected content of type 'element start' named '{urn:jboss:module:1.1}resources-root'
at org.jboss.modules.ModuleXmlParser.unexpectedContent( [jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.ModuleXmlParser.parseResources( [jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.ModuleXmlParser.parseModuleContents( [jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.ModuleXmlParser.parseDocument( [jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.ModuleXmlParser.parseModuleXml( [jboss-modules.jar:1.2.0.Final-redhat-1]
... 18 more

Steps to Reproduce

Following installation guide - PRPC71_Install_JASORA Page-42

Root Cause

The root cause of this problem is a defect in customer application code/rules. There might be i
nvalid characters in the xml that parser is complaining about. 


This issue is resolved through the following local change:
Copy the sample file available in JBoss installation under


And modify its contents to reflect your oracle driver module name and path etc.

This module.xml is for Mssql  but you can change the values in it to match Oracle. You can put the driver path as <resource-root path ="ojdbc7.jar"/> if the jar is located in the same location as the module.xml

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us