Question
CENTENE Corporation
US
Last activity: 20 Mar 2018 15:31 EDT
Externalization of prconfig/prlogging xml files is no longer working after upgrade to v7.3.x
Hello,
We recently upgraded from v7.1.8 to v7.3.1, and have found that the JVM arguments/JAVA_OPTS that have worked in the past to utilize external config files, are no longer working as expected. PEGA logs are no longer being written to the specified locations within prlogging.xml file, and the 'pegatmp' directory defined in prconfig.xml remains empty. How do we get these args/JAVA_OPTS working again, as we had before with v7.1.8?
Example of -D JAVA_OPTS that worked as expected in lower version (v7.1.8):
JAVA_OPTS="$JAVA_OPTS -Dpegarules.logging.configuration=/opt/projects/pega/prlogging.xml"
JAVA_OPTS="$JAVA_OPTS -Dpegarules.config=/opt/projects/pega/prconfig.xml"
***Edited by Moderator Marissa to update categories; add SR Details***
Accepted Solution
CENTENE Corporation
US
**UPDATE**
The SR is still being reviewed/investigated, as we await a V7.3.1 JBOSS container to be built by PEGA Support team on their side. However, I was able to discover that upon launching our new v7.3.1 instance in a DOMAIN MODE configuration, the external prconfig.xml and prlog4j2.xml files are now being picked up and utilized as expected! There is still a bug with running STANDALONE MODE for some reason, but we were planning to move to a domain configuration in the near future, so it works well for us. Thanks again for all who took the time to assist.
====================================================================
Version of JBOSS EAP when running in standalone mode configuration: 6.3.3
Version updated to and now running in domain mode configuratoin: 6.4.19
Oracle JDK: 1.8.0_162
OS: RHEL 6.9
Pegasystems Inc.
US
Prlogging.xml is probably not working because it's no longer used as of 7.3. The new file is prlog4j2.xml and you will need to customize and externalize this instead (do not just copy the contents from your existing prlogging.xml file, this will not work).
As for prconfig.xml, it sounds like you believe it's not being used because that is where you have defined the pega temp directory and nothing is being written there. What application server is in use? There should be another area to specify where the Pega temp directory is. (For example, in context.xml for Tomcat)
CENTENE Corporation
US
I agree with the prlogging.xml being replaced in 7.3.x, as I read this during my research and review of deployment guides this morning. However, the java argument for prconfig.xml should not be ignored. Thanks for that!
Updated: 22 Feb 2018 16:07 EST
CENTENE Corporation
US
explicittempdir otherwise known as 'pegatmp' is defined within prconfig.xml. During startup, I see that it is found at the static path I have configured with my java arg shown above. Afterwards, it is ignored, and the default one packaged within ear file for prpc takes over. Please see log entries below for review, this appears to a bug of some sort within 7.3.1:
^[[0m^[[0m13:41:40,750 INFO [stdout] (xx) Found spec for PegaRULES configuration using System property: /opt/projects/pega/prconfig.xml
^[[0m^[[0m13:41:40,801 INFO [stdout] (xx) Located PegaRULES configuration: pegajdbc://669771319:0/prresources.jar!//prconfig.xml
Pegasystems Inc.
US
As you've noted, it sounds like that may be a bug in which case you'll need to enter an SR. Let us know the SR number here after you submit it.
Accepted Solution
CENTENE Corporation
US
**UPDATE**
The SR is still being reviewed/investigated, as we await a V7.3.1 JBOSS container to be built by PEGA Support team on their side. However, I was able to discover that upon launching our new v7.3.1 instance in a DOMAIN MODE configuration, the external prconfig.xml and prlog4j2.xml files are now being picked up and utilized as expected! There is still a bug with running STANDALONE MODE for some reason, but we were planning to move to a domain configuration in the near future, so it works well for us. Thanks again for all who took the time to assist.
====================================================================
Version of JBOSS EAP when running in standalone mode configuration: 6.3.3
Version updated to and now running in domain mode configuratoin: 6.4.19
Oracle JDK: 1.8.0_162
OS: RHEL 6.9