SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 61365: Existing connections between object spawners are not closed when you refresh object spawners

DetailsHotfixAboutRate It

When you refresh object spawners, the initial connections established between object spawners for logical load-balanced servers are not closed. Each of these connections has an additional connection to the metadata server. The metadata server connection also remains open because the closing of that connection is driven by the closing of the connection between the object spawners.

When you encounter this problem, you might notice an increase in TCP connections between the object spawners and the metadata server when you execute the Refresh Spawner action on the object spawners. The number of open connections can be exacerbated when the environment contains several application server contexts that contain load-balanced workspace server definitions.

To work around this problem, execute the Refresh Application Server action. This action enables you to select the specific application server contexts that might have been added or changed to refresh. Using this action eliminates the additional connections created for the existing load-balanced servers.

For more information about object spawner actions, see the "Using SAS Management Console to Operate SAS Servers" section in SAS Intelligence Platform: Administration / System Administration Guide.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Object Spawnerz/OS9.4_M49.4 TS1M4
Microsoft® Windows® for x649.4_M49.4 TS1M4
Microsoft Windows 8 Enterprise 32-bit9.4_M49.4 TS1M4
Microsoft Windows 8 Enterprise x649.4_M49.4 TS1M4
Microsoft Windows 8 Pro 32-bit9.4_M49.4 TS1M4
Microsoft Windows 8 Pro x649.4_M49.4 TS1M4
Microsoft Windows 8.1 Enterprise 32-bit9.4_M49.4 TS1M4
Microsoft Windows 8.1 Enterprise x649.4_M49.4 TS1M4
Microsoft Windows 8.1 Pro 32-bit9.4_M49.4 TS1M4
Microsoft Windows 8.1 Pro x649.4_M49.4 TS1M4
Microsoft Windows 109.4_M49.4 TS1M4
Microsoft Windows Server 20089.4_M49.4 TS1M4
Microsoft Windows Server 2008 R29.4_M49.4 TS1M4
Microsoft Windows Server 2008 for x649.4_M49.4 TS1M4
Microsoft Windows Server 2012 Datacenter9.4_M49.4 TS1M4
Microsoft Windows Server 2012 R2 Datacenter9.4_M49.4 TS1M4
Microsoft Windows Server 2012 R2 Std9.4_M49.4 TS1M4
Microsoft Windows Server 2012 Std9.4_M49.4 TS1M4
Windows 7 Enterprise 32 bit9.4_M49.4 TS1M4
Windows 7 Enterprise x649.4_M49.4 TS1M4
Windows 7 Home Premium 32 bit9.4_M49.4 TS1M4
Windows 7 Home Premium x649.4_M49.4 TS1M4
Windows 7 Professional 32 bit9.4_M49.4 TS1M4
Windows 7 Professional x649.4_M49.4 TS1M4
Windows 7 Ultimate 32 bit9.4_M49.4 TS1M4
Windows 7 Ultimate x649.4_M49.4 TS1M4
64-bit Enabled AIX9.4_M49.4 TS1M4
64-bit Enabled Solaris9.4_M49.4 TS1M4
HP-UX IPF9.4_M49.4 TS1M4
Linux for x649.4_M49.4 TS1M4
Solaris for x649.4_M49.4 TS1M4
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.