About this Document

This document provides installation instructions for Unified CCE 12.6(1) ES38. It also contains a list of Unified CCE issues resolved by this engineering special. Review all installation information before installing the product. Failure to install this engineering special as described can result in inconsistent Unified CCE behavior.

This document contains these sections:

Sign Up for Email Notification of New Field Notices

In the Product Alert Tool, you can set up profiles to receive email notification of new Field Notices, Product Alerts, or End of Sale information for your selected products.

The Product Alert Tool is available at https://www.cisco.com/cisco/support/notifications.html.

About Cisco Unified CCE (and Unified CCE Engineering Specials)

Unified CCE Compatibility and Support Specifications

Unified CCE Version Support

Unified CCE Component Support

This section lists the Unified CCE components on which you can and cannot install this engineering special.

Supported Unified CCE Components

You can install Unified CCE 12.6(1) ES38 on these Unified CCE components:

Unsupported Unified CCE Components

Do not install this engineering special on any components other than the following:

Unified CCE Engineering Special Installation Planning

Installing Unified CCE 12.6(1) ES38

Installation of this patch requires that all Unified CCE services be shut down during the entire period of installation.

  1. It is always recommended to install this ES during a scheduled downtime.
  2. Using the Unified CCE Service Control, stop all the Unified CCE Services running on the system.
  3. Launch the installer provided and follow the instructions on the screen.

If the Unified CCE Services are set to manual, using the Unified CCE Service Control, start all the Unified CCE Services.

Uninstall Directions for Unified CCE 12.6(1) ES38

  1. To uninstall this patch, go to Control Panel.
  2. Select "Add or Remove Programs".
  3. Find the installed patch in the list and select "Remove".

Note: Remove patches in the reverse order of their installation. For example, if you installed patches 3, then 5, then 10 for a product, you must uninstall patches 10, 5, and 3, in that order, to remove the patches from that product.

Resolved Caveats in this Engineering Special

This section provides a list of significant Unified CCE defects resolved by this engineering special. It contains these subsections:

Note: You can view more information on and track individual Unified CCE defects using the Cisco Bug Search tool, located at: https://bst.cloudapps.cisco.com/bugsearch/search?null.

Resolved Caveats in Unified CCE 12.6(1) ES38

This section lists caveats specifically resolved by Unified CCE 12.6(1) ES38.

Index of Resolved Caveats

Caveats in this section are ordered by Unified CCE component, severity, and then identifier.

Identifier   Severity  Component  Headline
CSCvz50705  3  web.config.api  Tomcat crashes when contacts for more than 200 campaigns are imported in a sequential manner.
CSCvy91067  3  web.config.api  Tomcat OutOfMemoryError due to SQL Delay.
CSCvz21484  3  web.config.api  Import API requests at the same millisecond results in Session was already closed failure.

Detailed list of Resolved Caveats in This Engineering Special

Caveats are ordered by severity, then by defect number.

Defect Number: CSCvz50705

Component: web.config.api

Severity: 3

Headline: Tomcat crashes when contacts for more than 200 campaigns are imported in a sequential manner.

Symptom: Tomcat crashes when importing contact records for 200+ campaigns in sequential manner. Each campaign import contact API request can have a maximum of 10K records. On SPOG front end, web page will just hang for more than the time it is supposed to take.

You may get the following error message:

Error occurred • Timed out while connecting to server. Tomcat logs will show the following errors:

OutOfMemory error. IP ADDRESS : Aug 23 2021 19:31:48.180 +0200: %CCBU_ajp-nio-127.0.0.1-8009-exec-2-3-REST_API_EXCEPTION: %[exception=java.lang.OutOfMemoryError: GC overhead limit exceeded][message_string=uncaught exception thrown by the api]: The REST API has caught an exception IP ADDRESS: Aug 23 2021 19:31:48.196 +0200: %CCBU_ajp-nio-127.0.0.1-8009-exec-2-3-EXCEPTION_INFO: %[build_date=May 04, 2021 12:05 AM][build_type=rel][exception=java.lang.OutOfMemoryError: GC overhead limit exceeded at java.lang.Long.toString(Long.java:399) at java.lang.Long.toString(Long.java:124) at java.util.Formatter$FormatSpecifier.print(Formatter.java:3096) at java.util.Formatter$FormatSpecifier.print(Formatter.java:3083) at java.util.Formatter$FormatSpecifier.printInteger(Formatter.java:2787) at java.util.Formatter$FormatSpecifier.print(Formatter.java:2747) at java.util.Formatter.format(Formatter.java:2520) at java.util.Formatter.format(Formatter.java:2455) at java.lang.String.format(String.java:2940) at com.cisco.ccbu.cce.unifiedconfig.api.bulk.processors.ImportContactBulkProcessor.getDataForReplicationFile(ImportContactBulkProcessor.java:410) at com.cisco.ccbu.cce.unifiedconfig.api.bulk.processors.ImportBulkProcessor.insertDataIntoTableAndReplicationFile(ImportBulkProcessor.java:415) at com.cisco.ccbu.cce.unifiedconfig.api.bulk.processors.ImportContactBulkProcessor.processBeans(ImportContactBulkProcessor.java:106) at com.cisco.ccbu.cce.unifiedconfig.api.bulk.processors.ImportBulkProcessor.executeImport(ImportBulkProcessor.java:97) at com.cisco.ccbu.cce.unifiedconfig.api.campaign.importcontacts.ImportContactCreateTaskBase.doWork(ImportContactCreateTaskBase.java:83) at com.cisco.ccbu.cce.unifiedconfig.api.campaign.importcontacts.ImportContactCreateTask.doWork(ImportContactCreateTask.java:111) at com.cisco.ccbu.cce.unifiedconfig.async.AsyncExecutor.executeSync(AsyncExecutor.java:298) at com.cisco.ccbu.cce.unifiedconfig.async.AsyncExecutor.execute(AsyncExecutor.java:222) at com.cisco.ccbu.cce.unifiedconfig.api.campaign.CampaignService.importContacts(CampaignService.java:510) at sun.reflect.GeneratedMethodAccessor169.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)

