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

Unable to specify JNDI setting for prlogging configuration file

SA-16465

Summary



When trying to override the prlogging configuration file with an external file using the JNDI reference, the reference is not being properly picked up. The URL setting is being properly bound in the environment:

    WSVR0049I: Binding prlogging as url/pegarules.logging.configuration

However, the PegaRULES engine still reports the default logging configuration file is being used:


    located PegaRULES logging configuration: wsjar:file:/your_path/to/prlogging.xml


Error Messages



SystemOut_15.11.04_08.38.22.log:[11/4/15 8:36:43:301 EST] 00000001 ResourceMgrIm I WSVR0049I: Binding prlogging as url/pegarules.logging.configuration
SystemOut_15.11.04_08.38.22.log:[11/4/15 8:36:54:313 EST] 00000074 SystemOut O Located PegaRULES logging configuration: wsjar:file:/your_path/to/prlogging.xml


Steps to Reproduce

  1. Set the value of the 'url/pegarules.logging.configuration' resource reference. 
  2. Observer Pega engine behavior.


Root Cause



The JNDI name needs to be set in three different locations for the Pega application. For the EngineCMT and EngineBMT beans, as well as for the prweb.war module.

Resolution



Perform the following local-change: Ensure the resource reference is made for all three Pega application layers.

 

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

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