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

Upgrade Application Wizard hangs on JBoss 6.3 with Pega 7.1.8

SA-12387

Summary



You run the migration script of Pega (from PRPC 6.2 SP2 to Pega 7.1.8). You login into Designer Studio to complete the upgrade using the wizard (System > Upgrade > Upgrade Existing Applications) and click RUN.

The wizard starts but never ends (even after a complete night of processing). The progress bar stops at 23%. It is run on JBoss 6.3.


Error Messages



Not Applicable

Steps to Reproduce



1. Run the migration script (PRPC 6.2 SP2 to Pega 7.1.8).
2. In Designer Studio, navigate to System > Upgrade > Upgrade Existing Applications and click RUN.


Root Cause



The root cause of this problem is defect/misconfiguration in the operating environment as JBoss 6.3 needs to have some configuration changes to handle more threads.

Resolution



This issue is resolved by making the following change to the operating environment in JBoss config file standalone(-full).xml depending on the one used: 

1. AsyncConnectionFactory definition (defaults to 20 if not set)

<pooled-connection-factory name="AsyncConnectionFactory">
  <min-pool-size>40</min-pool-size>
  <max-pool-size>80</max-pool-size>
  <transaction mode="xa"/>
  <connectors>
    <connector-ref connector-name="in-vm"/>
  </connectors>
  <entries>
    <entry name="java:/jms/PRAsyncTCF"/>
  </entries>
</pooled-connection-factory>


2. Pools definitions

<pools>  
  <bean-instance-pools>  
    <strict-max-pool name="slsb-strict-max-pool" max-pool-size="100" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>  
    <strict-max-pool name="mdb-strict-max-pool" max-pool-size="100" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>  
  </bean-instance-pools>  
</pools>


3. Amend ejb-jar.xml in ear file deployed for PRPC application.

prpc_j2ee14_jboss61JBM/prbeans/META-INF/ejb-jar.xml

4. Add the maxSession ActivationConfigProperty for the MDB deployment descriptor and provide a value that is equal to or
lower than the MDB pool size. Below is an example.

<activation-config-property>  
  <activation-config-property-name>maxSession</activation-config-property-name>  
  <activation-config-property-value>100</activation-config-property-value>  
</activation-config-property>  


This allows more than 15 by default.
Suggest Edit

Published July 23, 2015 - 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