Conditions: CCE: 12.5

Workaround: Change the below parameters and restart tomcat service HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\Tomcat7\Parameters\Java\JvmMx -> 512 (increased from 256) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\Tomcat7\Parameters\Java\Options -> -XX:MaxPermSize=256m (increased from 128m).

Further Problem Description: The workaround mentioned above is temporary and need to be assessed by the Engineering team further based on the load testing with the max supported API limits.

Defect Number: CSCvy91067

Component: web.config.api

Severity: 3

Headline: Tomcat OutOfMemoryError due to SQL Delay.

Symptom: Tomcat goes out of memory due to SQL insertion delay.
0003170320: 10.17.46.12: Jun 24 2021 23:19:11.727 +0530: %CCBU_ajp-nio-127.0.0.1-8009-exec-2-3-REST_API_EXCEPTION: %[exception=java.lang.OutOfMemoryError: Java heap space][message_string=uncaught exception thrown by the api]: The REST API has caught an exception

Conditions: SQL delay in inserting the records to DB.

Example: 1925 secs (~30mins) for contacts to be inserted into DL.
0003170346: 10.17.46.12: Jun 24 2021 23:30:24.462 +0530: %CCBU_ajp-nio-127.0.0.1-8009-exec-3-6-REST_API_INFO: Time to take to write into the database for 1000 records is 1925225

Workaround: Restart the Tomcat.

Further Problem Description:

Defect Number: CSCvz21484

Component: web.config.api

Severity: 3

Headline: Import API requests at the same millisecond results in "Session was already closed" failure.

Symptom: Import API requests at the same millisecond results in "Session was already closed" failure.

Conditions: When two or more Import API requests are sent at the same millisecond.

Workaround: The API request tool can slow down and add 50ms delay between sending API requests as a workaround.

Further Problem Description: Getting the Patch: The following links take you to an emergency patch, called an Engineering Special or ES. These emergency patches are meant for deployments that are actively encountering a specific problem and cannot wait for a formal release to include a fix. An ES receives limited testing compared to a formal release. Installing an ES on a production system poses a risk of instability due to that limited testing. If you are not directly experiencing this problem, wait to install a major, minor, or maintenance release that includes the fix for this issue. If you experience this problem and cannot wait for a later formal release, select the ES that matches the base release of your deployment. The base release is the front part of the ES name. Only install an ES that matches the release that your deployment runs. Always read the release notes or Readme file before running the patch installer.

Caveats resolved in earlier ESs and included as part of Unified CCE 12.6(1) ES38

ES#

Identifier

Severity

Component

Headline

Comments

ES18

CSCwa00051

3

db.HDS

CCEAdmin portal in UCCE 12.6 takes more than 30 seconds to add agents to a skill

 

 

ES34

CSCwc00100

6

web.config.ui

SPOG needs to restrict administrator access to certain functions.

 

 

ES35

CSCwb36871

2

aw.tools

Unable to sync the CCAI config from control hub in cceadmin page due to Certificate error

 

 

ES37

CSCwa16619

3

web.config.api

Local authorization not happening in Logger AW for REST APIs

 

 

ES37

CSCwb73117

3

web.config.api

PCCE contacts upload to SPOG Campaign fails for Sysadmin domain users

 

 

Obtaining Documentation

You can access current Cisco documentation on the Support pages at the following sites:

Documentation Feedback

To provide comments about this document, send an email message to the following address:

contactcenterproducts_docfeedback@cisco.com

We appreciate your comments.

Obtaining Technical Assistance

Cisco.com is a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC site.

Cisco.com

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. You can also resolve technical issues with online technical support and download software packages. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

Technical Assistance Center

The Cisco TAC site is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Site

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to https://www.cisco.com/c/en/us/support/index.html.

P3 and P4 level problems are defined as follows:

In each of the above cases, use the Cisco TAC site to quickly find answers to your questions.

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following site: https://mycase.cloudapps.cisco.com/create/start/

Contacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following sites:

P1 and P2 level problems are defined as follows: