About this Document
This document provides installation instructions for Unified CCE 12.6(1) ES61. 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:
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.
Unified CCE Version Support
- Unified CCE 12.6(1)
- Packaged CCE 12.6(1)
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) ES61 on these Unified CCE components:
Unsupported Unified CCE Components
Do not install this engineering special on any components other than the following:
Installation of this patch requires that all Unified CCE services be shut down during the entire period of installation.
- It is always recommended to install this ES during a scheduled downtime.
- Using the Unified CCE Service Control, stop all the Unified CCE Services running on the system.
- 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.
- To uninstall this patch, go to Control Panel.
- Select "Add or Remove Programs".
- 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:
- Resolved Caveats in Unified CCE 12.6(1) ES61
- Caveats resolved in earlier ESs and included as part of Unified CCE 12.6(1) ES61
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) ES61
This section lists caveats specifically resolved by Unified CCE 12.6(1) ES61.
Index of Resolved Caveats
Caveats in this section are ordered by Unified CCE component, severity, and then identifier.
Identifier |
Severity |
Component |
Headline |
CSCwe94791 |
2 |
web.config.api |
Contacts are not getting uploaded in API Campaign due to Java OutOfMemory |
Detailed list of Resolved Caveats in This Engineering Special
Caveats are ordered by severity then defect number.
Defect Number: CSCwe94791
Component: web.config.api
Severity: 2
Headline: Contacts are not getting uploaded in API Campaign due to Java OutOfMemory
Symptom:
Customers are trying to upload the contacts Via the API Import process,Prior to the JavaOutOf Memory could see the delay in updating the database records.
CCBU_ajp-nio-127.0.0.1-8009-exec-5-6-REST_API_INFO: Time to take to write into the database for 6 records is 484
CCBU_ajp-nio-127.0.0.1-8009-exec-7-6-REST_API_INFO: Time to take to write into the database for 30 records is 1141
0000009022: 10.1.47.46: Mar 09 2023 12:47:47.969 +0530: %CCBU_ajp-nio-127.0.0.1-8009-exec-9-6-REQUEST_END: %[PARAM_TIME_ELAPSED=2738924]: Request complete
0000025755: 10.1.47.46: Mar 09 2023 12:47:50.844 +0530: %CCBU_ajp-nio-127.0.0.1-8009-exec-9-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
0000025756: 10.1.47.46: Mar 09 2023 12:47:52.750 +0530: %CCBU_ajp-nio-127.0.0.1-8009-exec-9-3-EXCEPTION_INFO: %[build_date=Sep 06, 2022 7:13 AM][build_type=rel][exception=java.lang.OutOfMemoryError: Java heap space
Conditions:
Due to tomcat is seeing the java heap memory performance issues and that is causing the break here.
Workaround:
Restart the tomcat services.
Further Problem Description:
Later could see the SQL Connection error: Which was fixed in 12.6.1 and Defect is - CSCvw82858 - Could see the 503 Service unavaliable error on the AW Tomcat logs
AW Tomcat logs
0000274963: 10.1.47.15: Feb 27 2023 12:00:45.331 +0530: %CCBU_ajp-nio-127.0.0.1-8009-exec-2-6-REST_API_INFO: Response Got is POST https://drtcclogprw01:443/unifiedconfig/config/personalcallback/import?proxied=true returned a response status of 503 Service Unavailable
0000274964: 10.1.47.15: Feb 27 2023 12:00:45.331 +0530: %CCBU_ajp-nio-127.0.0.1-8009-exec-2-3-REST_API_EXCEPTION: %[exception=com.cisco.ccbu.api.jaxb.error.ApiException: Cannot connect to the database; make sure that SQL Server is running.][message_string=Error 503 occurred while trying to POST to https://drtcclogprw01:443 ]: The REST API has caught an exception
0000274965: 10.1.47.15: Feb 27 2023 12:00:45.331 +0530: %CCBU_ajp-nio-127.0.0.1-8009-exec-2-3-EXCEPTION_INFO: %[build_date=Nov 17, 2022 11:03 AM][build_type=rel][exception=com.cisco.ccbu.api.jaxb.error.ApiException: Cannot connect to the database; make sure that SQL Server is running.
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.processErrorResponse(RESTClient.java:160)
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.analyzeClientResponse(RESTClient.java:116)
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.makeRequest(RESTClient.java:270)
Logger Tomcat logs :
0000025749: 10.1.47.46: Mar 09 2023 12:01:25.191 +0530: %CCBU_ajp-nio-127.0.0.1-8009-exec-10-6-REST_API_INFO: Delimiter used for replication is [^]
0000025750: 10.1.47.46: Mar 09 2023 12:01:25.691 +0530: %CCBU_ajp-nio-127.0.0.1-8009-exec-2-3-EXCEPTION_INFO: %[build_date=Sep 06, 2022 7:13 AM][build_type=rel][exception=com.cisco.ccbu.api.jaxb.error.ApiException: Cannot connect to the database; make sure that SQL Server is running.
at com.cisco.ccbu.cce.unifiedconfig.db.HibernateSession.getSessionFactory(HibernateSession.java:339)
at com.cisco.ccbu.cce.unifiedconfig.db.HibernateSession.getSessionFactoryForBaDB(HibernateSession.java:215)
at com.cisco.ccbu.cce.unifiedconfig.db.HibernateSession.openBADatabaseSession(HibernateSession.java:543)
Caveats resolved in earlier ESs and included as part of Unified CCE 12.6(1) ES61
ES#
|
Identifier
|
Severity
|
Component
|
Headline
|
Comments
|
ES50
|
CSCwd23815
|
3
|
outbound
|
Outbound Personal Call Back API got response error 500
|
-
|
You can access current Cisco documentation on the Support pages at the following sites:
- https://www.cisco.com
- https://www-china.cisco.com
- https://www-europe.cisco.com
Documentation Feedback
To provide comments about this document, send an email message to the
following address:
contactcenterproducts_docfeedback@cisco.com
We appreciate your comments.
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:
- P3--Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
- P4--You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.
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:
- P1--Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.
- P2--Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.