OSB to BPEL Invocation Fails Via Native Binding and t3 Protocol
(Doc ID 850013.1)
Last updated on AUGUST 07, 2018
Applies to:Oracle SOA Platform - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Oracle Service Bus (OSB) Product Information Center > Index Master Note for Oracle Service Bus > Master Note for Troubleshooting Oracle Service Bus Clustered Production Systems > Note 850013.1
When invoking a BPEL process from Oracle Service Bus (OSB), using the native BPEL transport and t3 protocol, as explained in <Note 788141.1>, the following exception is thrown in the OSB console in which the business service is executed:
java.lang.Exception: Failed to create "ejb/collaxa/system/DomainManagerBean" bean; exception reported is: "javax.naming.CommunicationException [Root exception is
weblogic.socket.UnrecoverableConnectException: [Login failed for an unknown reason: HTTP/1.0 501 Not Supported]]
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Oracle Service Bus (OSB) Product Information Center > Index Master Note for Oracle Service Bus > Master Note for Troubleshooting Oracle Service Bus Clustered Production Systems > Note 850013.1|