Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Watch4Net | SRM: Web client loading fails from timeout after implementing SSL on the frontend (516361)

Last Updated: 5/29/2020Categories: TroubleshootingTotal Views: 4178Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

After implementing an SSL certificate on the frontend host and updating the server.xml file to point to the keystore where the certificated was imported, the application web client is no longer able to load in a browser window and eventually times out. Restarting Tomcat has no effect and the following error shows up in the catalina log under a timestamp associated with Tomcat startup:

Jan 10, 2018 1:16:50 PM org.apache.catalina.core.StandardService initInternal
SEVERE: Failed to initialize connector [Connector[HTTP/1.1-58443]]
org.apache.catalina.LifecycleException: Failed to initialize component [Connector[HTTP/1.1-58443]]
...
Caused by: org.apache.catalina.LifecycleException: Protocol handler initialization failed
...
Caused by: java.lang.IllegalArgumentException: java.security.NoSuchAlgorithmException: TLSv1.2, TLS SSLContext not available
... 30

Cause

The issue is generally caused by an error in the new values introduced into the server.xml file. For example, the path specifying the location of the SSL keystore may be inaccurate. In the case of the above error, the issue was with the following xml tag:

sslProtocol="TLSv1.2" URIEncoding="UTF-8"

The above tag could not be read by Tomcat and is labeled by the error trapping logic as an illegal parameter because the Connector port xml tag's sslProtocol attribute name does not match the tag attribute name required by Tomcat, which should read as sslProtocols (adding a letter 's' on the end to make it plural). For example:

sslProtocols="TLSv1.2" URIEncoding="UTF-8"

This resulted in Tomcat being unable to identify TLSv1.2 as an available context which prevented the web application from initializing the port to which users must connect to load and log into the application web client.

Resolution

To resolve the issue:

1. Open the following file for editing in a host OS appropriate text editor capable of displaying XML formatting (ex.: Notepad++):

{SRM home path}/Web-Servers/Tomcat/Default/conf/server.xml

2. Correct any XML formatting errors that would prevent the file from being read and parsed by the application.
3. If a backup of the file exists from before the SSL configuration was changed, make a comparison of all parameter names contained in the file to make sure that all spelling and character cases in the current file exactly match those in the backup file. Correct any parameter names that may not match (see the example listed in the cause portion of this knowledge base article).
4. Make certain there are no spaces to either side of the equal sign (=) between any parameter name and any parameter value. Remove them if any.
5. Save and exit the file
6. Restart Tomcat on the front end host using the following command:

{SRM home path}/bin/manage-modules.sh service restart tomcat

If all flaws in the server.xml file have been correctly eliminated, Tomcat should now be able to properly initialize.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - Watch4Net/M&R

Take Our Survey

Support Assistant