SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 59434: Reply processing that fails as a result of errors causes a memory leak and instability in the SAS® Digital Marketing server

DetailsHotfixAboutRate It

In SAS Digital Marketing server, reply processing fails as a result of errors. When this problem occurs, the SAS Digital Marketing server might be unstable, with connection errors and a memory leak. This behavior might prevent the execution of broadcasts.

The errors that occur with failed reply processing might appear in the form of multiple, badly formed email addresses. When this problem happens, errors similar to the following might appear in the SASDigitalMarketing server log file:

2016-10-18 08:29:57,163 DEBUG [] [] [] FilterThread Exception occurred while processing the message javax.mail.internet.AddressException: Missing local name in string ``@''
                 at javax.mail.internet.InternetAddress.checkAddress(InternetAddress.java:1151)

In addition, the memory leak might show up as an error in the SASDigitalMarketing server log file, as shown in this example:

2016-10-18 09:04:05,317 ERROR (localhost-startStop-5)
[org.apache.catalina.loader.WebappClassLoader] The web application [/sdm]
appears to have started a thread named [Thread-19] but has failed to stop it.
This is very likely to create a memory leak.

To work around the problem, do one of the following:

  • If you do not use reply processing, disable the reply-processing option in SAS® Digital Marketing Studio.
  • Clear the bad email data from the Reply Email server and ensure that the emails that are being broadcast use only verified email addresses. You might also increase the number of minutes between automatic checks of the Reply Email Server.

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 Digital MarketingMicrosoft® Windows® for x646.3
Microsoft Windows 8 Enterprise 32-bit6.3
Microsoft Windows 8 Enterprise x646.3
Microsoft Windows 8 Pro 32-bit6.3
Microsoft Windows 8 Pro x646.3
Microsoft Windows 8.1 Enterprise 32-bit6.3
Microsoft Windows 8.1 Enterprise x646.3
Microsoft Windows 8.1 Pro 32-bit6.3
Microsoft Windows 8.1 Pro x646.3
Microsoft Windows 106.3
Microsoft Windows 95/986.3
Microsoft Windows 2000 Advanced Server6.3
Microsoft Windows 2000 Datacenter Server6.3
Microsoft Windows 2000 Server6.3
Microsoft Windows 2000 Professional6.3
Microsoft Windows NT Workstation6.3
Microsoft Windows Server 2003 Datacenter Edition6.3
Microsoft Windows Server 2003 Enterprise Edition6.3
Microsoft Windows Server 2003 Standard Edition6.3
Microsoft Windows Server 2003 for x646.3
Microsoft Windows Server 20086.3
Microsoft Windows Server 2008 R26.3
Microsoft Windows Server 2008 for x646.3
Microsoft Windows Server 2012 Datacenter6.3
Microsoft Windows Server 2012 R2 Datacenter6.3
Microsoft Windows Server 2012 R2 Std6.3
Microsoft Windows Server 2012 Std6.3
Microsoft Windows XP Professional6.3
Windows 7 Enterprise 32 bit6.3
Windows 7 Enterprise x646.3
Windows 7 Home Premium 32 bit6.3
Windows 7 Home Premium x646.3
Windows 7 Professional 32 bit6.3
Windows 7 Professional x646.3
Windows 7 Ultimate 32 bit6.3
Windows 7 Ultimate x646.3
Windows Millennium Edition (Me)6.3
Windows Vista6.3
Windows Vista for x646.3
64-bit Enabled AIX6.3
64-bit Enabled Solaris6.3
HP-UX IPF6.3
Linux for x646.3
Solaris for x646.3
* 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.