When you are using SAS Real-Time Decision Manager 6.5 with the SAS Federation Server 4.2, you might notice an increase in in-memory usage for Java processes. This increase of memory usage produces a gradual decline of throughput and increased response time.

The problem occurs due to a memory leak in the JDBC driver in the SAS Decision Services JVM garbage collection activity (for identifying unused memory blocks and allocating them for reuse). The process eventually consumes most of the available heap/memory.

To work around the issue, restart the SAS Federation Server to reset memory, or increase the size of the JVM heap. However, increasing the heap size is only a temporary fix.

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 Federation Server	Solaris for x64	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Linux for x64	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		HP-UX IPF	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		64-bit Enabled Solaris	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		64-bit Enabled AIX	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Windows 7 Ultimate x64	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Windows 7 Ultimate 32 bit	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Windows 7 Professional x64	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Windows 7 Professional 32 bit	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Windows 7 Home Premium x64	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Windows 7 Home Premium 32 bit	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Windows 7 Enterprise x64	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Windows 7 Enterprise 32 bit	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Microsoft Windows Server 2012 Std	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Microsoft Windows Server 2012 R2 Std	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Microsoft Windows Server 2012 R2 Datacenter	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Microsoft Windows Server 2012 Datacenter	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Microsoft Windows Server 2008 for x64	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Microsoft Windows Server 2008 R2	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Microsoft Windows Server 2008	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Microsoft Windows 10	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Microsoft Windows 8.1 Pro x64	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Microsoft Windows 8.1 Pro 32-bit	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Microsoft Windows 8.1 Enterprise x64	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Microsoft Windows 8.1 Enterprise 32-bit	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Microsoft Windows 8 Pro x64	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Microsoft Windows 8 Pro 32-bit	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Microsoft Windows 8 Enterprise x64	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Microsoft Windows 8 Enterprise 32-bit	4.2	4.2.1	9.4 TS1M3	9.4 TS1M4
		Microsoft® Windows® for x64	4.2	4.2.1	9.4 TS1M3	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 Decision Services 6.4_M1 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/Z24.html#58336

---

A fix for this issue for SAS Drivers for Federation Server 4.2 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/Z51.html#58336

---

A fix for this issue for SAS Management Console 9.4_M3 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/V11.html#58336

---

A fix for this issue for SAS Middle Tier 9.4_M3 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/V10.html#58336

---

When using SAS Federation Server 4.2, you might see an increase of in-memory usage for Java processes. This Java process could be for the SAS Web App Server or tc Server due to a JDBC driver bug.

Type:	Problem Note
Priority:	high

Date Modified:	2016-06-20 13:57:06
Date Created:	2016-06-03 23:31:09