EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB18516: TCP/IP connections to the MicroStrategy Intelligence Server 9.x appear to never be closed and left hanging on the system


Community Admin

• Strategy


In MicroStrategy 9.x, system administrators may notice that network connections opened to the MicroStrategy Intelligence Server are never killed. These connections are typically open on the Intelligence Server machine, but checking the other endpoint (typically MicroStrategy Web) shows no trace of the connections, and these remain in an idle state. Users should note that in general the MicroStrategy Web server opens a number of connections to the Intelligence Server (initial pool size) and these will remain relatively idle until user activity increases in MicroStrategy Web, so simply observing idle connections may not indicate this issue.

SYMPTOM:
In Strategy 9.x, system administrators may notice that network connections opened to the Strategy Intelligence Server are never killed. These connections are typically open on the Intelligence Server machine, but checking the other endpoint (typically Strategy Web) shows no trace of the connections, and these remain in an idle state. Users should note that in general the Strategy Web server opens a number of connections to the Intelligence Server (initial pool size) and these will remain relatively idle until user activity increases in Strategy Web, so simply observing idle connections may not indicate this issue.
These open connections use up file descriptors on Unix/Linux platforms, and may cause the Intelligence Server to reach the maximum number of open files limit. On Microsoft Windows operating systems, these open connections will reduce the number of active connections available (since on Windows the number of open connections is limited in proportion to the number of network threads see KB16624). In both cases however the end result may be loss in connectivity.
  
 
CAUSE:
This issue is typically caused by firewall timeouts. Usually the Intelligence Server does not initiate or close connections, that is the responsibility for the client (including the Web Server). Since the Web Server keeps the connection open to the Intelligence Server without closing, some firewalls may decide to close the connection - with a one sided 'reset' packet after a set amount of time. Because only the Web server is informed of the closed connection, the connection may remain open indefinitely on the Intelligence Server. Over a period of time these orphaned connections may accumulate and lead to connectivity issues.
 
ACTION:
Starting with Strategy Intelligence Server 8.1.1 Hotfix 3, there is a new idle timeout setting for each network connection created to the Strategy Intelligence Server. Once the idle timeout, speficied in minutes, has expired, the Strategy Intelligence Server will drop and clean up the connection.
 
The timeout can be changed by following steps below for each one of the Intelligence Server machines involved in an environment, whether it be just one or more than one if in a clustered environment. It is not necessary to apply these changes on machines with other Strategy products such as Strategy Desktop or Strategy Narrowcast Server, this workaround is only intended for Intelligence Server machines:
 
For Windows Operating Systems:
 

  1. Open the Registry Editor in Windows and locate the following key:
    HKEY Local Machine\\SOFTWARE\\MicroStrategy\\Data Sources\\CastorServer\
  2. Create a new DWORD Value and name it "IdleTimeout"
  3. Set the value. This value will be in minutes and it should be set to a value greater than the maximum value for either the 'User session idle time' or the 'Web user session idle time' setting. For example, if the 'User session idle time' is 1800 seconds (30 minutes) and the 'Web user session idle time' is 600 seconds (10 minutes), the IdleTimeout setting can be set to 35 minutes to encompass both settings.
  4. It will not be necessary to restart the Strategy Intelligence Server. This setting will be applied for any subsequent connections created after this value was entered.

For the Strategy Intelligence Server Universal on Unix/Linux Operating Systems
 

  1. Edit the MSIReg.reg file located under the home installation directory.
  2. Locate the following section within this file:
    "HKEY Local Machine\\SOFTWARE\\MicroStrategy\\Data Sources\\CastorServer\\"
  3. Add a new line like the following (including the quotes):
    "IdleTimeout"=dword:XXXXXXXX
  4. Replace the "XXXXXXXX" string with a hexadecimal value for the required new connection timeout. This value will be in minutes and it should be set to a value greater than the maximum value for either the 'User session idle time' or the 'Web user session idle time' setting. For example, if the 'User session idle time' is 1800 seconds (30 minutes) and the 'Web user session idle time' is 600 seconds (10 minutes), the IdleTimeout setting can be set to 35 (dword:00000023) minutes to encompass both settings.
  5. Save the MSIReg.reg file.
  6. Restart the Strategy Intelligence Server.

Note: A value of -1 should not be used.
 
Registry Modification:
WARNING:
Modifying registry values incorrectly may cause serious, system-wide problems that may require the re-installation of Microsoft Windows. Any edit of the registry is done at the user's own risk. Since these are user-initiated changes, they are not covered by any Strategy warranty. If using Microsoft Windows, the user should backup the registry and/ or update an Emergency Repair Disk prior to alterations.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 2, 2017

Last Updated:

June 2, 2017