Not Able To Start Schedule Through REST API Results Error "HTTP 400 Bad Request" (Doc ID 2893329.1)

Last updated on DECEMBER 03, 2022

Applies to:

Symptoms

On : 21.2.2.0.0 version, Rest Adapter

Calling REST API to start schedule (https://doicis0100integrationservices-atcoci1.integration.ocp.oraclecloud.com/ic/api/integration/v1/integrations/WFD05_SCHEDULER_TEST%7C01.00.0000/schedule/start) fails with error.

ERROR
-----------------------

  "detail": "javax.xml.bind.UnmarshalException\n - with linked exception:\n[Exception [EclipseLink-25004] (Eclipse Persistence Services - 2.6.7.v20190604-418f1a1c56): org.eclipse.persistence.exceptions.XMLMarshalException\nException Description: An error occurred unmarshalling the document\nInternal Exception: javax.json.JsonException: Cannot auto-detect encoding, not enough chars]; \nException Description: An error occurred unmarshalling the document\nInternal Exception: javax.json.JsonException: Cannot auto-detect encoding, not enough chars; Cannot auto-detect encoding, not enough chars",
  "status": "HTTP 500 Internal Server Error",
  "title": "HTTP 400 Bad Request",
  "type": "https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5.1"


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Invoke REST API to start schedule

 

Cause

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