Oracle Service Bus: With wrong business name dynamic routing uses 382000 in 12c but 382612 in 11g
(Doc ID 2585259.1)
Last updated on OCTOBER 04, 2021
Applies to:Oracle Service Bus - Version 18.104.22.168.0 to 22.214.171.124.0
Information in this document applies to any platform.
On : 126.96.36.199.0 version, OSB Core Functionality
OSB 12 Error handling
Facing a critical functional issue with OSB12. It seems that the error-handling for a dynamic routing is different than it was for OSB11.
When you have implementation of a dynamic routing to another Oracle Service Bus project to avoid static dependencies between the packages and if a package to that a message should be routed, is not present (e.g. as it will be deployed as second project), the message is rolled-back.
In such cases where a dynamic routing failed because of that the referenced package is not available, the Oracle Service Bus 11g used to throw error-code BEA-382612. In Oracle Service Bus 12c this behavior seems to be different, which in such cases responds with BEA-382000 (or OSB-382000).
Error in OSB11:
BEA-382612: Error preparing message for dispatch
Error in OSB12:
BEA-382000: Validation of ServiceMetadataDerivedType PackageNotPresent/ProxyServices/NotExistent.ProxyService failed: ServiceMetadataDerivedType PackageNotPresent/ProxyServices/NotExistent.ProxyService does not exist
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