Does Configuration for Coherence And HeartBeats Suggested In OCSB5 Are Necessary When Using In OCCAS-SC6.1
(Doc ID 1588302.1)
Last updated on FEBRUARY 20, 2019
Applies to:Oracle Communications Converged Application Server - Service Controller - Version 6.1.0 and later
Information in this document applies to any platform.
In OCSB5 there were some configuration that suggested avoiding coherence and HB (heartbeats) issues.
Does three of the suggestions need to be set or is necessary using OCCAS-SC 6.1?
1. Setting "response timeout" and "inactive interval" at least 32 seconds.
If using UDP for the heartbeat between SSU SIP and AS it makes sense to set 'response timeout' and 'inactive interval' at least 32 seconds.
The 'active interval' can be the present value at it is.
By using this directive, a recommended SIP network entity configuration looked like the following in OCSB5:
Active interval: 9s
Inactive interval: 32s
In OCCAS-SC 6.1, one of the advice was to use Response Timeout less than or equal to the minimum of Inactive Interval and Active Interval.
In this case the 32-9-32 setting for response-active-inactive parameters is not possible.
These settings CANNOT be set in OCCAS-SC 6.1, see "Document 1584006.1: FrameworkConfigurationException When Setting SIP Network Entity's Heartbeat Timeout And Interval"
In case that using -Dwlss.udp.mtu=9000 so we can stick to UDP.
Please clarify what timeout values should be used here if continue to use UDP.
What is the desired setting for timeout-active-inactive settings in SIP Network Entities? Is this related to coherence, since when had coherence problems, the recommended was to use 32-9-32 settings.
2. One more suggested was some additions to tangosol-coherence-override.xml:
(note that 4192608=2936*1428)
You do not recommend applying the modifications in tangosol-coherence-override.xml.
We have the following questions regarding the points above:
Since should not modify tangosol-coherence-override.xml are the /etc/sysctl.conf changes and MTU 3000 settings still necessary?
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