Jump to: navigation, search

log4j2-config-profile

Section: log
Default Value: None
Valid Values: Valid pathname
Changes Take Effect: Immediately
Introduced: 9.0.000.19

The full file pathname of the log4j2.xml configuration file, which is located in the /WebContent/WEB-INF/classes/log4j2.xml file of the application server. If this options is not set, after the server connects to Configuration Server and reads the logging settings, the startup values for the various loggers are lost, resulting in a lot of unnecessary log messages.

9.0.000.26

Genesys Rules System Rules Authoring Tool Release Notes


Genesys Rules System Rules Authoring Tool is part of 9.x starting in 9.0.000.13.
Release Date Release Type Restrictions AIX Linux Solaris Windows
07/23/21 Hot Fix X X

Helpful Links

What's New

This release includes the following new features or enhancements:

  • To prevent possible security vulnerabilities, support for WFM 7-based activities parameters is discontinued. (GRS-3702)

Resolved Issues

This release contains the following resolved issues:


Some decision tables, after being exported to .xls format, and then edited/saved in Excel, could not be reimported. This was due to a misinterpretation of a non-breaking space that Excel was injecting after each column name. This issue is now fixed. (GRS-3710)


Some string parameter values were inadvertently being interpreted as dates due to an error in GRAT code. This issue is fixed. (GRS-3707)


A potential security vulnerability with respect to the Business Structure has been resolved. (GRS-3703)


Repository initialization time has been greatly reduced by eliminating the unnecessary indexing of the system portion of the repository database. (GRS-3685)


The httpclient library has been updated to a newer version to improve security. The existing library contained recently reported vulnerabilities. (GRS-3699)


GRAT has been modified to properly restrict the XML parser during import operations, in order to protect against a possible security vulnerability. (GRS-3696)


A possible XSS vulnerability pertaining to parameters retrieved from an external database has been resolved. (GRS-3694)


Previously, users who opened multiple GRAT tabs could sometimes see erroneous messages related to expired sessions. This issue has been resolved. (GRS-3686)


Internal libraries related to REST have been upgraded in this release in order to prevent reported security vulnerabilities in the older libraries. (GRS-3283)


GRAT upgraded the logging libraries to log4j2 due to known vulnerabilities in log4j1.2 versions. You will need to make some logging-related configuration changes before deploying this version. See the GRE log4j2-config-profile option for details. (GRS-3271)


Upgrade Notes

See GRS-3271.

This page was last edited on August 3, 2021, at 16:01.
blog comments powered by Disqus