Support Article

PegaRULES Server(v5.2) is not getting up in WAS 6.1 server.



The user is upgrading PRPC v5.2 application from WAS 6.0 to WAS 6.1 server. In WAS 6.0 we used Oracle 9i DB . Now in WAS 6.1 they use Oracle 11gR2 as suggested by Pega Architect team, in order to further upgrade the application to PRPC 5.5 Oracle 11gR2 . Now the user is facing PegaRULES server not available error and NameNotFoundException while deploying the prweb.ear in WAS 6.1 server.

Error Messages

  1. W NMSV0612W: A NameNotFoundException occurred on an indirect lookup on the name "java:comp/env/url/pegarules.logging.configuration". The name "java:comp/env/url/pegarules.logging.configuration" maps to a JNDI name in deployment descriptor bindings for the application performing the JNDI lookup. Make sure that the JNDI name mapping in the deployment descriptor binding is correct. If the JNDI name mapping is correct, make sure the target resource can be resolved with the specified name relative to the default initial context. NameNotFoundException data follows:
  2. javax.naming.NameNotFoundException: Context: CLABC_DEVABC_CELPQR/ABC/XXXX, name: url/pegarules.logging.configuration: First component in name pegarules.logging.configuration not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound:]
  3. ERROR - PegaRULES initialization failed. Server: XXXXXXAAB
  4. ERROR - Error creating database instance for Thread

Steps to Reproduce

Deploy the prweb.ear in WAS 6.1 server and launch the application URL.
Check the exceptions in SysOut.logs


Prpc 5.2 will not support Oracle 11g version. PRPC 5.5 will support Oracle 11g version.


Published October 6, 2016 - Updated October 23, 2016

Have a question? Get answers now.

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