Advanced Search with backslash in Object Contents caused exception and/or matching objects were not found

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

If an advanced search is executed that browses for the presence of backslash character "\" in the object content at the end of the phrase (e.x. UNC path), AWI returns a popup with a java stack error the JCP throws a forced trace.

AWI error:

The AWI search API could not respond to you request

The JCP log file contains the following:

20210309/154202.146 - 39   U00045014 Exception 'org.apache.lucene.queryparser.classic.ParseException: "Cannot parse '((granularity:OBJECT) AND (client:22) AND (isLink:false) AND ((scriptAll:"\" OR scriptAll:*\\*) OR (title:"\" OR title:*\\*) OR (documentation:"\" OR documentation:*\\*) OR (archiveKey1:"\" OR archiveKey1:*\\* OR archiveKey2:"\" OR archiveKey2:*\\*) OR (agent:"\" OR agent:*\\*) OR (login:"\" OR login:*\\*))) AND (((aclPath:*)) OR aclPath:\\<NOFOLDER>)': Lexical error at line 1, column 354. Encountered: <EOF> after : "\"\\\" OR login:*\\\\*))) AND (((aclPath:*)) OR aclPath:\\\\<NOFOLDER>)""' at 'org.apache.lucene.queryparser.classic.QueryParserBase.parse():122'.

20210309/154202.147 - 39   U00045015 The previous error was caused by 'org.apache.lucene.queryparser.classic.TokenMgrError: "Lexical error at line 1, column 354. Encountered: <EOF> after : "\"\\\" OR login:*\\\\*))) AND (((aclPath:*)) OR aclPath:\\\\<NOFOLDER>)""' at 'org.apache.lucene.queryparser.classic.QueryParserTokenManager.getNextToken():1130'.

 

Environment

Release : 12.3.X One Automation

 

Cause

Defect

Resolution

A problem has been fixed where Advanced Search for backslash in Object Contents caused exception and/or matching objects were not found.

Please upgrade to one of the following versions of Automation Engine: 

Automation.Engine 21.0.0 - planned release 2021-09-30

Automation.Engine 12.3.6 - planned release 2021-06-28