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

Failure of generation of output file

SA-22723

Summary



The template remains in the status "In Progress" and cannot be finalized when running an outbound marketing campaign that writes to a file.

Error Messages




Steps to Reproduce



1. Run outbound marketing program. Program run is successful but the generation of the output template file is not produced on the file system. However lock files are produced.
2. Try to finalize it on the GUI.

Root Cause



A defect or configuration issue in the operating environment.

Resolution



1. Stop or remove the now-processing hung queue item from System Management Application (SMA).
2. Stop all PRPC nodes.
3. Clear the outbound staging table.
4. In JBOSS standalone-full.xml configuration file, under subsystem "urn:jboss:domain:ejb3:1.5" update "mdb-strict-max-pool" size to 100.


<mdb>
<resource-adapter-ref resource-adapter-name="${ejb.resource-adapter-name:hornetq-ra}"/>
<bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>
</mdb>
<pools>
<bean-instance-pools>
<strict-max-pool name="slsb-strict-max-pool" max-pool-size="20" 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>


5. Within the prpc_j2ee14_jboss61JBM.ear - assuming the ear file is used - extract the ejb-jar.xml from prbeans.jar\META-INF folder (prpc_j2ee14_jboss61JBM.ear\prbeans.jar\META-INF\), and add the following red highlighted lines to “PRAsync” EJB to set the maxsessions value.
<message-driven>
<ejb-name>PRAsync</ejb-name>
<ejb-class>com.pega.pegarules.internal.etier.mdb.PRAsyncBoot</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Bean</transaction-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>destinationType</activation-config-property-name>
<activation-config-property-value>javax.jms.Topic</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>destination</activation-config-property-name>
<activation-config-property-value>java:/topic/jms/PRAsyncTopic</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>maxSession</activation-config-property-name>
<activation-config-property-value>100</activation-config-property-value>
</activation-config-property>
</activation-config>
</message-driven>

6. Update the prpc_j2ee14_jboss61JBM.ear file with the modified ejb-jar.xml and prbeans.jar, and redeploy the prpc_j2ee14_jboss61JBM.ear file. Remove all traces of old deployment like the work folder.
7. Rerun tests.
Suggest Edit

Published August 23, 2017 - Updated December 2, 2021

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