Manage Groups UI hangs when using RegEx based Rules in Performance Management


Article ID: 194688


Updated On:


CA Infrastructure Management CA Performance Management - Usage and Administration DX NetOps


When doing any of the following using a bad regex expression the UI appears to hang.
  • Group Save
  • Run Rules

It can also be seen when selecting 'Preview Rules'. In that instance it doesn't hang, but does appear to provide no response as if it's doing nothing.

At the same time the following error is observed in the Performance Management Console service logs (PCService.log).

INFO   | jvm 1    | 2020/07/08 15:42:17 | ERROR | qtp1157754522-123933     | 2020-07-08 15:42:17,366 |   
      | Failed to preview rules
org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [INSERT INTO GroupRuleTemp_6469914_2_123933
SELECT ItemID, ItemSubType FROM t_component
WHERE `ItemName` REGEXP '*neiman*' AND 
OwnerItemID IN (SELECT ItemID FROM t_device WHERE ItemID IN (SELECT device_ItemID FROM GroupRuleTemp_6469914_1_123933))]; nested exception is com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Got error 'repetition-operator operand invalid' from regexp
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Got error 'repetition-operator operand invalid' from regexp


Error is triggered by the submission of invalid RegEx expressions in Group Rule configurations.

When that is input using the new non-Flash code it does not recognize and reject the invalid RegEx before it reaches the database.

It is only then that it fails and is caught which generates the log error.

As a result the UI hangs or acts as if it's doing nothing while waiting for a valid response that will never arrive.


Dx NetOps Performance Management r3.7.12


While this is subject to change, a fix is currently scheduled for inclusion in the r3.7.14 release. Defect ID DE469493 will be referenced in the Fixed Issues list for the release it's fix is included in.

Ensure invalid RegEx expressions are caught and rejected before reaching the database.

New code change will be available in a yet to be determined release that will resolve this issue.