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

Pega 7 fails to start after upgrade - name PRAsync not found



After upgrading from PRPC 6.3 SP1 to Pega 7, when attempting to start the JVM, Pega is not initializing. Errors are thrown in the WebSphere SystemOut log file.

Error Messages

[1/27/15 22:37:09:643 CST] 00000016 RALifeCycleMa E J2CA0052E: The lookup of the Activation Specification with JNDI Name eis/PRAsync failed due to the follow
ing exception: javax.naming.NameNotFoundException: Context: cell/clusters/cluster, name: eis/PRAsync: First component in name PRAsync not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound:]

Steps to Reproduce

Upgrade PRPC 6.3 SP1 to Pega 7 then attempt to start the application.

Root Cause

The root cause of this problem is software use/operation error. The prpc_j2ee14.ear deployment file was being used, which is not the correct ear file for a WebSphere deployment.


To resolve this issue, use the prpc_j2ee14_ws.ear file instead. This was created specifically for Websphere and doesn’t utilize PRAsync JMS components.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

100% 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