This document provides
installation instructions for Unified CCE 12.5(1) ES100. 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 the
following 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.
The Product
Alert Tool is available at https://www.cisco.com/cisco/support/notifications.html.
.
This section lists the Unified
CCE components on which you can and cannot install this engineering special.
You can install Unified CCE
12.5(1) ES100 on the following Unified CCE components:
Do not install this engineering
special on any component other than:
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.
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.
This section lists caveats
specifically resolved by Unified CCE 12.5(1) ES100.
Caveats in this section are
ordered by Unified CCE component, severity, and then identifier.
|
Severity |
Component |
Headline |
CSCvz50705 |
3 |
web.config.api |
Tomcat crashes when contacts for more than 200 campaigns are imported in a sequential manner |
Defect Number: CSCvz50705
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
<https://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<https://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.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
You can access current Cisco
documentation on the Support pages at the following sites:
To provide comments about this
document, send an email message to the following address:
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 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.
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.
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.
In each of the above cases, use
the Cisco TAC site to quickly find answers to your questions.
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: