Concerning the significant increase in logs following GW 11.1.2

Products

• CA API Gateway

Issue/Introduction

We wish to inform you that there has been a significant increase in the logs following the upgrade to GW 11.1.2. The GW 11.1.2 upgrade poses a critical issue for the live environment due to these instabilities. We kindly request you to review the situation and recommend the next steps to take. We have upgraded the JSON Path Expression (V2) and last log is no more present.

gateway:11.1.2_20250630

Below are the few examples of logs.
Occurences- 12,337,212 (This log is present with container gateway image gateway:11.1.2_20250630. It specific to GW 11.1.2)
"com.l7tech.external.assertions.evaluatejsonpathexpressionv2.server.ServerEvaluateJsonPathExpressionV2Assertion"
Invalid target message, variable "${circuitBreakerConfiguration}": The variable "circuitBreakerConfiguration" could not be found.

com.l7tech.external.assertions.keyvaluestore.server.ServerKeyValueStorageAssertion
The length of the key is '265', which exceeds the maximum allowed length of 256 characters

Error occurred evaluating JSON Path: 'Payload cannot be empty'
com.l7tech.external.assertions.evaluatejsonpathexpressionv2.server.ServerEvaluateJsonPathExpressionV2Assertion

Evaluate JSON Path Expression (V1) assertion is deprecated and will be removed in future Gateway releases. Users of this assertion are encouraged to use enhanced Evaluate JSON Path Expression (V2) assertion instead.

Environment

11.1.2

Resolution

com.l7tech.external.assertions.evaluatejsonpathexpressionv2.server.ServerEvaluateJsonPathExpressionV2Assertion"
Invalid target message, variable "${circuitBreakerConfiguration}": The variable "circuitBreakerConfiguration" could not be found.

Is not directly related to the JSONv2 assertion or to the circuitBreakerConfiguration. It says that the evaluatejsonpathexpressionv2  assertion is referencing a non existing variable called circuitBreakerConfiguration.

Indicating there is a problem in the policy which should be checked. 

Reproducing this error the message looks like below.

2025-09-29T12:38:06.350+0000 INFO    291  com.l7tech.external.assertions.evaluatejsonpathexpressionv2.server.ServerEvaluateJsonPathExpressionV2Assertion: 4330: Invalid target message, variable "${NONEXISTINGVAR}": The variable "NONEXISTINGVAR" could not be found.

The 4330 is the audit event code for this message .

You can suppress this message by setting the following cwp 

cwp audit.auditDetailExcludeList  value 4330 

After this this message's with id 4330 are  not logged at all .

This could also be other message's related to this event type like