OSB Project Failed After Applying Oct, 2017 PSU

(Doc ID 2368142.1)

Last updated on MARCH 08, 2018

Applies to:

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

Symptoms

OSB project failed after applying Oct, 2017 PSU

After applying the Oct 2017 PSU (26519424) for WebLogic Server., the OSB Business Service Call failing with Error Message = Failed to get operation name from incoming request.

Following error is seen in the logs:

BEA-380000

Service Ref = xxxx/BizServices/xxxxxx 
 URI = xxxxxxxxxxxxxxxxx 
 Error code = BEA-380000
 Error Message = Failed to get operation name from incoming request
 Message ID = xxxxxxxxxxxxxxxxxxxxxxxx 
 Response metadata =
 <xml-fragment>
<tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">1</tran:response-code>
<tran:response-message xmlns:tran="http://www.bea.com/wli/sb/transports">Failed to get operation name from incoming request</tran:response-message>
<tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">utf-8</tran:encoding>
</xml-fragment>
 Payload =
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/><env:Body><env:Fault xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP-ENV:Client</faultcode><faultstring>Failed to get operation name from incoming request</faultstring></env:Fault></env:Body></env:Envelope>

 

Cause

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