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

Error deploying prpc_j2ee14_jboss61JBM.ear on jboss eap 6.3 jvm

SA-8887

Summary



User getting the below error when deploying prpc_j2ee14_jboss61JBM.ear on jboss eap 6.3 jvm using Pega 7.1.7. Below is the complete stack trace error while starting the jvm.

2015-03-05 17:11:11,080ERROR(MSC service thread 1-6)MSC000001: Failed to start service jboss.deployment.subunit."prweb.ear"."prbeans.jar".PARSE: org.jboss.msc.service.StartException in service jbos
s.deployment.subunit."prweb.ear"."prbeans.jar".PARSE: JBAS018733: Failed to process phase PARSE of subdeployment "prbeans.jar" of deployment "prweb.ear"

Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found
2015-03-05 17:11:11,151INFO (ServerService Thread Pool -- 26)JBAS018559: Deployed "prweb.ear" (runtime-name : "prweb.ear")
2015-03-05 17:11:11,154INFO (Controller Boot Thread)JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.subunit."prweb.ear"."prbeans.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."prweb.

ear"."prbeans.jar".PARSE: JBAS018733: Failed to process phase PARSE of subdeployment "prbeans.jar" of deployment "prweb.ear"


Error Messages



Failed to start service jboss.deployment.subunit."prweb.ear"."prbeans.jar".PARSE: org.jboss.msc.service.StartException in service jbos
s.deployment.subunit."prweb.ear"."prbeans.jar".PARSE: JBAS018733: Failed to process phase PARSE of subdeployment "prbeans.jar" of deployment "prweb.ear"


Steps to Reproduce



1. Install prpc 7.1.7.
2. Install eap 6.3 jvm.
3. Deploy prpc_j2ee14_jboss61JBM.ear


Root Cause



The root cause of this problem is an error/omission in product documentation. As per our platform support guide for 7.1.7 (https://pdn.pega.com/documents/platform-support-guide ) the JBoss 6.3 Installation Guide or instructions are still work under progress and have not been released for GA. It will be available on the PDN shortly.


Resolution



This issue is resolved through the following Local-change: 


Advised user to use the following instructions –
 
For deploying the PRPC EAR in JBoss 6.3.x perform the following steps –
 
  1. Instead of using standalone.xml use the standalone-full.xml to configure the naming and datasources subsystem configurations that you already have in standalone.xml.
  2. In addition add the following JMS TCF configuration under the messaging subsystem –
 
Add JMS Connection Factory, under
<subsystem xmlns="urn:jboss:domain:messaging:1.">:

 
  •  
<pooled-connection-factory name="AsyncConnectionFactory">
                        <transaction mode="xa"/>
                        <connectors>
                            <connector-ref connector-name="in-vm"/>
                        </connectors>
                        <entries>
                            <entry name="java:/jms/PRAsyncTCF"/>
                        </entries>
               </pooled-connection-factory>

 
  1. In standalone.conf bootstrap config script add the following as the last line:
JAVA_OPTS="$JAVA_OPTS -Djboss.as.management.blocking.timeout=600"
 
  1. Restart JBoss specifying the standalone-full.xml configuration file mentioned as below:
 
$JBOSS_HOME/bin/standalone.sh --server-config=standalone-full.xml

 
  1. Login to the JBoss management console app and deploy the prpc_j2ee14_jboss61JBM.EAR. 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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