Kerberos connections to SAS Workload Orchestrator from grid clients such as the SAS^® Object Spawner, SASGSUB, or Base SAS^® sessions that use the GRDSVC_ENABLE function might not be removed from the disk or memory when the connection closes.

As a result, memory consumption can increase for persistent clients such as the SAS Object Spawner, and the remaining credential cache files (tktXXXXXX) increase in the Kerberos credential cache path (typically /tmp).

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 Workload Orchestrator	Windows 7 Professional 32 bit	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Windows 7 Home Premium x64	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Windows 7 Home Premium 32 bit	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Windows 7 Enterprise x64	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Windows 7 Enterprise 32 bit	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows Server 2019	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows Server 2016	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows Server 2012 Std	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows Server 2012 R2 Std	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows Server 2012 R2 Datacenter	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows Server 2012 Datacenter	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows Server 2008 for x64	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows Server 2008 R2	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows Server 2008	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows 10	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows 8.1 Pro x64	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows 8.1 Pro 32-bit	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows 8.1 Enterprise x64	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows 8.1 Enterprise 32-bit	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows 8 Pro x64	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows 8 Pro 32-bit	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows 8 Enterprise x64	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft Windows 8 Enterprise 32-bit	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Microsoft® Windows® for x64	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Windows 7 Professional x64	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Windows 7 Ultimate 32 bit	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Windows 7 Ultimate x64	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		64-bit Enabled AIX	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		64-bit Enabled Solaris	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		HP-UX IPF	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Linux for x64	9.46	9.48	9.4 TS1M6	9.4 TS1M8
		Solaris for x64	9.46	9.48	9.4 TS1M6	9.4 TS1M8

* 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 Workload Orchestrator and SAS Grid Manager for Platform 9.47 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/J9K.html#69770

---

A fix for this issue for SAS Workload Orchestrator and SAS Grid Manager for Platform 9.46 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/E3Y.html#69770

---

Kerberos connections to SAS Workload Orchestrator from grid clients such as the SAS® Object Spawner, SASGSUB, or Base SAS® sessions that use the GRDSVC_ENABLE function might not be removed from the disk or memory when the connection closes.

Type:	Problem Note
Priority:	high

Date Modified:	2022-12-19 15:20:10
Date Created:	2022-12-16 09:45:35