Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Serena VM Web Application Server fails to initialize the SSL connector(s) on port 8443 and/or 8444
... 26 more Sep 26, 2012 12:24:42 PM org.apache.catalina.core.StandardService initInternal SEVERE: Failed to initialize connector [ Connector [HTTP/1.1-8444]]
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()."
When Version Manager File Server clients connect to a VM File Server running release 8.5.0, and they communicate with that server via SSL (HTTPS on port 8443 ), those clients will randomly get errors of the type: File Server Status Error communicating with file server "https://ServerName
CMS-XML How to configure one-way and two-way SSL for Release Control and ZMF Connector
edit server.xml to use port 8443 and a valid path and password to the keystore/truststore file. For example:
CMS-XML How to install setup the ZMF Connector to communicate with SBM using SSL (SBM and ZMF Connector on same server)
-- Uncomment out the port 8443 section by removing the beginning comment characters (<!-- ) and the ending comment characters (-->) -- Update the keystorePass to the password you entered in Step 7 above -- Remove the keyAlias for the keystoreFile
CMS-XML KM-Dim9: How To setup SSL on Dimenions 9.1.3 on Win 2003
And search for: <!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 --> And add the following:
CMS-XML MCLG: How to setup Collage to run using SSL (https) instead of http?
<!-- SSL HTTP/1.1 Connector --> < Connector port =" 8443 " maxThreads="150"
MS-WORD Mitigating POODLE in SBM.doc
For each defined < Connector > element for HTTPS ( ports 8243, 8343 or 8443 ) add the following attribute: protocols="TLSv1,TLSv1.1,TLSv1.2" For example:
CMS-XML KM-Dim9: How to enable SSL on Tomcat
Now restart Tomcat and check the stderr.log file for errors. If there are none, then you should be able to connect through https: < https://localhost: 8443 >
CMS-XML KM-DIM2009R2: How to configure Tomcat to use SSL with a self-signed certificate
< Connector SSLEnabled=" ... port =" 8443 " scheme="https" secure="true" sslProtocol=" TLS " strategy="ms" truststoreFile="C:\Temp\.keystore" truststorePass="serena"/>
CMS-XML Dim10: How does Dimensions Desktop Client know how to connect to the Build Server?
When Dimensions connects to the Tomcat server, such as when the build is started by the Desktop Client, the server uses symbols in the dm.cfg to locate the address of the Tomcat server. ... DM_BUILDERWS_URL http://<servername>:< port > DM_WEB_URL http://<servername>:< port > ... If using SSL , they would look similar to the following: DM_BUILDERWS_URL https://mysecureserver: 8443 DM_WEB_URL https://mysecureserver: 8443
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs