OSB HTTP Service Timeout after Enabling Exalogic Optimizations in Weblogic Console
Last updated on NOVEMBER 03, 2016
Applies to:Oracle Service Bus - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
In a fresh installation of OSB 220.127.116.11 on Exalogic, you have created a simple business service that calls a WebService deployed on the same WLS server. This works without issues just as expected.
When enabling the "Exalogic Optimizations" through the WLS console and then restarting both admin and OSB servers, you notice that the business service no longer works: the call to the service hangs and sutk threads appear in the log file. This happens both when testing the business service from the OSB console and when using a WS client such as SoapUI.
If you disable the Exalogic optimizations and restart the servers, the issue no longer arises.
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 hundreds of Community platforms