Last updated on MARCH 27, 2015
Applies to:Oracle Communications Converged Application Server - Version 4.0.0 and later
Information in this document applies to any platform.
When a Java thread on the engine needs to access data on a CallState which is shared across different calls on the replica, for each different data (variable) which needs to be accessed, the engine locks and releases the call state for each operation, e.g. for the following example code :
This is not very efficient.
Instead, the approach described in the solution section of this note can be implemented to greatly reduce contention.
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