Here is a list of issues addressed in the SAS Event Stream Processing 4.3.2 hot fix:

• The C adapters restart issue was fixed.
• BoardReader adapters were fixed to not publish duplicate event blocks.
• The time-based periodicity in the Hadoop Distributed File System (HDFS) subscriber adapter was fixed by flushing the BufferedWriter for every timer expiration.
• Java adapters for Microsoft Windows were fixed to restart properly.
• When the file/socket connector is running as a socket and the server is stopped, the acceptor was deleted to ensure that the port can be re-opened.
• A file and socket connector running an HDAT name node connection was fixed to not crash during shutdown.
• Solace SEMP messages were fixed to show the correct version.
• The C Solace pubsub plugin was fixed to use the correct password.
• The DB connector was fixed to stop hanging in stop() when the commit thread is running. It was also fixed to send any pending rows if COMMITSECS or COMMITROWS is enabled. 
• The MQTT subscriber connector memory leak was fixed.
• The unknown entry point error was fixed when running the WebSphere MQ adapter with Kafka, Solace, RabbitMQ, or Tervela transport.
• An intermittent crash due to the incorrect shutdown order in the C Kafka pubsub transport executeMeta() method was fixed.
• The issue where a Kafka connector intermittently crashed while stopping was fixed by using the _kafkaProducer deletion check in stop().
• The protobuf library in the Protobuf parser no longer crashes when a field of type message is repeated, but the number of repeated fields = 0.
• The SMTP time-out issue in the notification window was fixed. SMTP now works when it has been inactive for more than 5 minutes.
• In the Streamviewer server, the XML parser could be used to expand external entities to read system files. The _documentBuilderFactory.setExpandEntityReferences(false) option was set in the XML parser to prevent this.
• The original key was transferred to a new pattern window when dynamically replacing the pattern window.
• The pattern window index was fixed to prevent a single event removal when dynamically replacing a pattern window.
• The Kafka connector with HOTFAILOVER=TRUE now goes active when a project is restarted.
• The connector and adapter password decryption failure was fixed under Windows.
• The failover case was fixed where the first message received by the standby server after setting the last message ID has ID=last message ID+1.
• The crash was fixed when the parent window to a join is replaced dynamically via a REST call.

Here is a list of enhancements included with the SAS Event Stream Processing 4.3.2 hot fix:

• REST adapter improvements: 
  • When no HTTP response code is received, the HTTPRETRIES and HTPRETRYINTERVAL options are now in effect. 
  • Log messages were added showing any bad response codes, remaining retries, and dropped requests due to configuration of IGNOREFAILEDHTTPCONNECTS or HTTPSTATUSCODES. 
  • The default number of threads was modified from unlimited to 32. 
  • The out of memory error when starting the REST adapter request thread is now caught. 
  • When a connection fails with the RETRIES option enabled, streams are not closed or disconnected from the REST service.
  • If retries are configured but exhausted, events are dropped and the adapter continues instead of quitting. 
  • Retry logic is applied for cases where the initial connect fails or a request could not be written.
• OPC-UA connector and adapter were added.
• "Queue only" mode was added to the MQ pub and the sub connector/adapter (no topic required).
• In the file and socket sub connector/adapter, the full option was added for the header parameter to output a header line that contains "opcode,flags" in addition to field names.
• Password encryption was added to the LASR adapter.

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 Event Stream Processing Engine	Microsoft® Windows® for x64	4.3
		Linux for x64	4.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.

---

An update for this issue is available for SAS® Event Stream Processing 4.3. For instructions on how to access and apply this software update see the SAS Event Stream Processing 4.3 Deployment Guide links on

http://ftp.sas.com/techsup/download/hotfix/HF2/Viya_ESP_4_3_home.html#61854

---

This note summarizes the fixes and enhancements that the SAS Event Stream Processing 4.3.2 hot fix contains.

Type:	Problem Note
Priority:	medium

Date Modified:	2018-04-24 13:17:31
Date Created:	2018-02-15 13:59:46