Universal Contact Server Release Notes
|Release Date||Release Type||Restrictions||AIX||HP-UX PA||HP-UX IPF||Linux||Solaris||Windows|
New in This Release
There are no restrictions for this release. This section describes new features that were introduced in this release of Universal Contact Server.
- Oracle Driver is updated to version 18.104.22.168.0.
- PostgreSQL 9.3 is supported with the following limitations:
- No clustering: Although PostgreSQL supports clustering and replication streams, this release of UCS does not support those features.
- High availability and load balancing are not supported.
- When connected to an Oracle database, UCS now sets oracle.net.CONNECT_TIMEOUT to 3000 (nine seconds). Previously, the database might accept the connection but never respond, in which case UCS's database connections remained stuck.
- When the max-connections option has a value of 0 (zero), the number of connections that Universal Contact Server can open simultaneously to this database is internally set to the default value of 40. Previously, UCS interpreted a value of 0 as meaning no connections and did not start.
- When connected to an Oracle database, UCS now sets oracle.jdbc.ReadTimeout to 5 minutes, so that a timeout occurs if no network packet is received within that period. Previously, network packets might be lost, which caused UCS's database connections to be permanently stuck. Note that in normal situations the DAP timeout is still taken into account.
Corrections and Modifications
This release also includes the following corrections or modifications:
The configuration of archiving and purging now affects UCS dynamically, even when the application configured as backup is running as primary. (ESR-8613)
When screening rules are deleted, the caching mechanism is properly cleared. Previously, the mechanism was not properly cleared, which could lead to high memory usage if a large number of rules were deleted. (ESR-8503)
The DataCorrection jobs launched by UCS Manager no longer removes attributes with DateValue not null (also known as LastCalledAgent_TimeStamp). Previously, these attributes were considered to be fixed. (ESR-8361)