OBLM - EOD FAILED | URI IS NOT ABSOLUTE (Doc ID 3040892.1)

Last updated on AUGUST 12, 2024

Applies to:

Symptoms

OBLM - EOD is failed.

For Branch abc , user has configured OBLM-EOC-2 Group workflow. Upon Triggering the EOD, system has started the process but failed at IC.MARKCUTOFF


ERROR
-----------------------
class EodTaskDTO {
  taskType: HTTP
  status: FAILED
  referenceTaskName: IC.MARKCUTOFF
  retryCount: 0
  seq: 6
  correlationId: asdfghjkl
  pollCount: 1
  taskDefName: IC.MARKCUTOFF
  scheduledTime: xxxxxxxxxxxxxxxxxx
  startTime: xxxxxxxxxxxxxxxxxx
  endTime: xxxxxxxxxxxxxxxxxx
  updateTime: xxxxxxxxxxxxxxxxxx
  workflowInstanceId: 4184073c-2223-4c17-914e-b6bc19d58b18
  workflowType: OBLM-EOC-2
  taskId: be95b45e-7b94-4300-a9c3-1a8159b003bb
  reasonForIncompletion: Failed to invoke http task due to: java.lang.Exception: java.lang.IllegalArgumentException: URI is not absolute
  taskStatus: FAILED
  outputData: class TaskOutputDataDTO {
  subWorkflowId: null
  }



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Workflow for OBLM-EOC-2 is uploaded.
2.Configured the OBLM EOD for abc branch
3.Invoked the EOD for abc branch.
4.EOD is failed



BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot completely run OBLM-EOC-2 Group

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.