My Oracle Support Banner

REST Adapter Fault Response Mapping Failure Results In Stuck Thread (Doc ID 2285859.1)

Last updated on FEBRUARY 27, 2018

Applies to:

Oracle Service Bus - Version and later
Information in this document applies to any platform.


On : version, OSB Core Functionality

REST Adapter fault response mapping failure results in stuck thread

In attached logfile osb_server2.out00100 we see the following error message occurring at :

Translation Failure.
Failed to translate JSON to XML. Cannot find schema type for /IbanCheck_ErrorReply/requestId Should not come here
The incoming data does not conform to the NXSD schema. Please correct the problem.

We know that the fault is being caused by an incorrect JSON response (not according to corresponding XSD).
However, this results in a stuck thread (response is not delivered to pipeline-thread).
Taken from the same logfile osb_server2.out00100:
<[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "610" seconds working on the request "Workmanager: _WM_Proxy, Version: 0, Scheduled=true, Started=true, Started time: 610590 ms
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:


The issue can be reproduced at will with the following steps:

The issue has the following business imp




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

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