Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Tomcat components fail to start after it's upgraded from 8.5 version.
A number of customers have upgraded Tomcat 8.5 that comes with Dimensions CM to newer 8.5.x versions in order to resolve some vulnerabilities. However, after Tomcat is upgraded some of the Connectors fail to start up. Tomcat logs include the following errors:
CMS-XML DimCM: Tomcat: How to upgrade Tomcat to 8.5.51 for Dimensions CM 14.4 and 14.5.x plus details for Tomcat 8.5.55 and above
The main concern with tomcat versions prior to 8.5.51 is the AJP connector, which is not used by Dimensions CM. Therefore we recommend this is commented out from tomcat / 8.5 /conf/server.xml. 1/ Stop the Micro Focus Tomcat service
CMS-XML DimCM: Pulse: Pulse not working after upgrade to Tomcat 8.5.54
Browse to the $ Tomcat \webapps\pulse\WEB-INF\web.xml file. Make a backup copy of this file.
CMS-XML DimCM: Pulse: Database upgrade fails 'Missing IN or OUT parameter at index:: 2' if any product has a default review check list
Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'databaseSchemaUpgrade' defined in URL [jar:file:/C:/Program%20Files/Micro%20Focus/common/ tomcat / 8.5 /webapps/pulse/WEB-INF/lib/platform-dbschema-14.5.0-SNAPSHOT.jar!/META-INF/starlight/app-components.xml]:
CMS-XML ZMF Connector: Upgrading to ZMF Connector 6.2.1, but encrypt fails with "java.security.InvalidKeyException: Illegal key size"
NOTE: The new Common Tomcat is still Tomcat 8.5 and the JRE is still 8.0, but the configuration has been updated.
CMS-XML Is Version Manager 8.6.3 affected by CVEs that include Tomcat 8.5.61 as an affected release?
Version Manager 8.6.3 upgraded Tomcat to release 8.5 .61 to solve potential security vulnerabilities.
CMS-XML Is Version Manager 8.5.3 affected by CVEs that include Tomcat 7.0.57 as an affected release?
Version Manager 8.5 .3 upgraded Tomcat to release 7.0.57 to solve a number of security vulnerabilities.
CMS-XML VM 8.5.3 DEF307915: HotFix for VM 8.5.3 to address Tomcat vulnerabilities CVE-2017-12615 and CVE-2017-12617
The attached HotFix solves the following issue in VM 8.5.3: DEF307915: Upgrade to Tomcat 7.0.82 to avoid vulnerabilities CVE-2017-12615 and CVE-2017-12617
CMS-XML After upgrading the VM server to release 8.5.0, File Server clients using SSL randomly report "error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure" Detail: SSL connect failed in tcp_connect()."
To work around this issue, all Diffie-Hellman ciphers must be disabled on the Tomcat server that is used by the Serena VM Web Application to run the VM File Server. Instructions on how to change these ciphers can be found in KB article S139650 .
CMS-XML Is Version Manager 8.6.2 affected by CVEs that include Tomcat 8.5.42 as an affected release?
An h2c direct connection did not release the HTTP/1.1 processor after the upgrade to HTTP/2. If a sufficient number of such requests were made, an OutOfMemoryException could occur leading to a denial of service.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs