search cancel

The message "Could not translate alert" is present in the jaws.log

book

Article ID: 240963

calendar_today

Updated On:

Products

Automic Automation Intelligence

Issue/Introduction

The error message shows up in the jaws.log.

 

2022-04-26 19:57:31,327 WARN  [PredictionDataManagerEJB] Could not translate alert: [email protected][id=UUID[AYBncD6-Fz4=],creationTime=2022/04/26 19:54:10.984 UTC,type=JOBSTREAM_EXCEEDED_SLA,[email protected]b60b44[id=UUID[AYBncD5vFzs=],initialJobRunStartTime=2022/04/26 19:54:00.000 UTC,[email protected][id=UUID[AX7bMACXNHk=]],externalId="1651004531999"],scheduler=<null>]: com.termalabs.common.JawsException: Error parsing alert data
    at com.termalabs.server.translate.AlertTranslator.getValues(AlertTranslator.java:141)
    at com.termalabs.server.translate.AlertTranslator.translate(AlertTranslator.java:74)
    at com.termalabs.server.ejb3.PredictionDataManagerEJB.getActiveAndCompletedAlerts(PredictionDataManagerEJB.java:346)
    ... 11 skipped
    at com.termalabs.server.ejb3.RequestScopeEJB3Interceptor.invoke(RequestScopeEJB3Interceptor.java:94)
    ... 68 skipped
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
Caused by: org.xml.sax.SAXParseException; lineNumber: 8; columnNumber: 24; Character reference "&#2" is an invalid XML character.

Cause

The error message in the jaws.log is caused by a special character in the Description of the JobStream.

2022-04-26 19:57:31,327 WARN  [PredictionDataManagerEJB] Could not translate alert: [email protected][id=UUID[AYBncD6-Fz4=],creationTime=2022/04/26 19:54:10.984 UTC,type=JOBSTREAM_EXCEEDED_SLA,[email protected]b60b44[id=UUID[AYBncD5vFzs=],initialJobRunStartTime=2022/04/26 19:54:00.000 UTC,[email protected][id=UUID[AX7bMACXNHk=]],externalId="1651004531999"],scheduler=<null>]: com.termalabs.common.JawsException: Error parsing alert data
    at com.termalabs.server.translate.AlertTranslator.getValues(AlertTranslator.java:141)
    at com.termalabs.server.translate.AlertTranslator.translate(AlertTranslator.java:74)
    at com.termalabs.server.ejb3.PredictionDataManagerEJB.getActiveAndCompletedAlerts(PredictionDataManagerEJB.java:346)
    ... 11 skipped
    at com.termalabs.server.ejb3.RequestScopeEJB3Interceptor.invoke(RequestScopeEJB3Interceptor.java:94)
    ... 68 skipped
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
Caused by: org.xml.sax.SAXParseException; lineNumber: 8; columnNumber: 24; Character reference "&#2" is an invalid XML character.

 

In the Description of the Jobstream, there' a special character in the email address between strings BTA and ETL.

 

 

 

Environment

Release : 6.4.2-1

Component : AAI

Resolution

The Jobstream ID can seen from the log below, which can be used to query the exact name of the jobstream from the JobStream table.

UTC,type=JOBSTREAM_EXCEEDED_SLA,[email protected]b60b44[id=UUID[AYBncD5vFzs=],initialJobRunStartTime=2022/04/26 19:54:00.000 UTC,[email protected][id=UUID[AX7bMACXNHk=]],externalId="1651004531999"],scheduler=<null>]:

 

 

SQL statement to get the name of the jobstream:

select * from JobStream where jobStreamId='AXrFZQlMMkc='

 

From the AAI Amin UI, check the Description of the jobstream and makes sure there's no special character.

 

Attachments