Updated DVM Values not Reflected after DVM Deployment
Last updated on DECEMBER 18, 2017
Applies to:Oracle SOA Suite - Version 184.108.40.206.8 and later
Information in this document applies to any platform.
On : 220.127.116.11.8 version, Fabric
Multiple messages are sent after a DVM file is updated in the MDS with new values. The outbound messages reflect both the updated DVM value and the old DVM value.
Even the following scenarios do not change the outcome:
1) Redeploying the composite.
2) Clearing the MDS cache.
However, if the DVM file name is changed, along with its references in the composite and XSLT, after redeploying the composite the new DVM values are reflected in outbound messages.
This is not expected behavior. Only the updated DVM values should be reflected in the outbound message.
The issue can be reproduced at will with the following steps:
1. Deployed DVM with new values.
2. Sent twenty of the same message with .5 seconds interval with both servers running.
3. Only about 60% of the outbound messages have the new DVM values.
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