Problem Note 68428: Issues that are addressed in Hot Fix 6.2.3 for SAS® Event Stream Processing
Hot Fix 6.2.3 for SAS Event Stream Processing contains the following fixes and enhancements.
Fixes:
- Updated the dfesp_rest_subscriber adapter to use INFO level log messages instead of console messages
- Fixed the memory leak when you use secure HTTP connections
- Configured the dfesp_rest_subscriber adapter to reuse connections to the REST service to improve performance
- Fixed a lack of responsiveness when you stop the PI Web publisher connector
- Fixed the issue when the PI Web subscriber connector could not find the element or the attribute to now log an appropriate error message
- In the PI Web connector/adapter, added a sleep function to the publisher thread to reduce CPU usage
- Configured the PI Web connector/adapter to support query responses containing more than 1,000 items
- Configured Java log messages to use the default character set instead of ISO_8859_1
- In the PI Web connector/adapter, fixed an issue when the subscriber is stopped
- Reduced the CPU usage of web socket subscribers by removing the polling interval of 0
- In the PI Web connector/adapter, restored the REST and web socket connections when the PI server goes down
- Fixed the JSON class to prevent it from removing leading or trailing spaces from JSON values
- Fixed duplicate events sent by a CAT240 subscriber
- Fixed an issue when disconnecting a pub/sub connection
- Fixed the BACnet connector/adapter issue when the configuration file contains a large value for the Period key
- Fixed an issue when stopping the database subscriber connector/adapter
- Fixed the database connector/adapter to repeat the logic to skip the repeat interval when stopped
- Fixed a lack of responsiveness in the database connector/adapter publisher when stopping the connector
- Fixed an issue in the HTTP plug-ins support when multiple requests initialize the plug-in simultaneously
- Changed the HTTP code to support instant socket shutdown after a response when the Connection: close request header is specified
- Fixed a lack of responsiveness when a connection to the HTTPS port did not send data
- Added support for multiple parameter values for the same name in URLs
- Added support for multi-threaded web socket readers
- Fixed JSON parsing to create numeric values when appropriate
- Returned an error from the web socket client if a URL request gets an error response
- Fixed an issue when capturing logs from ESP Studio
- In the PI Web connector/adapter publisher with the ALLVALUESTOSTRINGS parameter enabled, removed quotation marks from published values
- Configured the adapter connection to base64 to encode the command-line arguments
- Fixed a JSON escape issue with multiple backslashes
- In the QuasarDB connector/adapter publisher, corrected the prune range specified after de-duplicating
- Configured the dfesp_cas_adapter to check whether a CAS table is already loaded prior to loading the table from a SASHDAT file
- Configured HTTP connections to support the "100 Continue" interim response for clients that request it
- Configured the database connection to close after the database connector publisher finishes
- In the PI Web connector/adapter subscriber, accepted the HTTP status 207 response to the POST request and to log response content at the warn level
- In the PI Web connector/adapter subscriber, copied the subscribed window timestamp field to the JSON Timestamp field sent in POST
- Fixed an issue when running a pub/sub client with the max queue size configured
- Fixed an issue in the serialize function of the Java pub/sub API in which event data is returned only the first time serialize is called
- Fixed an issue with analytic models failing to load in tksamas.so when you apply the hot fix from SAS Note 68350
- Fixed an issue where an analytic store file greater than 2 GB could not be loaded into a SAS® Micro Analytic Service store
Enhancements:
- Added Asterix CAT240 radar video data support to the file/socket connector/adapter
- Enhanced the dfesp_cas_adapter to load a CAS table from a SASHDAT file, if present
- Added the BUFSIZE configuration parameter for the dfesp_rest_subsciber adapter
- Added the RESPOPAQUEJSON and RESPUSEINSERT configuration parameters for the dfesp_rest_subscriber adapter
- Added the SEARCHFULLHEIRARCHY configuration parameter for the PI Web connector/adapter
- Enhanced PI Web subscriber POST requests to implement bulk Writes to improve performance
- Added the optional DEDUPLICATE parameter to the QuasarDB publisher connector/adapter and applied the INRANGESTARTREL parameter to every select operation
- In the QuasarDB connector/adapter publisher, inserted an IN RANGE clause before WHERE and/or other further clauses
- In the MQTT subscriber connector/adapter, wrote MQTT messages to a dynamic topic matching the contents of the event field configured in the MQTTTOPIC parameter
- In the database connector/adapter Oracle logminer mode, included the row ID in a sql_where field and required the rowid string field in the source window schema
- Enabled the subscriber connector DOUBLEPRECISION parameter to control the number of precision digits printed for ESP doubles in JSON output; the default value is 6
- In the Kafka subscriber connector/adapter, expanded the FIELDTOKAFKAKEY functionality to AVRO, OPAQUESTRING, and CSV formats
- In the timer connector/adapter, added the MILLISECOND option for the UNIT parameter
- Added encryption support to the OPCUA connector/adapter to fix user name and password authentication
- In the Kafka publisher connector/adapter, added support to save Kafka message offset and partition to source window fields
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
Operating System and Release Information
SAS System | SAS Event Stream Processing Engine | Microsoft® Windows® for x64 | 6.2 | 6.2 | | |
Linux for x64 | 6.2 | 6.2 | | |
SAS System | SAS Event Stream Processing for Edge Computing | Linux for AArch64 | 6.2 | 6.2 | Viya | Viya |
Linux for x64 | 6.2 | 6.2 | Viya | Viya |
*
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.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2024-01-10 16:57:03 |
Date Created: | 2021-09-22 16:17:08 |