Hello @davin-fifield-oracle and everyone else on the board - Happy New Year!
I have an interview extension that performs a fetch to a REST API. The REST API is accessible, authorized and there are no CORS issues. This has been checked and tested.
When I use the traditional Mozilla fetch API in my extension :
const requestOptions = {
method: "GET",
headers: myHeaders
};
fetch("https://XXXXXXXX:8433/XXXXX", requestOptions)
.then(function (response) {
let promise = response.json().then(function (json) {
textEl.value = response.status + " " + JSON.stringify(json.items);
interview.setInputValue("interviewResponse", response.status)
});
})
.then((result) => console.log(result))
.catch((error) => console.error(error));
The call is successful and the REST response is received without issue, in the interview. When I use an interview connection and interview.fetch:
var opts = {
connectionName: "CONNECTION_NAME",
relativeUri:"/XXXXXX",
headers: headers, // header creation not shown in the snippet, there is one header
method: "GET"
}
try {
interview.fetch(opts)
.then(function (response) {
let promise = response.json().then(function (json) { … etc.etc.
Then the call is made but there is no response for approximately 2 minutes, and then I see two errors. In the browser console , the response is HTML, which reads :
Weblogic Bridge Message</TITLE>
</HEAD>
<BODY>
<H2>Failure of Web Server bridge:</H2>
<P>
<hr>
No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.<hr>
</BODY>
</HTML>
In the message log of the Oracle Intelligent Advisor Hub, I see "Error fetching data from connection "CONNECTION_NAME on Policy Model "POLICYMODEL:31": Connect to XXXXXX.8433 [/XXXXXX] failed: Connection timed out (Connection timed out), Connection: CONNECTION_NAME, Deployment: POLICYMODEL:31"
If I activate the Debug Log on the interview deployment, I see :
HTTP Request Sent (GET https://XXXX:8433/XXXX)
Interview extension fetch failed (with a copy of the session data which is normal).
Having seen that a Mozilla fetch is successful, I am not sure why the interview fetch is failing. A custom root certificate (valid) is in the Hub, the address is accessible and there are no restrictions. The interview is being accessed directly from a browser, no embedding.
The Hub in question is running 12.2.41.755 - Tuesday, 02 December 2025 04:36. The interview was created using Product Version: 12.2.41.755, Component Version: 63.0.0.20251202051600-b9d4562b5.
Any thoughts as to the difference in behaviour? Could it be something as simple as the port number causing an issue? I've run out of other ideas.
Edit : one other snippet. The certificate chain has a self-signed one in it. Would that cause an issue. I’ve used the same chain to set up Connector API SOAP connections without issue, and as I say it works fine with Mozilla fetch but I felt it pertinent to mention it.
Thanks