ServiceNow-Jira Integration Issue

Originally asked by Shruthi on 20 April 2021 (original question)


Hello Team,

ServiceNow Requests are not getting synchronized and they are being stuck in the sync queue. The following error being displayed when we try to sync up.

" JsResultException(errors:List(((4853),List(JsonValidationError(List(error.expected.jsobject),WrappedArray())))))"

We did take a look at the logs but unfortunately we could not find any potential leads. Yet we could find the below error but that did not help in identify the issue.

ā€œservices.ScriptExceptionCategoryService.categorizeProcessorAndIssueTrackerExceptionsIntoScriptExceptions(ScriptExceptionCategoryService.scala:34)ā€

Thanks,

Shruthi


Answer by Francis Martens (Exalate) on 21 April 2021

Can you provide

  • The whole stack trace of the error
  • The corresponding script

Comments:

Shruthi commented on 21 April 2021

Hello Francis,

2021-04-20 09:09:57,281 [ERROR] from application.services.replication.request.RequestProcessorService in application-akka.actor.default-dispatcher-11 - Exception occurred while processing sync request ID `3415`, remote event `2891` number `1` for remote issue urn `ITC-2072`, connection `DEV SN SR_to_DEV JIRA SR`.
com.exalate.api.exception.script.ScriptException: JsResultException(errors:List(((4154),List(JsonValidationError(List(error.expected.jsobject),WrappedArray())))))
at com.exalate.error.services.ScriptExceptionCategoryService.categorizeProcessorAndIssueTrackerExceptionsIntoScriptExceptions(ScriptExceptionCategoryService.scala:34)
at com.exalate.processor.ExalateProcessor.executeProcessor(ExalateProcessor.java:47)
at com.exalate.replication.services.processor.CreateIssueProcessor.$anonfun$executeScriptRules$1(CreateIssueProcessor.scala:104)
at scala.util.Try$.apply(Try.scala:213)
at com.exalate.replication.services.processor.CreateIssueProcessor.executeScriptRules(CreateIssueProcessor.scala:101)
at com.exalate.replication.services.processor.CreateIssueProcessor.createIssue(CreateIssueProcessor.scala:78)
at com.exalate.replication.services.replication.request.CreateIssueSyncRequestState.transition(CreateIssueSyncRequestState.scala:36)
at com.exalate.replication.services.replication.request.CreateIssueSyncRequestState.transition(CreateIssueSyncRequestState.scala:21)
at com.exalate.replication.services.replication.in.RequestProcessorService.$anonfun$processSyncRequest$2(RequestProcessorService.scala:172)
at scala.util.Try$.apply(Try.scala:213)
at com.exalate.replication.services.replication.in.RequestProcessorService.processSyncRequest(RequestProcessorService.scala:149)
at com.exalate.replication.services.replication.in.RequestProcessorService.$anonfun$processSyncRequestsForIssue$1(RequestProcessorService.scala:99)
at com.exalate.replication.services.replication.in.RequestProcessorService.$anonfun$processSyncRequestsForIssue$1$adapted(RequestProcessorService.scala:98)
at scala.collection.LinearSeqOptimized.foldLeft(LinearSeqOptimized.scala:126)
at scala.collection.LinearSeqOptimized.foldLeft$(LinearSeqOptimized.scala:122)
at scala.collection.immutable.List.foldLeft(List.scala:91)
at com.exalate.replication.services.replication.in.RequestProcessorService.processSyncRequestsForIssue(RequestProcessorService.scala:98)

Dev connection - DEV SN SR_to_DEV JIRA SR

Jira Request - ITC-2074

Please let me know if you need any additional details.

Thank you.

Francis Martens (Exalate) commented on 21 April 2021

The exception is raised by ā€˜JsonValidationErrorā€™

Can you check what the incoming replica is looking like and identify why the json is wrong