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

Default Paths are not getting loaded

SA-35170

Summary



Classes from jar files defined in the path Settings >Compiler >Default path landing page is not loading by PRPC class loader.

Error Messages



Failed t
o get setting with key: "compiler/defaultClasses" and owning ruleset: "Pega-RULES". PegaRULES database context is not available.
Failed to get setting with key: "compiler/defaultPaths" and owning ruleset: "Pega-RULES". PegaRULES database context is not available.


Steps to Reproduce

  1. Add list of jars in Setting >Compiler > Default Path landing page separated by semicolon (;).
  2. Invoke the functionality that uses class in jar file mentioned in above step.


Root Cause



While starting of the system, no external jar files were getting read by class loader as it was not able to read the class path correctly.

Resolution



In compiler settings in Systems settings landing page Default Paths value is given with ";" separated between jars.

At engine value is being read and tokenized based on System property "path.separator". In Windows "path.separator" is ; but in Unix "path.separator" is :.

From the logs, it is found that customer is on Linux machine.

Make the change in the Default Paths value, to give multiple jars with : separated.

The path separator for separating multiple path in Default path setting must be according to environment where PRPC is running.

For Windows platform the separator should be semicolon and for Linux / Unix it should be colon (:)

Suggest Edit

Published April 11, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

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.

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