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

Need JVM restart to see exposed properties on clipboard

SA-15545

Summary



When a new deployment adds additional property rules and those properties are exposed in the database by running DDL directly to create the columns, the properties do not appear on the clipboard until all of the JVMs are restarted in Pega 7.1.2. 


Error Messages



Not Applicable.


Steps to Reproduce

  1. Run DDL on the database to create the columns for the new properties.
  2. Import the jar file containing the new properties.


Root Cause



This is expected system behavior.
The Pega engine reads database metadata that is - the structure of all objects for example table, procedures, views, and so on, which is again visible in the Pega schemas, on engine initialization only. Pega engine caches this information and references it for the duration of the engine uptime.

It does not re-read database object metadata for performance reasons. Thus, if the database structure has changed during runtime by an import or direct DDL, an engine restart is necessary.

Resolution



Restart your JVM to force the Pega engine to read new metadata from the database, including all table and view changes.

 

Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

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