JCA Operation Timeout Enhancement To Support Better Timeout Semantics
(Doc ID 2698827.1)
Last updated on AUGUST 13, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management (BRM) 22.214.171.124.0 version, Webservices Mgr & JCA Adaptor
Currently BRM does not have a proper "operation" timeout that one could set to (example to 120s) to match with Siebel. It is impossible to configure that currently because:
- The PcmTimeoutInMs only works on client operations. One can timeout the opcode on the JCA/Siebel side and that will cause the JCA to drop the connection to the CM. But that will not interrupt the BRM operation that is in progress, which could complete its work and then only fail, when it tried to send the response back to the JCA (which had closed the connection).
- The PcmTimeoutInMs on the BRM server side (Connection Manager) is again only a per-request timeout for single operations to the dm_oracle. So setting it to 120s would imply that each and every dm_oracle call could take 120s. It is not something which is cumulative.
- It would be an Enhancement to BRM, if it introduced an additional operation timeout to support better timeout semantics. This would involve having an overall timeout gradually be reduced as operations were performed and the reduced time would be used to timeout lower levels in the stack. This can only be done if operations communicate the remaining time across components. This is causing difficulty while configuring timeouts, it is tricky to do perfectly in the CM, but could be done much better."
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