Last updated on JUNE 02, 2016
Applies to:Oracle SOA Suite - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11gR1 to 11g]
Information in this document applies to any platform.
On : 22.214.171.124.0 version, Core B2B Platform
Messages placed in a remote folder are being picked up by both instances of Oracle which are installed in geographical separate sites and both are in an active-active set up. We are seeing that the same message is being processed by each of Oracle instances from the different sites resulting in duplicate messages. We see that the locking mechanism is not happening here at the FTP server end also. We have a requirement of setting up the instances of oracle B2B in an active-active set up for providing high availability and geographical resilience.
The flow is Remote TP ->B2B->Backend. Remote TP will place the xml in a remote folder which will be polled by different instances of Oracle B2B from different sites and not in the same cluster. Ideally if one oracle B2B instance picks the message , there should be a locking mechanism which prevents the other B2B from picking the same message . Currently what is happening is some messages are being picked by both B2B instances resulting in duplicate messages. We have even set the property b2b.HAInstance to True in both B2B's.
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