Operational Defect Database
BugZero updated this defect 58 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 372986
Smarts SAM 9.1/9.2: Slow initial broker/domain connection time seen in WebConsole and Business Dashboard after upgrading from earlier Smarts SAM version
Last update date:
3/22/2024
Affected products:
Smart Assurance - SMARTS
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
After upgrading to Smarts Service Assurance Manager (Smarts SAM) 9.1 or 9.2, the initial connection of Smarts SAM Business Dashboard or Smarts SAM Web Console to the Smarts broker and domains is slow
Cause
The above issue has been found to occur when there is a lack of Entropy on the system. Entropy is required by the Transport Layer Security (TLS) protocol used by Smarts 9.1 and later applications, and a lack of Entropy in the system will cause a delay in establishing a TLS session, resulting in a slow broker/domain connection. Smarts Foundation software started using the industry standard TLS protocol as the inter-process communication protocol for EMC Smarts applications. TLS replaces the Smarts proprietary IPC protocol in Smarts 9.1 and later.
Resolution
If you encounter this issue, you can do either of the following:Disable TLSSet the java "egd" parameter on the system where the browser runsThe following sections explain the requirements, considerations, and steps for each of these options. Disabling TLSDisabling TLS should be done in accordance with the local network security policies. Disabling TLS can be done as follows:On the machine where the Smarts tomcat server is started, open the webconsole.properties file in the following directory: <BASEDIR>/smarts/tomcat/webapps/webconsole Add the following line (or set existing parameter to "true"):# Flag to disable TLScom.smarts.no_tls=true Save and close the webconsole.properties file.Restart tomcat after this change is made. Setting the java "egd" parameter on the system where the browser runsSetting the "java.security.egd" parameter must be done on every Linux/Solaris machine where connection slowness is observed in the browser. There are a few ways to do this, but updating the java.security file in the JRE/JDK should resolve the issue. This is done as follows: On the Linux/Solaris machine where connection slowness is observed, open the java.security file in the following location: <JDK/JRE>/lib/security/java.security Find the following line:securerandom.source=file:/dev/urandom Change the above line to the following:securerandom.source=file:/dev/./urandomIMPORTANT! The extra "./" in the above file path is required. Without it, the "file:/dev/urandom" path is sometimes mapped back to "file:/dev/random" (see http://bugs.sun.com/view_bug.do;?bug_id=6521844). Save and close the java.security file.
