SAS Metadata Server might experience high CPU utilization under normal running conditions. As the system increases its CPU utilization, SAS Metadata Server might not respond to client requests and might seem to stop responding. For example, new logon requests from SAS^® Management Console or SAS^® Enterprise Guide^® might time out.

The underlying cause of this problem is an infinite loop that occurs when SAS Metadata Server performs normal communication with an LDAP server over SSL.

The workaround is to restart SAS Metadata Server, which resolves the problem only temporarily.

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

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Metadata Server	HP-UX IPF	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		64-bit Enabled Solaris	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Windows 7 Professional 32 bit	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Windows 7 Home Premium x64	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Windows 7 Home Premium 32 bit	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Windows 7 Enterprise x64	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Windows 7 Enterprise 32 bit	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Microsoft Windows XP Professional	9.3_M2		9.3 TS1M2
		Microsoft Windows Server 2012 Std	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Microsoft Windows Server 2012 R2 Std	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Microsoft Windows Server 2012 R2 Datacenter	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Microsoft Windows Server 2012 Datacenter	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Microsoft Windows Server 2008 for x64	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Microsoft Windows Server 2008 R2	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Microsoft Windows Server 2008	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Microsoft Windows Server 2003 for x64	9.3_M2		9.3 TS1M2
		Microsoft Windows Server 2003 Standard Edition	9.3_M2		9.3 TS1M2
		Microsoft Windows Server 2003 Enterprise Edition	9.3_M2		9.3 TS1M2
		Microsoft Windows 8.1 Pro x64	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Microsoft Windows 8.1 Pro 32-bit	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Microsoft Windows 8.1 Enterprise x64	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Microsoft Windows 8.1 Enterprise 32-bit	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Microsoft Windows 8 Pro x64	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Microsoft Windows 8 Pro 32-bit	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Microsoft Windows 8 Enterprise 32-bit	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Microsoft® Windows® for x64	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		64-bit Enabled HP-UX	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		64-bit Enabled AIX	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Windows Vista for x64	9.3_M2		9.3 TS1M2
		Windows Vista	9.3_M2		9.3 TS1M2
		Windows 7 Ultimate x64	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Windows 7 Ultimate 32 bit	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Windows 7 Professional x64	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Microsoft Windows Server 2003 Datacenter Edition	9.3_M2		9.3 TS1M2
		Microsoft Windows 8 Enterprise x64	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		z/OS	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Linux	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Linux for x64	9.3_M2	9.4_M4	9.3 TS1M2	9.4 TS1M4
		Solaris for x64	9.3_M2	9.4_M4	9.3 TS1M2	9.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.

---

A fix for this issue for SAS Threaded Kernel Core Routines 9.4_M3 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/V63.html#56744

---

A fix for this issue for SAS Threaded Kernel Core Routines 9.4_M2 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/R87.html#56744

---

A fix for this issue for SAS Threaded Kernel Core Routines 9.3_M2 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/I29.html#56744

---

There have been customer reports that the CPU utilization for SAS Metadata Server has increased. The Linux kernel tracing shows that a value is read from memory (futex call), but it is not accessible or changed during the reading. Then it starts looping continuously, which increases CPU usage.

Type:	Problem Note
Priority:	medium

Date Modified:	2015-10-13 10:52:28
Date Created:	2015-10-07 14:35:53