After Upgrading from 188.8.131.52 to 184.108.40.206, OSB Async Web Service Calls are Failing due to, 'Unable to find operation: unknown'
Last updated on JUNE 19, 2016
Applies to:Oracle Service Bus - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
SOA interaction with OSB (Async-callback). You will see binding.ws location which is pointed to the OSB effective wsdl. SOA can invoke the OSB service fine, however, when OSB sends the callback to SOA, SOA is trying to read the wsdl for the callback opertion. Since the OSB effective wsdl no longer contains the callback port type information, it throws the below error.
In 18.104.22.168, the effective wsdl which is generated by OSB includes the port type/binding information from the source wsdl. Therefore, when SOA reads the effective wsdl to find the callback operation, there is no issue. After 22.214.171.124, OSB changed the behavior and only left with the port/port type/binding that is used by the OSB proxy.
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