Solace PubSub+ Monitor

Version 5.2.1 Release Notes

23877: Deliverable renamed to SolacePubSubMonitor

The Solace PubSub+ Monitor deliverable has been refactored in the following ways 1) The file name is now SolacePubSubMonitor instead of RTViewSolaceMonitor 2) projects/rtvservers.dat has been replaced by a unique rtvservers.dat within each project directory 3) rtvapm/solmon/webapps and rtvapm/rtvmgr/webapps include a copy of all servlets that can be used to rebuild the servlets under apache*/webapps 4) libraries, scripts, and configuration files relating to unused components have been removed to reduce file size 5) an Amazon EC2 image is no longer being provided 6) the RTView Manager dashboard has been updated to a new HTML UI. The new UI is available at: http://HOST:8068/rtview-manager 7) the bin/stop_servers.[bat/sh scripts] now require the use of the -eval argument to stop any HSQLDB database servers that were started by using the -eval argument with bin/start_servers.[bat/sh]

Alerts

23611: Clear button added to Alerts tab

A button labeled "Clear" has been added to the row of buttons near the top of the Alerts tab, A click on the button will set the Cleared flag on the selected alert(s). The button is enabled if one or more alerts are selected which are not already cleared, otherwise it is disabled.

24225: Ease of use enhancements for Alert notifications

A drop-down list of $alertValues was added to the Subject and Body fields of the email alert notification dialog in the Configuration Application.

24385: Changes to alert notification Java Commands were not saved the first time

A change was made to ensure that alert notifications using the default Java type do not contain blank entries in the properties file.

24654: ArrayIndexOutOfBoundsException with 20,000+ alerts

A problem has been fixed which sometimes caused the data server to throw an ArrayIndexOutOfBoundsException, and then grow unresponsive, when removing rows from a cache table.

Configuration

23789: Support Secure Connections to Solace in Configuration Application

The Configuration Application has been enhanced to support connections to secure Solace Brokers. For connections to Cloud Brokers, use an https url in the Connection dialog. For connections to non-Cloud Brokers, turn on the SSL Connection toggle in the Connection dialog. Then go to the Security tab and fill in the SSL Credentials section with the appropriate truststore and truststore password values for your Brokers.

24266: Display server tab removed from Configuration Application for some products

The Configuration Application for SolacePubSubMonitor and TIB_rtview-as Monitor have been enhanced to remove the Display Server tab as it is not used by those products.

24285: Merge memory and jmx jvm arguments instead of appending them

The jvm argument handling has been enhanced to produce a simpler command line output. In previous releases, both the default and the project specific values for the following jvm arguments were included in the command line: -Xmx -Xms -Dcom.sun.management.jmxremote.* This did not cause any functional changes as the last (right-most) value in the command line takes precedence. However, it made the command output confusing to users who were trying to determine which jvm argument values were in use based on the process command. The jvm argument handling has been enhanced so that only one value (previously, the right-most value) is output for the above jvm arguments.

24334: Added soleventmodule configuration to Config UI

The Configuration Application for Solace has been enhanced to include the Solace Event Module configuration. In previous releases, this configuration was read from the rtvapm/solmon/soleventmodule/config/soleventmodule.properties files. Those properties are now stored in the project properties. Upgrade Notes Upgrading customers will not need to do anything to transfer their properties from the old soleventmodule.properties file to the project properties. During upgrade, copy your old soleventmodule.properties into the rtvapm/solmon/soleventmodule/config/soleventmodule.properties directory in the new installation, then run as usual. The first time the Configuration Application is used, these properties will be tranfered over to the project properties. After that, the soleventmodule.properties file will no longer be used.

24394: Improved wording of Solace PubSub+ Event Broker toggle in Config UI

Text describing the Solace PubSub+ Event Broker as service toggle in the Configuration Application was enhanced for clarity.

24537: soleventmodule log4j2.properties moved to projects\rtview-server\soleventmod.log4j2.properties

The rtvapm\soleventmodule\config\log4j2.properties file, which controls the logging settings for the SolEventModule, is now included under the projects\rtview-server directory and has been renamed to soleventmod.log4j2.properties. In previous releases, this file was only available under rtvapm\soleventmodule\config and users were instructed to modify it there. As of this release, changes to the SolEventModule logging must be configured in the projects\rtview-server\soleventmod.log4j2.properties file, not in rtvapm\soleventmodule\config\log4j2.properties This was done as part of a larger project to make upgrading easier in version 5.0+ by limiting user changes to files under the projects directory. Upgrade Notes For upward compatibility, if the projects\rtview-server\soleventmod.log4j2.properties file is not found, the rtvapm\soleventmodule\config\log4j2.properties file will be used instead. However, users upgrading from previous versions who have modified the logging settings should apply their logging changes to the soleventmod.log4j2.properties file in projects\rtview-server in order to make it easier to upgrade to future releases.

24538: sl.log4j.properties copied to projects

The sl.log4j.properties file, which controls the logging settings, is now included under the projects directory. In previous releases, this file was only available under rtvapm\common\conf and users were instructed to modify it there or to copy it to their project directory. As of this release, changes to the logging must be configured in the projects\sl.log4j.properties file, not in rtvapm\common\conf\sl.log4j.properties. This was done as part of a larger project to make upgrading easier in version 5.0+ by limiting user changes to files under the projects directory. Upgrade Notes For upward compatibility, if the projects\sl.log4j.properties file is not found, the rtvapm\common\conf\sl.log4j.properties file will be used instead. However, users upgrading from previous versions who have modified the logging settings should apply their logging changes to the sl.log4j.properties file in projects instead of the copy under rtvapm\common\conf in order to make it easier to upgrade to future releases.

24551: Enhanced update_wars with option to secure rtvquery servlet

If the update_wars scripts are called with the new argument "-secure" then the rtvquery war will be updated with security enabled. (A version of the web.xml file with the security section uncommented will be used).

24648: Restore scroll position after closing dialog in Config UI

The Configuration Application has been enhanced to restore the scroll position after opening a dialog on the following pages: - Alerts - Databases - Security - Apache Kafka CONNECTIONS - Solace CONNECTIONS

24688: Default text now editable in Configuration Application

The behavior of the default value in text entry fields in the Configuration Application has been enhanced. Text entry fields that are set to the default value show the default value in gray to indicate that it is the default. When you click on it, the text now becomes editable to make editing default values easier. To return to the default, delete the edited text.

24796: Enhanced sample app for editing properties

The sample application for editing properties (rtvapm/sampleapps/propeditor) has been enhanced for ease of use. The host, port and path variables can now be set from environment variable and the installation process has been simplified. See the README.txt in the sample application's directory for more details.

Customization

23816: Added getExtendedSolEventAlertInfo to example custom command

The custom java command handler for alert notifications has been enhanced to include an example of how to get additional information about SolEventModule alerts from the SolEventModuleAlerts cache. To enable this sample code: 1. Edit projects\custom\src\com\sl\rtvapm\custom\RtvApmCommandHandler.java to uncomment the if statement that calls getEventModuleInfo at the end of the outputAlertNotification method and also uncomment the getEventModuleInfo method. 2. Edit projects\custom\src\make_all.bat or make_all.sh to add RTVAPM_HOME/rtvapm/solmon/lib/rtvapm_solmon.jar to the CP 3. Run make_all.bat or make_all.sh to rebuild the jar 4. In the RTView Configuration, configure your alert notifications to execute a java command - this will generate a message in the data server log file for each alert notification. For SolEventModule alerts, there will be a second message containing the information from the corresponding row in the SolEventModuleAlerts cache.

Deployment

24425: Removed HSQLDB runtime error

A spurious "unable to getSchema" error generated by the HSQLDB database has been suppressed.

Distribution

24576: RTView Manager application refreshed

The RTView Manager application in SolacePubSubMonitor and RTViewCentral has been updated as follows: 1. The classic user interface has been replaced with the html user interface. The url is now host:port/rtview-manager and it requires login. You can login as rtvadmin (rtvadmin) or rtvuser (rtvuser). 2. In SolacePubSubMonitor, connections to components that are no longer included in the deliverable have been removed. 3. In SolacePubSubMonitor, the RTView Manager used to share a database and rtvservers.dat script with the solace monitor. It now has it's own database and rtvservers.dat script. 4. In RTViewCentral, the rtvservers.dat file has changed and custom_setup.bat and custom_setup.sh have been added. Upgrade Notes ============ The rtview-manager directory is not typically customized in RTViewCentral or SolacePubSubMonitor. In the case where this directory was customized, upgrading users should re-apply their changes to the new rtview-manager project and not just override the directory with the old version of the rtview-manager directory.

General

24115: Support form-based auth in HTML UIs

The user login mechanism has been enhanced: 1) The login prompt now uses a page with product branding, rather than the generic popup window. 2) The user can now logout without closing the browser. The appearance of the top banner on the login page varies by product: - For rtview-central and rtview-manager, the banner is dark blue and contains the SL logo and text "RTView© Login" - For rtview-*-rtvadmin (Config UI), the banner is dark blue and contains the SL logo and text "RTView© Project Configuration - Login" - For Tibco-branded UIs (rtview-emsmon, rtview-bwmon, rtview-tdgmon), the banner is medium blue and contains the text "TIBCO(tm) RTView©" - For rtview-solmon, the banner is a black-gray gradient and contains the Solace logo and text "PubSub+ Monitor" In all cases the browser tab title is simply "Login" with no favicon. Logout is performed by clicking on the user name in the top right corner of the UI and then confirming in a popup window. After logging out, a page appears containing the text "Logged out" and a link to return to the login page. Note that closing the browser tab does not perform a logout, so navigating to the UI in another tab afterwards in the same browser will not result in a login prompt. This is by design. If the UI is deployed using tomcat, and if you log in to the rtview UI (e.g. rtview-central) in one tab as rtvuser and then open the configuration tool (e.g. rtview-central-rtvadmin) in a second tab, you'll see the following: You don't have the required role to view this page. Click here to login as a different user. This occurs because the configuration tool requires the rtvadmin role. If you click the link, you'll be logged out in all tabs and can then log back in as a user with the rtvadmin role.

HTML UI

Components Displays

24512: Small version of Solace Brokers Table has no Expired column

The expired flag and time stamp columns have been added to the reduced version of the All Brokers Table.

Navigation

24514: Improved visibility of button to hide navigation panel

The background color of the "<<" button in bottom left corner of the UI (which hides the navigation panel) is now a darker gray color than the nav panel's background, to make it more obvious when it overlaps with items in the navigation tree.

RTView Core Functionality

24450: Deprecate support for Sybase database

RTView no longer supports Sybase database.

24604: Format the alert text to at most 2 decimal digits

The Alert Text in the Alert Table has been enhanced to format decimal values to 2 decimal digits.

Alerts

24756: Log message when alert table limit is exceeded

The alert engine was enhanced to print a warning when the alert count limit is exceeded. In previous releases this warning was only printed when logging was enabled.

Data Historian

24767: Improved Historian insertDataIntoDbTable performance for prepared statements

The performance of the historian has been improved. It now performs commits on batches of inserts, as defined by the historian's cache_size property, rather than one commit per insert. This reduces overhead in some databases. Also, in verbose mode a message is logged for each such commit as follows: ... committing the following number of records from cache: <N>, msec = M This matches the behavior of the historian before prepared statements were supported in release 4.2.

24768: Historian continues writing to database after connection is lost and restored

A problem has been fixed which sometimes caused the historian to stop storing data after the database connection was lost and then restored.

Data Sources

24707: New database ping feature added to SQL data source

An option named "dbping" has been added to the SQL data source. It can be used to specify a simple SQL query to be run periodically on a specified database connection. This is intended to keep the database connection alive on systems where idle connections are closed, for example by a firewall between the host running RTView and the database server's host. Typically a simple database vendor-specific query would be used for this purpose. For example: Oracle: SELECT 1 FROM DUAL SQL Server: SELECT COUNT(*) FROM SYSOBJECTS MySQL: SELECT 1 The dbping option is specified in an RTView properties file as follows: sl.rtview.sql.dbping=name=N;interval=I;query=Q where: N = the database connection name (required) I = ping interval in seconds (optional, default = 300) Q = sql query for ping (required) For example: sl.rtview.sql.dbping name=MyOracleDB;interval=600;query=SELECT 1 FROM DUAL As with all periodic sql queries in RTView, the query is not guaranteed to be performed at the exact interval specified but within a few seconds. In RTView Enterprise, the dbping property can be added on the CUSTOM PROPERTIES tab of the Configuration Application. For example, the following could be specified for use on the RTView history database connection for an Oracle database: Name: sl.rtview.sql.dbping Value: name=RTVHISTORY;interval=600;query=select 1 from DUAL Filter: dataserver

General

24706: Pinger feature added to rtvquery servlet

The rtvquery servlet will now ping the data server after 5 minutes of inactivity. (The connection is inactive when no web clients are actively sending queries to the servlet). The ping is intended to keep the servlet's connection to the data server alive on systems where idle connections are automatically closed, for example by a firewall between the host running tomcat and the data server's host. If the interval needs to be changed, add the following property to the rtvquery.properties file: PingerIntervalSec=N where N is the desired interval in seconds, or 0 (zero) to disable the ping feature.

RTView Manager

24484: Upgraded Tomcat caches to support Tomcat 7 and 8, drop support for Tomcat 6

The Tomcat caches have been enhanced to support monitoring Tomcat 8 and to drop support for Tomcat 6. The following columns in the TomcatWebModuleStats and TomcatWebModuleTotals caches are not supported for Tomcat 8. They will show 0 for Tomcat 8 connections, but will show correct data for Tomcat 7: desiredEntryAccessRatio maxAllocateIterations spareNotFoundEntries The state column in the TomcatWebModuleStats and TomcatWebModuleTotals caches is not supported for Tomcat 7 or 8, but was left in for upward compatibility. It will always show a value of 1. The xmlNamespaceAware column was removed from the TomcatHostInfo cache and the bufferSize and maxSpareThreads columns were removed from the TomcatConnectorInfo cache. These columns are not supported for Tomcat 7 or 8 and removing them will not impact upward compatibility.

Scripts

22858: Classpath fields now check if path ends with .jar before adding /*

The Configuration Application has been enhance to handle .jar file names in the Classpath Directory fields for all solution packages. In previous releases, these were incorrectly used as directory names.

Solution Package for Solace PubSub+

24861: Increased precision of some columns in Broker Capacity table

The number of decimal places has been increased for the following columns in the Broker Capacity table: Ingress Flow Count % Ingress Flow Count HWM % Spool Files Used % Spool Files Used HWM %

24077: VARCHAR limits in "name" columns increased in database schemas

The VARCHAR limits of "name" columns in the database schemas have been increased from 100 to 255 to allow more flexibility with long names. Users do not need to make any changes to their existing database records.

24106: Force VPN name when adding a cloud connection

Solace PubSub+ Cloud broker connections now require the use of a VPN name.

24116: Dynamic connection updates via rest API now supported for StatsPump DS

The StatsPump data collection now supports updating connection properties via rest api. A sample application that shows how to use the rest api is available under rtvapm\sampleapps\propeditor. See the README.txt in that directory for instructions on using the rest api. You can also refer to the "Property Editor REST API" section of the User Guide for more details. LIMITATION: Connections that are removed will not consistently display as Expired in all displays, particularly the Brokers and Capacity screens. Removed items will be reliably deleted in all screens according to the configured Delete Time.

24158: SolEventModule typo for BLACKLIST

Previously there was a bug filtering events and alerts by the priority of BLACKLIST. This has been fixed.

24318: SolGuaranteedMsgingNoMsgSpoolAdActive improvements

The SolGuaranteedMsgingNoMsgSpoolAdActive alert has been fixed to be associated per Message Router. This alert will now be triggered on the two brokers that are redundancy configured as an HA pair when the operational status of their message spool is not AD-Active on any of the two brokers. This alert now correctly has a CI Type, and drilling down on this alert will load the Solace Broker Spool Table.

24322: Platform now collected correctly for all SEMP versions

Platform is now being correctly gathered for all supported SolOS versions.

24341: Msg ingress/egress alerts switched from %utilization to Msg/s

SolMsgRouterMsgEgressUtilHigh and SolMsgRouterMsgIngressUtilHigh alerts have been removed from the list of available alerts, as they incorrectly assumed a hardcoded maximum value in order to compute a percentage of utilization. Two new alerts, SolBrokerEgressMsgRateHigh and SolBrokerIngressMsgRateHigh, have been introduced to alert on the ingress and egress message rates. The units of these two new alerts are messages per second. Upgrade Notes: - To remove the unused alerts from the Alert Admin page, remove all entries for SolMsgRouterMsgEgressUtilHigh and SolMsgRouterMsgIngressUtilHigh from the ALERTDEFS ALERTLEVELS database table. Configure thresholds and overrides for the new alerts in the Alert Administration. - If you have enabled alert persistence, remove SolMsgRouterMsgEgressUtilHigh and SolMsgRouterMsgIngressUtilHigh from the ALERT_PERSIST_TABLE and ALERT_PERSIST_TABLE_CENTRAL or you will see errors about these alerts in the log file at startup. Also note that if you have stored alert history, the old alert will be in the alert history. It is up to user discretion whether to keep the old alerts in history or not.

24391: New alerts for redundancy misconfiguration and activity status change (deprecates SolHAPairFailoverDetected)

SolBrokerRedundancyDown and SolBrokerRedundancyActivityStatusChanged alerts have been implemented to detect redundancy misconfiguration and changes in the activity state of brokers configured for redundancy. These alerts will be only executed for brokers that are detected as being configured for redundancy due to either the existence of its mate router name or because they have been explicitly defined as configured for redundancy. Explicitly defining brokers as being redundancy configured is only required when the monitor has not succeeded on detecting the brokers as configured for redundancy. To verify whether the monitor has detected all brokers configured for redundancy correctly, go to the Admin > Cache Table display and select the _SolBrokerRedundancy cache in the upper table. Verify in the lower table of this display that all brokers redundancy configured have the IsHABroker flag checked. If that is not the case, you need to specify the mate router name in the redundancy configuration of each broker. The SolBrokerRedundancyDown alert verifies that redundancy is configured properly by checking whether Redundancy Mode, Redundancy Status and Configuration Status are valid. That is, the Redundancy Modes is either Active/Active or Active/Standby, the Redundancy Status is Up and the redundancy Configuration Status is Enabled. If any of these conditions is not met, then an alarm alert will be raised with the following alert text: "<hostname> is not properly configured for redundancy or redundancy is down. Redundancy Status: <a> Configuration Status: <b>", where <hostname> is the hostname of the offending broker and <a> and <b> are the current Redundancy Status and Configuration Status of the broker respectively. The SolBrokerRedundancyActivityStatusChanged alert checks whether the previous state of the Active-Standby Role, the Activity Status of the Primary Virtual Router and the Activity Status of the Backup Virtual Router is different from the current state. If they are different, that implies a change in the state of the redundancy status occurred and a warning alert will be triggered. As soon as the previous and the current redundancy state is stabilized, the warning alert will be automatically cleared, indicating in the alert text the current and previous states being detected. The warning alert contains the following text: "<hostname> has changed its redundancy activity state. There might be untracked intermediate states from the ones that have been detected. Current state: <A> Previous state: <B>", where <A> and <B> are the concatenation of active-standby-role, primary-status-activity, and backup-status-activity separated by the character "-" for current and previous states. Best Practices & Troubleshooting * It's possible to have multiple SolBrokerRedundancyActivityStatusChanged warning alerts when failing over if intermediate states have been collected. For instance, if the changes from Local Active to Local Inactive to Shutdown are detected, then two SolBrokerRedundancyActivityStatusChanged warning alerts will be executed in this broker and will have two warnings from one broker and one from the other broker if the intermediate state on the second broker was not gathered due to polling interval being longer than the time the broker changes its redundancy state. If you only want one warning alert per broker per failover operation, the recommended action is to increase the duration of the alert. This value will vary depending on data collection latency and is system dependent. On the other hand, if you need to keep track of all intermediate states of the failover operation, then you should decrease the polling interval for the show redundancy detail poller. This is not recommended as might overflow the data collector with requests that cannot be successfully completed or preventing sending other monitoring data regarding other aspects of the broker due to the existence of requests too-often repeated. * Due to SolBrokerRedundancyActivityStatusChanged warning alert being a transient alert which will be automatically cleared when the redundancy status is stabilized, enabling both alerts is recommended as SolBrokerRedundancyDown can stay uncleared if manual intervention for fixing redundancy misconfiguration or non-functioning is required.

24404: SolMsgRouterTranSessionCntUtilHigh no longer using a deprecated metric

SolMsgRouterTranSessionCntUtilHigh previously used a deprecated metric from Solace. It now uses the result of: (Transaction-sessions-used/Max-transaction-sessions) * 100

24443: Replaced Pending Messages by Spooled Messages across displays

"Pending Messages" labels across all Solace PubSub+ monitor displays have been renamed to "Spooled Messages."

24455: New SEMP schemas (9.3+)

The SEMP schemes for 9.3 and 9.3.1 versions have been included.

24461: Solace Config UI no longer allows creation of incorrectly formatted connections

Enhancements have been made to the Solace connections dialog in the Configuration Application to ensure that all required fields have data entered before the connection can be saved.

24464: Client integer metrics changed to long

Integer client metrics have been updated to long type. To update these metrics in their corresponding tables in history, execute the following "alter table" SQL sentences. Work with your database administrator on the optimal way to make these changes. DB2/HSQLDB ALTER TABLE "SOL_MESSAGE_SPOOL" ALTER COLUMN "ingress-flow-count" SET DATA TYPE BIGINT; ALTER TABLE "SOL_MESSAGE_SPOOL" ALTER COLUMN "queue-topic-subscriptions-used" SET DATA TYPE BIGINT; ALTER TABLE "SOL_MESSAGE_SPOOL" ALTER COLUMN "spool-files-total-used" SET DATA TYPE BIGINT; ALTER TABLE "SOL_MESSAGE_SPOOL" ALTER COLUMN "transacted-sessions-used" SET DATA TYPE BIGINT; ALTER TABLE "SOL_APPLIANCE" ALTER COLUMN "num-messages-spooled" SET DATA TYPE BIGINT; ALTER TABLE "SOL_APPLIANCE" ALTER COLUMN"total-clients-connected" SET DATA TYPE BIGINT; ALTER TABLE "SOL_ENDPOINT" ALTER COLUMN "num-messages-spooled" SET DATA TYPE BIGINT; ALTER TABLE "SOL_VPN" ALTER COLUMN "connections" SET DATA TYPE BIGINT; ALTER TABLE "SOL_VPN" ALTER COLUMN "total-unique-subscriptions" SET DATA TYPE BIGINT; ALTER TABLE "SOL_VPN" ALTER COLUMN"num-messages-spooled" SET DATA TYPE BIGINT; MySQL ALTER TABLE "SOL_MESSAGE_SPOOL" MODIFY "ingress-flow-count" BIGINT; ALTER TABLE "SOL_MESSAGE_SPOOL" MODIFY "queue-topic-subscriptions-used" BIGINT; ALTER TABLE "SOL_MESSAGE_SPOOL" MODIFY "spool-files-total-used" BIGINT; ALTER TABLE "SOL_MESSAGE_SPOOL" MODIFY "transacted-sessions-used" BIGINT; ALTER TABLE "SOL_APPLIANCE" MODIFY "num-messages-spooled" BIGINT; ALTER TABLE "SOL_APPLIANCE" MODIFY "total-clients-connected" BIGINT; ALTER TABLE "SOL_ENDPOINT" MODIFY "num-messages-spooled" BIGINT; ALTER TABLE "SOL_VPN" MODIFY "connections" BIGINT; ALTER TABLE "SOL_VPN" MODIFY "total-unique-subscriptions" BIGINT; ALTER TABLE "SOL_VPN" MODIFY "num-messages-spooled" BIGINT; SQL Server ALTER TABLE [SOL_MESSAGE_SPOOL] ALTER COLUMN [ingress-flow-count] BIGINT; ALTER TABLE [SOL_MESSAGE_SPOOL] ALTER COLUMN [queue-topic-subscriptions-used] BIGINT; ALTER TABLE [SOL_MESSAGE_SPOOL] ALTER COLUMN [spool-files-total-used] BIGINT; ALTER TABLE [SOL_MESSAGE_SPOOL] ALTER COLUMN [transacted-sessions-used] BIGINT; ALTER TABLE [SOL_APPLIANCE] ALTER COLUMN [num-messages-spooled] BIGINT; ALTER TABLE [SOL_APPLIANCE] ALTER COLUMN [total-clients-connected] BIGINT; ALTER TABLE [SOL_ENDPOINT] ALTER COLUMN [num-messages-spooled] BIGINT; ALTER TABLE [SOL_VPN] ALTER COLUMN [connections] BIGINT; ALTER TABLE [SOL_VPN] ALTER COLUMN [total-unique-subscriptions] BIGINT; ALTER TABLE [SOL_VPN] ALTER COLUMN [num-messages-spooled] BIGINT;

24469: Support filtering by Topic Endpoint or by Queues

A new drop down for filtering out Solace Queues and Topic Endpoints has been added to the Endpoints Table display.

24474: Include hostname in 'Alert Text' field of SolMsgRouterNotConnected

The SolMsgRouterNotConnected alert now includes the hostname in the alert text.

24499: Fixed missing Provisioning info for hardware brokers

A bug in displaying the hardware provisioning details (Chassis serial number, BIOS version) for hardware message routers has been fixed. Due to the changes made on the SEMP schemas for software brokers, the hardware information will show blank for software brokers. For additional information, refer to Solace documentation.

24508: 'Client Summary' page now showing correct values

Fixed a bug in the collection of client metrics. With the fix, the Single Client Summary will display correctly activity in trends as well as provide the metrics from the last update period in the case the Client went down. To identify whether the Client is still generating activity and the data collection is proceeding normally, verify the Expired field of the Client is false. Otherwise, when Expired is true, the data provided in the display will reflect the metrics delivered from the last update time, when the information was successfully collected. Notice that trends might not show any activity with current preset time of 15 min when the Client stopped earlier to this time frame. To detect whether the transient activity of the Client was registered properly, extend the time range of the trends in the Client Summary display to a broader period.

24518: Addressed collision of Topic Endpoint and Queue Endpoint with same name

The SolEndpoints and SolEndpointStats have been fixed to account for Queue and Topic Endpoints with the same name. If that case occurs, then the Queue name will remain the same and the suffix "-TE" will be concatenated to the Topic Endpoint name to resolve the similarity. This will only take effect when the Queue and the Topic Endpoint belong to the same broker and VPN. No upgrading instructions are required.

24520: SolSparseMsgSpool alert now accounts for disk space utilization

Fixed a bug in the execution of the SolSparseMsgSpool alert. With the fix, this alert will trigger a warning alert (Severity 1) when the active disk partition usage is above 30% and the ratio between disk utilization and current persistent utilization is larger than 3. Further reading about this condition can be reached from Solace’s site, Section on diagnosing the sparse message spool file condition at: https://docs.solace.com/Configuring-and-Managing/Mon-Mgmt-Disk-Con.htm

24522: Calculated rates in Broker displays no longer zero when collected with Stats Pump

Fixed a bug in the calculation of client rates for direct, persistent, and non-persistent messages, and bytes received and sent. The fixed metrics are: cl-direct-bytes-rcvd cl-direct-bytes-sent cl-direct-msgs-rcvd cl-direct-msgs-rcvd-per-sec cl-direct-msgs-sent cl-direct-msgs-sent-per-sec cl-non-prst-bytes-rcvd cl-non-prst-bytes-sent cl-non-prst-msgs-rcvd cl-non-prst-msgs-rcvd-per-sec cl-non-prst-msgs-sent cl-non-prst-msgs-sent-per-sec cl-prst-bytes-rcvd cl-prst-bytes-sent cl-prst-msgs-rcvd cl-prst-msgs-rcvd-per-sec cl-prst-msgs-sent cl-prst-msgs-sent-per-sec egress-compression-ratio ingress-compression-ratio tcp-fast-retransmit-sent total-cl-bytes-rcvd total-cl-bytes-sent total-cl-msgs-rcvd total-cl-msgs-rcvd-per-sec total-cl-msgs-sent total-cl-msgs-sent-per-sec total-clients total-clients-connected total-egress-discards total-egress-discards-per-sec total-ingress-discards total-ingress-discards-per-sec cl-direct-bytes-rcvd-per-sec cl-direct-bytes-sent-per-sec cl-non-prst-bytes-rcvd-per-sec cl-non-prst-bytes-sent-per-sec cl-prst-bytes-rcvd-per-sec cl-prst-bytes-sent-per-sec total-cl-bytes-rcvd-per-sec total-cl-bytes-sent-per-sec avg-egress-byte-per-min avg-egress-comp-per-min avg-egress-per-min avg-egress-ssl-per-min avg-egress-uncomp-per-min avg-ingress-byte-per-min avg-ingress-comp-per-min avg-ingress-per-min avg-ingress-ssl-per-min avg-ingress-uncomp-per-min current-egress-byte-per-sec current-egress-comp-per-sec current-egress-per-sec current-egress-ssl-per-sec current-egress-uncomp-per-sec current-ingress-byte-per-sec current-ingress-comp-per-sec current-ingress-per-sec current-ingress-ssl-per-sec current-ingress-uncomp-per-sec egress-comp-bytes egress-ssl-bytes egress-uncomp-bytes ingress-comp-bytes ingress-ssl-bytes ingress-uncomp-bytes

24525: Brokers now appearing in Brokers Table when both NOT_RUNNING and FAILURE statuses are present

Fixed a bug that preventing some Solace Brokers from appearing in in the Solace Brokers Table. The issue was related to the variations in the failure code returned by different SEMP versions. For debugging purposes, a new set of auxiliary caches have been introduced. Each of these auxiliary caches provides a self-explanatory flag indicating one Broker condition.. The list of auxiliary caches and the flags supported is the following: 1. _SolBrokerSystemHardwareRaw (IsSoftwareBroker flag) 2. _SolBrokersConnected (Connected flag) 3. _SolBrokersEndpoints (HasEndpoints flag) 4. _SolBrokerBridges (HasBridges flag)) 5. _SolBrokerRedundancy (IsHABroker flag) 6. _SolBrokerClientStatsRaw (HasClients flag) 7. _SolBrokerVpns (HasVPNs flag)

24558: Differentiate unexpired endpoints in the 'Broker Summary' page

The Solace Broker Summary display has been enhanced to show Unexpired / Total Endpoints instead of only the Total Endpoints.

24585: Use defaults if group_sl.xml and poller_sl.xml not in project directory

In previous releases, the Data Server monitoring Solace PubSUb+ crashed if the pollers_sl.xml and groups_sl.xml files were missing from the project directory. This has been fixed. If these files are missing, the defaults are used instead.

24606: Reduced polling rate of StatsPump to 30 seconds

We changed the mandatory poller update rates in the StatsPump from 5 to 30 seconds. As part of this change, a JVM heap dump will now be generated in the case of an OutOfMemory error.

24612: Remove HA pair specification from Solace Connection properties

The Solace connections have been enhanced to remove the HA connection type. HA connections from previous versions will automatically be split into 2 standalone connections. The primary server from the HA connection will use the same name as the HA connection. The backup server from the HA connection will use the same name as the HA connection with a -B appended.

24634: Blank brokers aren't listed in All Brokers Table

Fix a bug preventing Solace Brokers that did not have endpoints from being listed in the All Brokers Table display.

24639: Hardware metrics now correctly reporting for older schemas

A bug in the directory structures of the supported SEMP schemas was causing information (BIOS version, chassis product number, chassis revision, and chassis serial.) about some Solace Hardware Message Routers running older schemas (< 9.3) to be missing. This has been fixed.

24643: Capacity metrics adjusted to not use default values as a benchmark

The following estimates that were used to compute percentages of utilization for capacity displays have been deleted: qt-subscriptions-max max-ingress-per-sec max-egress-per-sec max-ingress-byte-per-sec max-egress-byte-per-sec Similarly, the spool disk size is now being collected from the 'show message-spool detail' SEMP request. LIMITATION On the Broker Capacity Summary display, Egress and Ingress Bytes/s, and Egress and Ingress Msgs/s, now appear in tooltips as the actual rates and not the percentage of utilization calculated from an estimated maximum rate. This change causes the bars on the Broker Capacity Summary display, which expect a value of 0 to 100, to be visually misleading.

24667: Corrected endpoints column in the "Solace Broker Table" page

The current number of endpoints per Solace broker in the Brokers Table display is now correct.

24671: SolSparseMessageSpoolFile alert improved to account for boundary conditions

The SolSparseMessageSpoolFile alert has been adjusted to use a different metric to compute the sparse ratio. The metric current-persist-usage-mb has been replaced by current-disk-usage. Moreover, the metrics involved in this alert have been converted from long to double to account for reduced spool utilization that can deliver a ratio above 3 but are below 1MB and therefore missed when the metrics are converted from blocks to MB.

24716: Corrected invalid sample soleventmodule filters

The SolaceEventModule contains several sample Alert Filters. The System + VPN - VPN Resource Util filter previously used invalid wildcard XPath syntax: severityCode>=5, scope='CLIENT', eventName='VPN_RDP_RC_CONN_DOWN', eventName='VPN_RDP_RC_DOWN', eventName='VPN_RDP_RDP_DOWN', scope='VPN' and (eventName='*_HIGH' or eventName='*EXCEED' or eventName='EXCEEDED') This has been updated to use correct XPath 1.0 syntax: severityCode>=5, scope='CLIENT',eventName='VPN_RDP_RC_CONN_DOWN', eventName='VPN_RDP_RC_DOWN', eventName='VPN_RDP_RDP_DOWN', scope='VPN' and (substring(eventName,string-length(eventName)-4)='_HIGH' or substring(eventName,string-length(eventName)-6)='_EXCEED' or substring(eventName,string-length(eventName)-8)='_EXCEEDED')

24735: StatsPump datasource performance optimized

The Solace PubSub+ Monitor's datasource has been enhanced to reduce contention and improve throughput of messages from the statspump, leading to better GC (Garbage Collection) behavior and performance in the "consumer - producer" relationship between statspump and the datasource. It has also been enhanced to tune individual statspump parameters by means of system properties (that can be set as custom properties in the Configuration UI for the data server). STATS_PUMP.MISSED_SEMP_POLL_LIMIT STATS_PUMP.MAX_POLLER_RUN_LIMIT_FACTOR STATS_PUMP.HOSTNAME_POLLER_INTERVAL_SEC STATS_PUMP.REDUNDANCY_POLLER_INTERVAL_SEC STATS_PUMP.VPN_DETAIL_POLLER_INTERVAL_SEC STATS_PUMP.MSG_SPOOL_POLLER_INTERVAL_SEC STATS_PUMP.REACHABLE_POLLER_INTERVAL_SEC STATS_PUMP.BLOCKING_QUEUE_TOTAL_CAPACITY Reducing the Queue Size, controlled by the STATS_PUMP.BLOCKING_QUEUE_TOTAL_CAPACITY system property has been found to be beneficial in reducing memory usage and GC issues. For example, setting the property sl.rtview.jvm to the value -DSTATS_PUMP.BLOCKING_QUEUE_TOTAL_CAPACITY=1000 with the filter collector via the config UI would reduce the internal queue length to 1000 and result in the following entry in the project.properties collector.sl.rtview.jvm=-DSTATS_PUMP.BLOCKING_QUEUE_TOTAL_CAPACITY=1000

24741: SolMsgRouterSwapUsedHigh alert now disabled for hardware appliances

SolMsgRouterSwapUsedHigh alert is now exclusively enabled for SW Brokers and it will not execute for HW Brokers.


24742: Blank brokers now appear in the brokers table

A bug that prevented brokers from appearing in the All Brokers Table display when they were all blank brokers (no clients, bridges, vpns and endpoints) has been fixed.

24747: SolMsgRouterSubscriptionUtilHigh alert refined for queue subscription utilization

The SolMsgRouterSubscriptionUtilHigh alert has been reworked to compute the percentage of queue topic subscription utilization from the max-queue-topic-subscriptions configured value of each broker instead of using a global maximum estimated value. The max-queue-topic-subscriptions is obtained from 'show message-spool detail' SEMPv1 request. The following table column names have been changed: Message Router Capacity Table Old: Queue / Topic Subscriptions Used Queue / Topic Subscriptions Used % Queue / Topic Subscriptions Used HWM % Subscriptions HWM Transacted Sessions % Utilization Transacted Sessions HWM % Utiliztion New: Topic Subscriptions on Queue Used Topic Subscriptionson Queue Used % Topic Subscriptions on Queue Used HWM % Topic Subscriptions on Queue Used HWM Transacted Sessions Used % Transacted Sessions Used HWM % Message Spool Table Old: Queue/Topic Subscriptions Used Max Queue/Topic Subscriptions New: Topic Subscriptions on Queue Used Max Topic Subscriptions on Queue

24757: SolGuaranteedMsgingHbaLinkDown alert fixed

Fixed a bug in the firing of the SolGuaranteedMsgingHbaLinkDown alert. it should now correctly be triggered.

24759: SolGuaranteedMsgingMatePortDown alert now supports both HW and SW brokers

SolGuaranteedMsgingMatePortDown alert has been reworked to account for HW and SW Solace Brokers. The alert will execute when the broker is configured for Guaranteed Messaging and the ADB Link to Mate is down. Initially this alert used "show hardware details" to obtain the information regarding the mate link however this command is not supported on SW Brokers from SEMPv1 8.13 onwards. Limitation: This alert will not clear until a failover occurs.

24762: Updated event definitions for 9.4.0.78

The Solace Event Module has been updated to work with the syslog messages from the 9.4.0.78 Solace release.

24765: SEMP v9.4 schemas

Solace SEMPv1 schemas for Solace Appliance and SW Broker with version 9.4.0 have been included.

24774: Byte ingress/egress alerts switched from %utilization to Byte/s

SolMsgRouterByteEgressUtilHigh and SolMsgRouterByteIngressUtilHigh alerts have been removed from the list of available alerts, as they incorrectly assumed a hardcoded maximum value in order to compute a percentage of utilization. Two new alerts, SolBrokerEgressByteRateHigh and SolBrokerIngressByteRateHigh, have been introduced to alert on the ingress and egress message rates. The units of these two new alerts are messages per second. Upgrade Notes: - To remove the unused alerts from the Alert Admin page, remove all entries for SolMsgRouterByteEgressUtilHigh and SolMsgRouterByteIngressUtilHigh from the ALERTDEFS ALERTLEVELS database table. Configure thresholds and overrides for the new alerts in the Alert Administration. - If you have enabled alert persistence, remove SolMsgRouterByteEgressUtilHigh and SolMsgRouterByteIngressUtilHigh from the ALERT_PERSIST_TABLE and ALERT_PERSIST_TABLE_CENTRAL or you will see errors about these alerts in the log file at startup. Also note that if you have stored alert history, the old alert will be in the alert history. It is up to user discretion whether to keep the old alerts in history or not.

24778: Syslog alerts created/cleared at the same time no longer reappear

In previous releases, Cleared SolEventModule alerts were sometime regenerated. This has been fixed.

24789: Caches now have consistent delete behavior

Information on Appliances that are no longer monitored will now be removed from the displays after a user specified delay. Prior to the advent of dynamic (appliance) connections, Appliance caches did not need delete behavior, as Appliance connections were only added at startup for a given dataserver run. With the advent of dynamic connections, (appliance) connections may be added and removed at run-time. The consistent application of delete behavior ensures that (current) cache rows will be removed after the Delete Time has passed since the last data update. Removing an appliance connection will stop its associated data from updating and thus will be removed from caches after the Delete Time has passed since the last data update. Thus information on Appliances that are no longer monitored will be removed from the displays. The Delete Time can be specified in the Config UI The Delete Time should be longer than the expiry time. LIMITATION: Connections that are removed will not consistently display as Expired in all displays, particularly the Brokers and Capacity screens. Removed connections will be reliably deleted from all screens according to the configured Delete Time.

24797: Solace Event Module - Additional Fields are no longer parsed incorrectly

In previous releases of the Solace Event Module, the Additional Fields values were parsed incorrectly. This has been fixed.

24806: in sol_allvpns_heatmap.html, every choice for "Show" dropdown shows all the VPNs

The "show expired/unexpired" dropdown on the VPNs Heatmap display now correctly selects expired or unexpired VPNs

24812: Corrected column name for "Client Control Msgs Sent"

In the Solace Broker Clients Table there were two columns named "Client Control Msgs Rcvd". The second one has been corrected to "Client Control Msgs Sent".

24814: Increased precision of "Transacted Sessions Util %" in Broker Capacity Table

Columns "Transacted Sessions Util %" and "Transacted Sessions HWM Util %" in the Broker Capacity Table are now displayed with 4 decimal places

24815: Corrected Connection Max value in Brokers Table and Broker Capacity Table

The Max Client Connections values in the Brokers Table and the Connections Max values in Broker Capacity Table now correctly reflect the configured value for an appliance.

24817: Spool-disk-size column in Broker Capacity Table corrected

The column Spool Disk Allocated in the Broker Capacity Table has been renamed to Spool Size Max MB and is now displaying correct data.

24818: Removed Reserved columns from Broker Capacity Table

The following columns have been removed from the Broker Capacity Table: Connections Reserved Subscriptions Reserved Spool Reserved

24819: [Solace Event Module ] Reduced logging level of non-critical message parsing and regex errors

The logging for the Solace Event Module has been enhanced to reduce the logging level for the following errors: - Failed to create/enqueue message... This message is printed to the log when the event module receives a message that is not a syslog message. Since only syslog messages are supported in the event module, these messages are discarded. In previous releases, this was logged at the error level along with a stack trace. It is now logged at the debug level since it is not a critical error. - Failed to match regex, additional fields for message will be empty... This message is printed when the additional fields of the syslog message cannot be parsed due to an unexpected message format or an unexpected character in one of the additional fields. This error does not prevent the message from getting into the SolEventModuleEvents cache. This error may or may not impact alerting on this message. In previous releases, this was logged at the error level. It is now logged at the warn level.

24821: Corrections to metric used for Topic Subscriptions on Queue Used HWM %

The column Topic Subscriptions on Queue Used HWM % in the Broker Capacity table no longer shows incorrect zero values.

24843: Broker Capacity table Spool Size Max MB corrected

The Spool Size Max MB column now returns more accurate information. Also, the following columns in the Broker Capacity table: Cur Spool Usage MB Current Spool Usage HWM have been renamed to: Current Spool Usage MB Current Spool Usage MB HWM

24847: Current Spool Usage HWM % no longer zero in Broker Capacity Table

In the Broker Capacity table the column Current Spool Usage HWM % no longer shows zero values even when the corresponding Current Spool Usage % has data.

24860: Memory usage for state storage used by DELTA functions in solmon is now set to expire

The DELTA functions store internal state to perform their necessary calculations. Previously state was stored for all unique indices encountered. Now stored state is expired (and thus reclaimed) after they have not been updated for a period. The period matches that of the deletion period of the caches they populate. Thus their total memory usage is bounded in a manner similar to the current rows of the caches they populate.

Version 5.1.3 Release Notes

24280: Error msg "rtvconfig.hostmon.xml not found" removed

In previous releases, some dataserver.log files would contain the following error message at startup INFO main - [rtview] ERROR: GmsRtViewXmlDs – rtvconfig.hostmon.xml not found. This error message was benign and did not indicate a functional problem. It has been removed.

Configuration

24236: Allow users to see cleared alerts from any time in the past

A simple Alert History Table display has been added to the Components tab at Other/Common/Alerts/Alert History Table. This new table enables the user to see previously cleared alerts in a table.

HTML UI

Components Displays

23651: Click and Drag on heatmap no longer performs fake "zoom"

In previous releases, dragging the mouse across a heatmap and then releasing would cause the "Reset zoom" button to appear in the top left corner of the heatmap even though no zoom was actually performed. This has been fixed.


23989: Overview top 10 graph should always show 0-100% on x axis for CPU %

In the Package Overview displays, the top 10 graph now uses a fixed range of 0 to 100 when viewing a CPU% metric.


24041: Expired column moved to the right

Columns in tables have been rearranged to move Expired and Time Stamp to the far right.


General

24091: Export to Excel feature now works with Edge browser.

The Export to Excel feature on tables now works in MS Edge browser.


RTView Core Functionality

Data Server

24393: Fix deadlock condition in rtvquery

A problem in the rtvquery servlet has been fixed which could cause the servlet to hang with a deadlock. However this was only observed during shutdown of the app server (tomcat).

Distribution

24219: Upgrade from jetty 9.4.14 to 9.4.19

The version of jetty has been updated from 9.4.14 to 9.4.19. Users should not see any difference in behavior.

Solution Package for Solace PubSub+

23444: Improve responsiveness of Solace PubSub+ monitoring

The responsiveness of Solace PubSub+ monitoring has been improved in the case where Solace connections to PubSub+ Cloud brokers are processing large data sets.

23701: Solace Bridge diagram - connect to SolAdmin now working for SEMP v9

Right clicking router icons in the Bridges Diagram allows the user to launch the associated PubSub+ Manager. This functionality was broken for routers running newer SEMP versions, and has now been fixed.

24138: Improved calculation of SolMsgRouterSpoolUtilization alert

The calculation of the SolMsgRouterSpoolUtilization has been fixed to be computed as the percentage of spool memory consumed by all endpoints in the broker against the maximum spool memory assigned to the broker itself overall. If the maximum spool memory assigned to the broker varies from the sum of the spool memory assigned for each VPN, then the percentage of this alert might not be triggered correctly. To fix that, the user should manually ensure that the sum of all message VPN maximum spool usage is less or equal to the overall broker maximum spool usage. The reasons to allow that the maximum spool memory assigned to the broker can differ from the total assigned to the VPNs are the following: 1. It would be a painful for users to adjust all (or at least more than one) message VPN’s max spool usage setting when they really only wanted to increase it for one message VPN. 2. Creating a new message VPN would mean the user having to adjust this configured setting on other Message VPN. 3. Avoid artificially limiting the spool size of message VPNs if it is unlikely that several VPNs would ever be near the max spool usage assigned to the broker. This allows users the option to configure the broker to make the most of the underlying storage resources if the associated application behavior is unlikely to cause the overall message-spool allocation to be exceeded.

24159: SolClientSlowSubscriber misconfiguration fixed

A bug that prevented the SolClientSlowSubscriber alert from firing has been fixed.

24162: Alert and metrics to compute SolSparseMessageSpoolFile fixed

The collection of the metrics being used to compute the SolSparseMessageSpoolFile alert has been fixed.

24169: Support setting the maximum memory for the SolEventModule

The RTViewSolaceMonitor and RTViewDataServerSolace have been enhanced to support setting the maximum memory for the SolEventModule. The default is 512M. To set the maximum memory for the SolEventModule, add it to the end of the -soleventmodule command line as follows: -soleventmodule:1024M Replacing 1024M with the maximum memory you would like to use. This must not be set to a value smaller than 512M or to a value higher than the resources allocated for your jvm. This value is passed into the -Xmx Java command line and should use syntax appropriate to that argument which is a number followed by a unit. Valid units are k (kilobyte), m(megabyte), g(gigabyte). If no unit is specified, the number is assumed to be bytes.

24195: Improved handling of loss of connectivity to brokers

Previously connection threads to the HTTP data source could silently stop, causing healthy broker's to appear as Expired. This has been fixed. In conjunction to this fix, a new alert, SolMsgBrokerExpired, has been created to indicate when the monitoring data collection has stopped abruptly. Use this alert in conjunction with the SolMsgBrokerNotConnected alert, or in replacement of it if you don't need to be notified of lack of connectivity when the Solace Monitor starts up.

24224: Use physical-memory-usage-percent provided metric instead of calculated memory-used-percent

The physical and subscription memory used percentages have been enhanced to account for the values provided by Solace.

24304: Ease of use improvements for editing Solace PubSub+ connections.

The Configuration Application now ensures that new standalone Solace connections use the required host:port format.

24314: Replaced SolMsgRouterFailoverDetected with SolHAPairFailoverDetected

The SolHAPairFailoverDetected alert has replaced the SolMsgRouterFailoverDetected. This alert has as indexes the connection strings of the two HA brokers on an Active/Standby or Active/Active redundancy configurations. The condition for this alert to be executed is the following: (primary-status-activity == “Local Active? AND backup-status-activity2 == “Mate Active?) OR (backup-status-activity == “Mate Active? AND primary-status-activity2 == “Local Active?) Limitation: This alert requires that the hostnames and node names of the HA Group must be identical.

24315: Support use of user-supplied SEMP schemas

To simplify the update of the SEMP schemas when they are missing, schemas have been moved outside the data source jar. If the SEMP schemas that are required for connecting to a Solace Broker are missing, the Broker will not appear in the Broker Table of the PubSub+ Monitor and the log from the dataserver under projects\rtview-server\logs directory will show the following exception: “… java.lang.IllegalStateException: Have not loaded schemas for 'soltr/9_0VMR'. Ensure schema version looks like 'soltr/x_y'. Call loadSchemas() first, or import new schema files…? To solve the problem, you should download the schemas from the Solace Customer Portal (https://products.solace.com/) where you as a customer have access to download Solace products as well as the SEMP schemas from any supported release (either Software or Appliance Brokers). Be aware that the SEMP schemas from Software and Appliance Brokers even from the same version might differ. Therefore, verify that the downloaded files for either Software or Appliance Brokers are uniquely identified. To include the newly downloaded SEMP schemas follow these steps: 1) cd to the ‘resources’ directory (yourProjectDir/rtvapm/solmon/lib/ext/resources) and create a separate directory for the SEMP schema version to include. 2) Copy the two schema files into the newly created directory 3) Stop/start PubSub+ Monitor, Solace Data Server or Collector and verify whether the missing Broker appears connected and data is being collected properly. 4) Finally, verify the dataserver.log file no longer shows the missing schema error. Contact SL Technical Support if you have issues downloading or adding these files to the product.

24319: XPath functions fixed in soleventmodule.properties

In previous releases, xpath functions in the following soleventmodule.properties properties did not work and caused a parsing exception: ALERT_WHITELST ALERT_BLACKLIST EVENTWRITER_WHITELST EVENTWRITER_BLACKLIST This has been fixed. XPath functions that return true/false can now be used. Additionally, the typo in the ALERT_WHITELST and EVENTWRITER_WHITELST property names was confusing and has been fixed. Those property names have been changed to ALERT_WHITELIST and EVENTWRITER_WHITELIST. For upward compatibility, if the new property names are not found in the soleventmodule.properties file, the old properties names will be used.

24320: Raised alert level from warning (yellow) to alarm (red) for three alerts

The severity level of the following alerts has been raised to "alarm" level: SolGuaranteedMsgingHbaLinkDown SolGuaranteedMsgingMatePortDown SolGuaranteedMsgingNoMsgSpoolAdActive

24321: Included Solace PSG Password Utility scripts

The scripts to execute the Solace PSG Utility have been added. This tool is used for adding the connection properties to InfluxDB with an encrypted password. To use the tool, open a command prompt or terminal and initialize it: cd <install_dir>/rtvapm> . ./rtvapm_init.sh **IMPORTANT - do not omit the leading dot in this step** or cd <install_dir>\rtvapm> rtvapm_init.bat and then cd to rtvapm\solmon\bin directory and execute: pwd-utility[.bat] <yourPwdString> the following message will appear: Solace PSG Password Generation Utility v0.0.0 ------------------------------------------------------------------- This program encrypts passwords for storage in application property files. The encrypted password is: 'yourEncryptedString' (without the quotes). You may use this value in the password field in configuration property files.

24323: Update jackson libraries from 2.8.4 to 2.9.9

The Jackson libraries used with the Solace PubSub+ monitor have been updated from version 2.8.4 to version 2.9.9.

24336: Soleventmodule: Empty filters shouldn't trigger syntax error messages

In previous releases, setting the following filter properties in soleventmodule.properties to blank did not work and generated an error: ALERT_WHITELST ALERT_BLACKLIST EVENTWRITER_WHITELST EVENTWRITER_BLACKLIST This has been fixed.

24355: Improved support for monitoring of Backup and Monitoring brokers

A bug that prevented that Solace Backup Message Routers from populating correctly to the Solace PubSub+ Monitor has been fixed. This fix also allows monitoring of Solace PubSub+ Brokers that are partially configured.

24362: SolBridgeStats data collection for statds connections fixed

A bug that prevented data from being stored into the SolBridgeStats cache has been fixed.

24363: soleventmodule now correctly creates alerts when recommended actions contains a hard return

In previous releases, the soleventmodule events that have hard returns in the Recommended Actions failed to generate alerts due to a json parsing error. This has been fixed.

24364: Count of spooled messages should match across Broker, VPN, and Endpoint displays

Previously the number of spooled messages per VPN did not match the sum of the spooled messages across all endpoints of the same VPN. This has been fixed.

24383: Integrated "show redundancy group" query

The information from the "show redundancy group" command of the Solace CLI has been included. The SolRedundantBrokers and SolMonitorBrokers caches are now storing the information from this request.

Version 5.1.0 Release Notes

23814: Clean up webapps directory in bundled apache Tomcat

In the previous release, the webapps directory of the bundled Apache Tomcat contained extraneous RTView demo .war files. These have been removed.

23834: Export to Excel sometimes fails

The export to Excel feature now works reliably on tables in the rtview-central and rtview-solmon UIs

Alerts

23189: Included my_alert_actions scripts in all projects

RTView has been enhanced to include the my_alert_actions scripts in all project directories for ease of use.

23844: Enhance alert notification configuration.

Alert Notifications have been enhanced to support several new actions and a better configuration interface. For each notification, you can select one or more of the following actions: 1. Execute Script - This wil exectue the my_alert_actions*.bat/sh scripts in the project directory. This is the same action that was used in the previous releases when a notification was enabled. 2. Execute Java Method- This will execute a custom java command. 3. Send Email - This will send an email to one or more recipients. 4. Send SNMP Trap - This will issue an SNMP trap as described in RTVAPM_HOME\common\lib\SL-RTVIEW-EM-MIB.txt. 5. Other - This will execute any command supported by our core product. 6. Conditional - This will allow you to execute different commands based on values in the alert. For example, you could email Jvm alerts to the system administrator and Ems alerts to the TIBCO administrator. The user interface in the Configuration Application has also been enhanced with better descriptions of additional configuration needed for the selected actions. Upgrade Notes In previous releases, any notification other than executing the my_alert_actions scripts had to be configured on the CUSTOM PROPERTIES tab of the Configuration Application. If you are running a project configured with a previous release that has alert notifications defined in the CUSTOM PROPERTIES tab, they will continue to work as they did before with no changes. However, if you want to use the new Alert Notification configuration page, you will need to first delete the CUSTOM PROPERTIES for alert notifications, then recreate them in the Alert Notification page. Otherwise, the CUSTOM PROPERTIES will override the settings in the Alert Notification page.

24078: Alert Renotification interval default value corrected

In previous releases, the Renotification Interval in the Configuration Application incorrectly listed the default value as 300 seconds. This has been fixed. The default is now set to 0. Users must set it to a value greater than 0 in order to issue renotifications.

Configuration

23641: Support for updating properties via rest api

RTView has been enhanced with a rest api for editing solution package properties. This is to support the following use cases: 1. Importing an initial set of connections into the Configuration Application. This is useful in the case where there are a lot of connections and adding them via the Configuration Application ui will be too time consuming. Once the connections are imported using the rest api, all further editing can be done in the Configuration Application. 2. Dynamic updating of connections via automated process. These connections will only be updated via the automated process and will not be included in the Configuration Application. Connections will be applied without requiring a restart of the data server. Solace and TIBCO Enterprise Message Service properties are editable in the new rest api. Other solution packages properties will be added soon. A sample application has been added to all deliverables that shows how to use the rest api under rtvapm\sampleapps\propeditor. See the README.txt in that directory for instructions on using the rest api.

23886: Fixed bug effecting dynamic update of connection definitions

An issue that prevented connection definitions from being dynamically updated has been fixed.

23941: Can now restart data server without changing configuration

Servers can now be restarted from the Projects page even if no changes have been made that require a restart.

24032: Configuration Application updated to handle new Solace data acquisition.

The solace connection dialog in the Config UI now supports HA pairs and is also able to use the stats pump connection for non-cloud vmr's.

Display Server

24123: Support 'nosniff' header in thin client in IE11

A problem has been fixed which prevented the thin client Classic UI from rendering displays correctly in IE11 when the web server set the X-Content-Type-Options:nosniff response header. No other supported browsers were affected by this issue. Site administrators may configure a web server to send the X-Content-Type-Options:nosniff response header for security reasons. With this fix the thin client is not affected by the presence or absence of that header, which is the correct behavior. A related note for Tomcat users: In standalone Tomcat, the X-Content-Type-Options:nosniff response header is set by enabling the httpHeaderSecurity filter in tomcat's conf/web.xml file. By default, that filter also sets the X-Frame-Options:DENY response header. That setting will disable the thin client even with the fix described in this release note. To avoid that problem, tomcat should be configured to set the X-Frame-Options response header to SAMEORIGIN rather than DENY, to allow pages hosted by the same tomcat instance (only) to load thin client displays in iframes. So to set X-Content-Type-Options:nosniff and X-Frame-Options:SAMEORIGIN, the httpHeaderSecurity filter should be configured as follows intomcat's conf/web.xml file: <filter> <filter-name>httpHeaderSecurity</filter-name> <filter-class>org.apache.catalina.filters.HttpHeaderSecurityFilter</filter-class> <async-supported>true</async-supported> <init-param> <!-- allow use in iframe on pages with same origin --> <param-name>antiClickJackingOption</param-name> <param-value>SAMEORIGIN</param-value> </init-param> </filter>

Distribution

23737: Version now available from HTML UI

Users can now see the version of RTView from the HTML UI by clicking on the product name at the top left.

24040: Update bundled Apache Tomcat 8.5.x to 8.5.41

The version of the bundled Apache Tomcat has been updated to 8.5.41 (previous was 8.5.35).

General

23624: Configuration Application now catches Data Server's memory sizes without a unit (e.g., m or g)

In the Configuration Application, the Data Server's initial memory and max memory fields now have additional error checking to help ensure that only valid values are saved.

24099: Displays now support dynamically changing CIs

Additions and deletions of elements are now reflected in the filter drop-downs of all Component Displays. By default, lists update once per minute.

Scripts

23594: Added "status_servers.bat/.sh" convenience scripts

The following scripts have been added: RTViewCentral\bin\status_servers.bat RTViewCentral\bin\status_servers.sh RTViewDataCollectorSP\status_collector.bat RTViewDataCollectorSP\status_collector.sh RTViewDataServerSP\status_server.bat RTViewDataServerSP\status_server.sh RTViewSolaceMonitor\bin\status_servers.bat RTViewSolaceMonitor\bin\status_servers.sh

Solution Package

Solace

23792: Allow user to rename rtview-solmon.war

The update_wars.bat/sh scripts for the Solace PubSub+ monitor, under projects/rtview-server, now include the creation of the HTML UI servlet (default name rtview-solmon.war).

23825: New filter defaults for SolaceEventModule

The SolaceEventModule configuration has been enhanced with improved defaults for the alert and event filters in RTVAPM_HOME\solmon\soleventmodule\soleventmodule.properties. Additionally, several commented out sample filters have been added for different monitoring scenarios.

23962: New statspump data source for Solace.

The Solace Stats Pump Data Source has been integrated into the RTView Solace Monitor. This new data source supports HA Broker Pairs and multi-threaded SEMP XML response parsing which improves Data Server performance. The Solace Stats Pump Data Source is used by default in the RTView Configuration Application. Cloud Brokers are the only type of Solace Brokers that are using exclusively the HTTP Data Source.

23963: Output Solace SEMP data to Influx DB

The Solace monitor has been enhanced to send monitoring data to InfluxDB. The configuration requires edition of the stats-receiver.properties file, located in the project directory, to define the list of metrics to store in Influx DB and the IP address and port of the InfluxDB platform to store the data. Please refer to the documentation for the specific configuration steps.

23964: Output Solace SEMP data from Solace Stats Pump to a Solace Broker

The Solace Stats Pump can be configured to execute in isolation and send monitoring data from multiple Brokers to a designated Broker. This configuration will not downgrade the performance of the monitored Brokers if the Broker that will receive the monitoring data is exclusively doing this task. The steps to configure Solace Stats Pump to send monitoring data to a Solace Broker are the following: - Define the Solace Brokers to be monitored by editing the file appliance_config_demo.xml - Define the monitoring data to be polled by editing the file pollers_sl.xml - Define the poller groups that will be used by editing the file groups_sl.xml See the Solace documentation for further reference on how to configure Stats Pump for sending monitoring data to a Solace Broker.

23983: Removed calculated rates from SolVpns cache

Calculated rates from SoVpns cache have been replaced by the metrics delivered by Solace. The SOL_VPNS table from history should be dropped and recreated with the appropriate table create sql sentence you can locate in the rtvapm\solmon\dbconfig directory.

23985: User and some event-driven boolean metrics added to SolClients cache

User and boolean fields associated with one-show events have been added to Solace Client metrics. These booleans are: eliding-enabled, large-message-event-raised, max-eliding-topics-raised, message-too-big-event-raised, parse-error-event-raised

23994: Topic and Queue Rates added to the SolEndpointStats cache

Requests for message flow from Solace Topics and Queues have been added. These requests query all available Endpoints at once without the need of requesting this information per Endpoint.

23998: Added os-physical-interface to SolApplianceInterfaces cache

The os-physical-interface for each Broker Interface has been introduced into the SolApplianceInterfaces cache. This metric will be exposed in the Solace Interface Summary display from the Solace Monitor.

24015: New broker and endpoint alerts

The following new alerts have been added to the Solace monitor: - SolBrokerNoValidDestination alert, which will be triggered as an alarm alert when there exist currently invalid destinations in the broker. (Delta of discard-nodest is non-zero). - SolBrokerNoQueueFound alert, which which will be triggered as an alarm alert when there are discarded queues in the broker. (Delta of discard-queue-not-found is non-zero). - SolEndpointNoBridgeClient alert, which will be triggered as an alarm alert when no binds for the Solace Endpoint exist (bind-count is zero). - SolBrokerNoSubscriptionMatch alert, which will be triggered as an alarm alert when there are no current subscription matches (Delta of no-subscription-match is non-zero). - SolEndpointNoBridgeTopic alert, which will be triggered as an alarm alert when there are no topics subscribed to the Queue (topic-subscription-count is zero). Limitation of SolBrokerNoValidDestination, SolBrokerNoQueueFound and SolBrokerNoSubscriptionMatch Alerts: The request XML is a system level request. The cloud logon credentials will not have permission to execute this request, so this alert will not be executed for Cloud Brokers.

24033: Not clearable event module alerts now clear after expiration time

In the previous release, SolEventModule alerts that were based on non-clearable events sometimes did not clear. This has been fixed.

24055: Replaced calculated rates from SolBridgeStats cache with Solace provided rates

Calculated rates from SolBridgeStats cache have been replaced by the metrics delivered by Solace. The SOL_BRIDGE_STATS table from history should be dropped and recreated with the appropriate table create sql sentence you can locate in the rtvapm\solmon\dbconfig directory.

24056: Replaced delta/rate calculated metrics with Solace provided CSPF rates

The calculated rates for Solace CSPF Neighbors have been replaced by Solace calculated rates. The SOL_CSPF_NEIGHBOR table from history should be dropped and recreated with the appropriate table create sql sentence you can locate in the rtvapm\solmon\dbconfig directory.

24057: Rename calculated rates from SolClientStats cache with those from Solace

Calculated rates from SolClientStats cache have been replaced by the metrics delivered by Solace. The SOL_CLIENT_STATS table from history should be dropped and recreated with the appropriate table create sql sentence you can locate in the rtvapm\solmon\dbconfig directory.

24060: Calculated rates in SolVpns cache replaced by those provided by Solace

Calculated rates from SoVpns cache have been removed except for the total ingress/egress discard rates. The SOL_VPNS table from history should be dropped and recreated with the appropriate table create sql sentence you can locate in the rtvapm\solmon\dbconfig directory.

24082: Solace event module no longer reporting regex errors

In previous releases, the soleventmodule sometimes threw parsing errors on the following syslog messages: CLIENT_CLIENT_BIND_SUCCESS SYSTEM_AUTHENTICATION_SESSION_CLOSED SYSTEM_AUTHENTICATION_SESSION_OPENED This has been fixed.

24090: Ingress/egress message rates added to Endpoint Summary

Endpoint summary display has been enhanced with history of ingress/egress message rates.

24185: Support for HA Solace Brokers

Support for adding HA Pairs has been introduced. Using the Configuration Application, specify the URL, port, and credentials for the Primary and Backup Brokers. Two rows in the broker table for each broker will be added. Note that the Backup Broker will be identified by having the string "-standby" concatenated to the connection string.

24186: Solace Event Module can be used as sole source of monitoring data

The Solace PubSub+ monitor can be configured to run with all data being provided via the Solace Event Module; without connection properties being configured to Solace Brokers. See the RTView Solace Monitor documentation for a complete description of the configuration steps of the Solace Event Module.

24192: New standby filter selection list added to Solace Broker table and heatmap

An 'Show Standby' selection list has been added to filter the table and heatmap of Solace Brokers.

24193: Solace Broker Environmental Sensors should only show data from a single broker

The Solace Broker Sensors display now enforces selection of a single Broker.

Version 5.0.0 Release Notes

23222: Build with Java 1.8 + drop support for Java 1.7

RTView is now built with Java 1.8 Java 1.7 is no longer supported.

23671: New Syslog Event alerts

Three new alerts for Solace monitor for monitoring Syslog Events for the scopes SYSTEM, VPN, and CLIENT have been implemented. These alerts are named: SolEventModuleBrokerAlert SolEventModuleVpnAlert SolEventModuleClientAlert ... and require the Solace Event Module being configured and running. These alerts handle simultaneously Clearable and Non-Clearable Syslog Events. See TN23693 for details on how the Solace Event Module is configured and executed in the Solace Monitor.

Alerts

23373: Improved error reporting when persistence database doesn't have correct schema

The Alert Engine has been enhanced to provide expected column information in the case where the Alert Persistence database table does not contain the correct schema.

Configuration

22526: Enlarged font for help text in Config UI

The font size for help text throughout the ConfigUI has been enlarged to make reading easier.

23346: Refresh prompt added to avoid "invalid project not editable" error

The Configuration Application will now show a message asking the user to refresh when it encounters difficulty connecting to a server after that Data Server (or Data Collector) has been restarted.

23364: Support added for searching connections

Searching and sorting functionality has been added to all connection lists.

23391: History Storage - Keys field removed from MySQL configuration

The History Storage Keys field on the DATA STORAGE tab of the config ui was removed.

23674: Editing existing connection no longer results in a new duplicate connection

Previously editing existing connections could accidentally created clones. This has been fixed.

23686: Solace branding changes in Config UI

The Solace Configuration Application pages have been updated to reflect current Solace branding.

23720: config UI mangles alert notification properties when saving; causes them to fail

In previous releases the alert notification properties were not saved correctly by the Configuration Application in the following deliverables: BWMonitor / TIB_rtview-bw EMSMonitor / TIB_rtview-ems RTViewSolaceMonitor This has been fixed.

Data Historian

23504: Historian now detects lost database connection when using prepared statements

Previously, under certain circumstances, the Historian would not detect lost database connections when using prepared statements. This is no longer the case.

Data Sources

SQL Data Source

23500: Duplicate database connection errors no longer printed to log file

The error reporting for failed database connection attempts has been enhanced. Previously, an error was printed to the console for each failed connection attempt. Now, an error is reported for the first failed connection attempt and no more output is generated until a success message is printed when the connection succeeds. The connection error is only printed again the first time we fail to reconnect after a successful connection is lost. This change applies both to the GmsRtViewSqlDs connections and to the Historian connection to the RTVHISTORY database.

Distribution

23220: jetty updated to 9.4.14

The version of Jetty used by EM to host web applications has been upgraded to Jetty version 9.4.14. In addition, the temp directory used by Jetty has been changed. Previously, the java.io.tmpdir directory was used, but files were not always removed from this directory. Now, Jetty creates a temp sub-directory in the directory where the data server is running. This temp directory is deleted on shutdown.

23560: Data Cache package added to the Solace Monitor

The Solace Monitor has been enhanced to the include the DataCache package. It is used to collect data via http from a javascript application such as NodeJs. Rest Endpoints (urls) are provided to allow the posting of data to caches, and the creation, deletion and replacement of caches.

General

23640: Servlet file names changed

The names of the war files distributed with RTView have been changed as per the table below. This means the URLs used with the corresponding RTView servlets must be changed. For example: Old: http://localhost:10070/rtvcentral/ http://localhost:10070/rtvcentral_rtvadmin/ New: http://localhost:10070/rtview-central-classic/ http://localhost:10070/rtview-central-rtvadmin/ Note that the thin client war which was named <package>.war is now named <package>-classic.war and the new HTML UI war will be named <package>.war. The servlet renames for the independent, single-technology monitoring products are listed below. bwmon_rtvadmin.war rtview-bwmon-rtvadmin.war bwmon_rtvquery.war rtview-bwmon-rtvquery.war bwmon_rtvdata.war rtview-bwmon-rtvdata.war bwmon_rtvpost.war rtview-bwmon-rtvpost.war bwmon_rtvagent.war rtview-bwmon-rtvagent.war bw6mon_rtvadmin.war rtview-bw6mon-rtvadmin.war bw6mon_rtvquery.war rtview-bw6mon-rtvquery.war bw6mon_rtvdata.war rtview-bw6mon-rtvdata.war bw6mon_rtvpost.war rtview-bw6mon-rtvpost.war bw6mon_rtvagent.war rtview-bw6mon-rtvagent.war emsmon_rtvadmin.war rtview-emsmon-rtvadmin.war emsmon_rtvquery.war rtview-emsmon-rtvquery.war emsmon_rtvdata.war rtview-emsmon-rtvdata.war emsmon_rtvpost.war rtview-emsmon-rtvpost.war emsmon_rtvagent.war rtview-emsmon-rtvagent.war tbemon_rtvadmin.war rtview-tbemon-rtvadmin.war tbemon_rtvquery.war rtview-tbemon-rtvquery.war tbemon_rtvdata.war rtview-tbemon-rtvdata.war tbemon_rtvpost.war rtview-tbemon-rtvpost.war tbemon_rtvagent.war rtview-tbemon-rtvagent.war rtview#solmon rtview-solmon.war rtview#solmon_manager.war N/A (deprecated) rtview#solmon_rtvadmin.war rtview-solmon-rtvadmin.war rtview#solmon_rtvquery.war rtview-solmon-rtvquery.war rtview#solmon_rtvdata.war rtview-solmon-rtvdata.war rtview#solmon_rtvpost.war rtview-solmon-rtvpost.war rtview#solmon_rtvagent.war rtview-solmon-rtvagent.war rtview#rtvmgr_manager.war rtview-manager-classic.war rtview#rtvmgr_rtvadmin.war rtview-manager-rtvadmin.war rtview#rtvmgr_rtvquery.war rtview-manager-rtvquery.war rtview#rtvmgr_rtvdata.war rtview-manager-rtvdata.war rtview#rtvmgr_rtvpost.war rtview-manager-rtvpost.war rtview#rtvmgr_rtvagent.war rtview-manager-rtvagent.war

23687: New user names added to the thin client

The default thin client login has been enhanced to support the following new users: user = rtvadmin, password = rtvadmin, role = admin user = rtvuser, password = rtvuser, role = read-only user = rtvalertmgr, password = rtvalertmgr, role = event The previously supported default users (admin, demo) are still supported for the thin client in RTViewCentral, but the new login must be used for the beta Enterprise Edition user interface. In RTViewSolaceMonitor, the new login must be used.

23706: Updated Solace Monitor interface

The navigation of the RTView Solace Monitor has been updated. On larger screens the page now contains a horizontal menu bar with three tabs described below. On smaller screens, the horizontal menu bar is replaced by a vertical menu whose visibility is toggled by clicking the menu icon in the upper right corner of the page. The Displays tab is used to view the Solace displays in the main panel, selected from the navigation tree in the left panel. The Alerts tab is used to view and manage alerts. The Admin tab is used to administer alerts and to view cache contents directly. This tab is accessible only for users that have admin privileges (user accounts with the rtvadmin role). The use of each tab is described below in more detail. The navigation tree in the left panel on the Displays and Admin tabs can be hidden by clicking the "<<" button in the bottom left corner, and then made visible again by clicking the ">>" button. In many cases a click or double click on an object in a display can be used to drilldown to a related display. After such a drilldown, the corresponding item in the navigation tree will be highlighted. The user's navigation through the displays is recorded in the browser history, and the browser's back and next buttons can be used to traverse that history. There is no logout button in the UI. Once a user has logged in, that user remains logged in until the browser window is closed. Closing just the browser tab that contains the UI will not log the user out, the browser itself must be closed. 1) Displays tab: Use this tab to view the Solace Monitor displays. Displays can be selected from the navigation tree in the left panel or by drilling down from one display to another. 2) Alerts Tab: - Use the dropdowns labelled Ack'd and Cleared to filter the table according to the contents of the Ack and Clr columns. - A single click on a row in the table selects the alert. Use Ctrl + click to select multiple alerts. - A double click on a table row simply selects the row, the same as a single click. It does not trigger a drilldown. - With one or more alerts selected, the buttons above the table can be used to: Own: set the alert(s) owner field Ack: acknowledge the alert(s) Unack: clear the acknowledgement on previously acknowledged alert(s) Comment: add a comment to the alert(s) Details: drilldown to the alert detail display CI: drilldown to the CI display that corresponds to the alert, if any. The user must have the rtvalertmgr or the rtvadmin role to perform the Own, Ack, Unack, or Comment actions. If not, an error dialog will appear when the user clicks any of those buttons. 3) Admin tab: - The Alert Administration display allows an administrator to manage alert definitions, by setting thresholds, duration and enabling/disabling them. Use the Override Settings button to define thresholds that are specific to individual items or groups of items. - The Cache Table display is for browsing the raw content of the caches. This low-level option can be useful to identify the source of the problem when the displays are not showing the expected data.

RTView Core Functionality

Alerts

23373: Improved error reporting when persistence database doesn't have correct schema

The Alert Engine has been enhanced to provide expected column information in the case where the Alert Persistence database table does not contain the correct schema.

Data Historian

23504: Historian now detects lost database connection when using prepared statements

Previously, under certain circumstances, the Historian would not detect lost database connections when using prepared statements. This is no longer the case.

Data Server

23491: Options added to rtvquery for how to output NaN

The rtvquery servlet has new options for specifying how values of NaN, Infinity, and -Infinity should appear in the response. The new options are infval, and neginfval, and nanval. infval: The value to use for +Infinity neginfval: The value to use for -Infinity nanval: The value to use for NaN, and for +Infinity if infval is not specified, and for -Infinity if neginf is not specified. These options are recognized only if the nanok option is set to true (nanok=true) and if the requested format is json (fmt=json). These options can be useful if the rtvquery response will be parsed by 3rd party apps that expect specific strings for those values. For example, if a parser expects the string "null" for values of NaN and +/-Infinity, the following options should be used: http://somehost/rtvquery/cache/MyCache/current?fmt=json&nanok=true&nanval="null" Note that the quotes around null are required to make it a valid JSON string. Or, for a parser that expects zero for NaN and +/-Infinity: http://somehost/rtvquery/cache/MyCache/current?fmt=json&nanok=true&nanval=0 Or, for a parser that expects zero for NaN, 99999 for +Infinity, and -99999 for -Infinity http://somehost/rtvquery/cache/MyCache/current?fmt=json&nanok=true&nanval=0&infval=99999&neginfval=-99999 If none of the new options is specified, then the behavior is the same as in previous releases: That is, if nanok = true, then NaN appears as "NaN" in the response, +Infinity appears as "Infinity", and -Infinity as "-Infinity". If nanok = false or is not specified, then NaN, +Infinity,and -Infinity all appear as "" (an empty string) in the response.

Distribution

23220: jetty updated to 9.4.14

The version of Jetty used by EM to host web applications has been upgraded to Jetty version 9.4.14. In addition, the temp directory used by Jetty has been changed. Previously, the java.io.tmpdir directory was used, but files were not always removed from this directory. Now, Jetty creates a temp sub-directory in the directory where the data server is running. This temp directory is deleted on shutdown.

Scripts

18806: Support secure JMX with start and stop and status scripts

The start_rtv, stop_rtv and status_rtv scripts have been enhanced so as to work with RTView servers whose JMX ports have been secured either with username and password or with SSL. You give the scripts the necessary information about credentials and they manage authentication with the server. In the first case the necessary information is username and password. In the second case it is client KeyStore and TrustStore locations and their corresponding passwords. This information can be given to the scripts in two ways: via command-line arguments, and via properties placed in any property file used by the server. Username and password may be specified via command-line arguments as follows: -jmxuser:... -jmxpass:... Or by properties as follows: sl.rtview.jmxremote.username=... sl.rtview.jmxremote.password=.... Client KeyStore and TrustStore files and passwords may be specified as follows: -sslkeystore:... -sslkeystorepass:... -ssltruststore:... -ssltruststorepass:... Or by properties as follows: sl.rtview.ssl.client.keyStore=... sl.rtview.ssl.client.keyStorePassword=... sl.rtview.ssl.client.trustStore=... sl.rtview.ssl.client.trustStorePassword=.... You may encrypt the passwords in your properties files by using the command-line tool "encode_string", for example encode_string encoder2 password This will give you an encrypted value for "password" you may use in your properties.

23204: update_wars scripts now support command-line arguments

The update_wars scripts in all deliverables have been improved as follows: 1. The name, host, and portprefix are declared in variables at the top of the script for easy editing. 2. Those three variables may be passed into the scripts on the command-line, e.g. update_wars.sh my-appname my-hostname 99 3. You may use "?" or "help" to get a usage message, e.g. > update_wars.sh help Usage: update_wars.sh [appname [host [portprefix]]] Defaults: rtview-bwmon localhost 33 4. You may edit other variables at the stop of the scripts to set properties for HA (high-availability). Set HA_HOST to the hostname of the backup data server. Set HA_DISPLAYHOST to the hostname of the backup display server. Set HA_FAILBACK to true to automatically reconnect to the primary display server.

23416: JMX port conflicts reported by start scripts

The start_rtv scripts, when checking for port conflicts before starting a server, will now detect if a port conflict is caused by another RTView server, and will identify that server by its RTVAPM_HOME. For example: ...start_rtv.bat: another dataserver running with JMX port 3268 under C:\rtview\RTViewDataServer\rtvapm If the port conflict is caused by a non-RTView process the message will be like this: ...start_rtv.bat: JMX port 3268 in use by PID 1234 In either case the script will include this advice: Warning: server not started, port conflict To avoid port conflicts, run your start script with the -portprefix: command line argument to change the first 2 digits of all your server ports. To persist these port changes, change the port prefix in the Configuration Application or use the -saveportprefix: command line argument. See the documentation for more information.

23431: Start scripts no longer fail on windows if there are spaces in the install directory

The scripts used to start and stop rtview servers on Windows would fail if the product were installed in a directory with spaces in the name (e.g. "test directory"). This has been fixed.

23467: Fixed portprefix command line bugs

Two problems with the -portprefix option have been corrected. It will now emit correct args for the single-solution monitoring products, and it will not incorrectly emit args for central servers.

Solution Package

Host Infrastructure

23048: Fixed incorrect info in hostbase sample.properties file

This Host Solution Package property is obsolete: collector.sl.rtview.cache.config=host_cache_source_agent_v1.1.rtv $hostAgentDomain:myDomain For SL Host agents, the domain name is set in the agent's agent.properties file.

23683: Corrections/additions to rtvHostAgent

The default port that the Host Agent sends to has been changed from 3972 to 3272, the new default listen port for RTView DataServers. For user convenience, information about optional command line arguments, that can override some properties in agent.properties, has been added to the README.txt and agent.properties comments.

Solace

23258: Improved drill down behavior of Solace Neighbors topology diagram

The CSPF Neighbors Topology diagram has been fixed and now allows drill down to the CSPF Neighbor Table filtered by the selected Message Router when one double clicks on a Message Router with neighbors. Otherwise, the CSPF Neighbor table will show all neighbors from all Message Routers.

23265: HSQLDB database now only started with -eval flag

The starting of HSQLDB has been parameterized with command line flag in the scripts for starting RTView processes. For evaluation purposes append the -eval command line: start_servers.bat -eval or start_servers.sh -eval which will execute HSQLDB for ease of use in evaluation situations. When one of the supported SQL databases is configured, the script should be started without any command line appended.

23536: Data queries improved to work with heavily loaded router

The RTView Solace Data Source has been improved to incorporate paging on all high volume SEMP requests. These improved queries are for Clients, Endpoints (Queues and Topics) and VPNs.

23630: Bind-requests removed from SolClients cache

The metric bind-requests has been removed from the SolClients cache and accordingly from the Clients Table and Client Summary.

23675: Display Server UI removed from Solace Monitor

The RTView Display Server UI for the Solace Monitor has been deprecated. Users should continue to use the newer HTML 5 UI that was added in the previous release.

23690: Brokers Table no longer empty when collecting data from cloud brokers

The VPN information from the Solace Cloud Brokers has been raised to the Brokers displays to avoid misleading empty displays due to the limited characteristics of their functionality.

23722: New Solace Sparse Message Spool Files alert

A new alert SolSparseMessageSpoolFile, for detecting the existence of sparse message spool files, has been implemented. This alert will be triggered when the Disk Space Utilization is above 30% and the ratio of Disk Space in MB and Spool Usage in MB is above 3. Look at the Recommended Actions Section from https://docs.solace.com/Configuring-and-Managing/Mon-Mgmt-Disk-Con.htm for details on how to solve this situation.

23729: Support for Syslog messages changed

Solace solution package support for Syslog messages has changed. The previously supported Syslog connections and displays are no longer available. Solace Syslog messages are now handled by the Solace Event Module. The new Syslog display is availabe in the RTViewSolaceMonitor and in the beta Enterprise Edition monitor. It is not available with Enterprise Monitor (thin client). Users with existing Solace projects from previous releases that contain Syslog connections will need to migrate their Syslog connection information to the Solace Event Module.

23766: New metrics to calculate SolSparseMessageSpoolFile alert

The Disk Space Usage in MB and the Spool Usage in MB metrics have been added to the SolApplianceMessageSpool cache. These metrics will be used to calculate the condition for triggering the SolSparseMessageSpoolFile alert.

Version 4.2.0 Release Notes

Configuration

23135: Fixed bug with removing vpn from Solace connection

In the previous release, it was not possible to remove all Solace vpn's from the connections dialog. This has been fixed.

23140: New Connection icon no longer disappears from Configuration Application after toggling tabs on SYSLOG connections.

The Solace Add Syslog Connection ('+') button now always appears as expected.

23187: IE 11 Compatibility mode is now recognized as not supported

IE 11 Compatibility mode is now flagged as being unsupported for the Configuration Application.

Data Historian

22195: RTView Historian now uses PreparedStatements

The Historian now uses PreparedStatements for repeated SQL Queries against the historian database - For raw data insert - For data compaction - For retention deletion Previously the historian used literal SQL queries with unique timestamps.

Data Server

23210: Improved error reporting for start_rtv.bat/sh scripts

The start_rtv scripts have been enhanced to report possible port conflicts before trying to start a server, and to report if a server is not actually started due to some other cause (e.g. expired license key). if a server's data and/or JMX port is already in use by another process, start_rtv will report e.g.: dataserver: JMX port xxx in use by PID yyy dataserver: Data port xxx in use by PID yyy If the server fails to start for some other reason, start_rtv will report e.g.: dataserver: Executing rundata -propfilter:receiver dataserver: ... was not started, check log file.

23211: Message now shown in dataserver console when Java is not available.

The scripts which start servers have been improved to give a clear indication if the java command is not available. If java(.exe) is not found on the PATH but JAVA_HOME is defined, the scripts will add JAVA_HOME/bin to the PATH and try again. If JAVA_HOME is not defined or java(.exe) cannot be found in JAVA_HOME, the scripts will fail with the error "java not found on PATH and JAVA_HOME not defined or not valid." On Windows this will be followed by a pause and "Press any key to continue".

General

23064: Configuration Application now displaying proper warning after failing to write property.

An alert dialog has been added to display any warning msgs that follow a successful save.

23177: Renamed project directories in RTViewSolaceMonitor

The project directory names have been changed: RTViewSolaceMonitor\projects\solmon -> RTViewSolaceMonitor\projects\rtview-server RTViewSolaceMonitor\projects\rtvmgr-> RTViewSolaceMonitor\projects\rtvmgr-server

RTView Core Functionality

Data Historian

22195: RTView Historian now uses PreparedStatements

The Historian now uses PreparedStatements for repeated SQL Queries against the historian database - For raw data insert - For data compaction - For retention deletion Previously the historian used literal SQL queries with unique timestamps.

Data Server

23211: Message now shown in dataserver console when Java is not available.

The scripts which start servers have been improved to give a clear indication if the java command is not available. If java(.exe) is not found on the PATH but JAVA_HOME is defined, the scripts will add JAVA_HOME/bin to the PATH and try again. If JAVA_HOME is not defined or java(.exe) cannot be found in JAVA_HOME, the scripts will fail with the error "java not found on PATH and JAVA_HOME not defined or not valid." On Windows this will be followed by a pause and "Press any key to continue".

Scripts

23032: New validate_install.bat/sh script

A new script has been added to the RTView distributions to validate the RTView installation. It will verify the environment and directory structure and on Unix it will also fix file permissions and file formats as required. The script is validate_install.bat/sh. It is used in a command prompt or terminal window by changing to the toplevel/rtvapm directory and typing "validate_install(.sh)". On Unix, if file permissions or formats are fixed, the script will print a count of the files fixed. Additionally, if invoked with the argument "-v" (verbose) it will list the names of the files fixed. Examples: Validating installation in /opt/rtview/RTViewSolaceMonitor ... Java installation correct. ... rtvapm installation correct. ... file permissions correct. ... file formats correct. Validating installation in C:\rtview\RTViewDataServerKafka ... Java installation correct. ... rtvapm installation correct.

Solution Package

Solace

23037: Table Displays now present subset of available data, with a toggle to view full data

To improve ease of location of metrics in the tabular displays of the RTView Solace Monitor, these displays have been enhanced to show a limited set of metrics by default. If the user needs the full set of metrics in the tables, a toggle element in the form of the hyperlink is present. This feature will improve usability and assist users on toggling between tables showing all available metrics for the corresponding monitoring item or a limited set of the most outstanding metrics. Affected display are: All Msg Routers Table, All VPN's Table, All Clients Table, CSPF Neighbors, All Bridges Table, All End points Table, Message Router Capacity Table.

23060: Two new automated topology views for CSPF Neighbors and Bridges

Two new automated topology views for CSPF Neighbors and Bridges have been added to the RTView Solace Monitor. The first display allow users to see the topology view of their CSPF Neighbor Message Routers, showing which Servers are active and which Message Routers connected to each other. The second display allow users to see the topology view of their Bridges, showing the bridge connectivity as arrows between VPNs from the same or different Message Routers. LIMITATIONS - Only the Chrome browser is supported - Clicking on objects in the Bridges topology diagram will allow users to drill down, but this functionality is not currently supported for the Neighbors toplogy diagram.

23173: Physical memory used percentage and subscription memory used percentage added to SOL_APPLIANCE database table

Two new message router metrics have been added to the history of the SolAppliances cache: physical memory used percentage and subscription memory used percentage. These metrics are shown in the Message Router Summary display in the fourth metric card and under the trend tab titled "Memory". Users will need to update the table structure of the SOL_APPLIANCE historian table by executing the following alter table SQL sentences in your selected database administrative tool: Oracle: ALTER TABLE "SOL_APPLIANCE" ADD ("memory-used-percent" REAL , "subscript-mem-used-percent" REAL); DB2: ALTER TABLE "SOL_APPLIANCE" ADD "memory-used-percent" DOUBLE; ALTER TABLE "SOL_APPLIANCE" ADD "subscript-mem-used-percent" DOUBLE; SyBase: ALTER TABLE "SOL_APPLIANCE" ADD "memory-used-percent" FLOAT NULL, "subscript-mem-used-percent" FLOAT NULL; MySQL: ALTER TABLE "SOL_APPLIANCE" ADD "memory-used-percent" DOUBLE; ALTER TABLE "SOL_APPLIANCE" ADD "subscript-mem-used-percent" DOUBLE; SQLServer: ALTER TABLE [SOL_APPLIANCE] ADD [memory-used-percent] FLOAT; ALTER TABLE [SOL_APPLIANCE] ADD [subscript-mem-used-percent] FLOAT;

Version 4.1.0 Release Notes

22843: Configuration Application added to RTView Monitor for Solace

The Solace Monitor has been enhanced to include the Configuration Application which is available at the following url: http://localhost:8068/rtview/solmon_rtvadmin The login is rtvadmin/rtvadmin. The Configuration Application can be used to setup connections and poll rates and configure history.

Configuration

22891: Configuration Application now uses basic authentication instead of digest

In the previous release, the Configuration Application used Digest authentication which cause occasional problems with the login dialog coming up repeatedly when single sign on was not enabled in the app server. It has been modified to use BASIC authentication instead which does not require single sign on. Basic authentication sends the username and password as a base64-encoded string. This a public encoding scheme and is therefore not secure unless https is used. If you are concerned about keeping the login credentials of the Configuration Application secure, you should deploy it using https which will secure all data including the login credentials.

22892: New Restart Data Server option added to configuration application

The RTView Configuration Application has been enhanced with a button to restart a Solution Package data server. This button is available whenever there are unapplied changes. To restart a solution package data server: 1. Make some configuration changes and click SAVE to save them. 2. A Restart button will appear in the top right corner of the page. When you click the Restart button, you will be taken back to the top level page. The data server for the solution package project will exit, then start back up with the changes applied. The button is also available on the top level page if you want to restart your data server later. There is a delay of 10 seconds between the shutdown of the server and the restart in order to allow system resources to be released by the exising process. It may take several more seconds before Configuration Application and other clients reconnect to the data server. Note that this process only restarts the data server. Settings for the display server or historian processes will not be applied until those processes are restarted using the scripts. They cannot be restarted from the Configuration Application.

Distribution

22794: New user interface for RTView Monitor for Solace

RTView Monitor for Solace UI has been updated. To reach the new UI, open a browser window and redirect to: YourHost:8068/rtview/solmon where YourHost is the host name or IP address where the RTView Monitor for Solace Monitor was installed.

Solace

22796: Added Tomcat security for RTView Monitor for Solace

Tomcat digest security has been added to RTView Monitor for Solace.

RTView Core Functionality

Distribution

22853: rtvpost servlet added to Jetty

RTView Enteprise Monitor html server feature has been enhanced to include the %RTV_HOME%\servlets\rtvpost\rtvpost.war servlet in Jetty.

Solution Package

Solace

22721: Support Solace Cloud Edition

Support for Solace Cloud Edition has been added. Connections can be defined using the RTView Configuration Application.

22787: Wrong metric name in renaming function will generate a wrong zero value

A typo on the name of the spool message size in MB metric for topic endpoints was preventing the correct value to be collected. This typo has been fixed and now the spool message size in MB for topic endpoints is collected properly. Also, several typos on client bridge received bytes metrics have been removed which prevented the correct values to be stored in the SolBridges cache. Now the client received total, data, persistent, non persistent, and direct bytes are stored properly into the cache.

22789: Collect SEMP version automatically to avoid configuration problems

As of Solace VMR version 8.7+ and Solace Appliance version 8.3+, it is no longer required to include a SEMP version string in connection properties. See https://docs.solace.com/SEMP/Using-Legacy-SEMP.htm. For earlier versions of Solace VMR and Solace Appliance, the SEMP version string should be entered in connection properties. Not using the proper SEMP version string would impair the collection of monitoring metrics. See RTView Solace Solution Package documentation for a description to determine the SEMP version string in your Solace Message Router and to enter this value in your connection properties.

22799: Full EM deployment no longer an alterative deployment option

The RTView Monitor for Solace no longer contains the option to run a full RTView Enterprise Monitor deployment. The URLs for RTView Monitor for Solace are the following: - SOLMON UI: host:8068/rtview/solmon Username: solmon Password: solmonpw - SOLMON Configuration Application: host:8068/rtview/solmon_rtvadmin Username: rtvadmin Password: rtvadmin - SOLMON Alert Manager UI: host:8068/rtview/solmon_manager Username: solmon Password: solmonpw - RTVMGR UI: host:8068/rtview/rtvmgr_manager Username: solmon Password: solmonpw

Version 3.8.0 Release Notes

Configuration

22053: EM property handling has been enhanced

In previous releases, sender properties could be overriden by project properties unintentionally. In order to address this, the EM property handling has been enhanced to give precedence to the properties that use the sender property filter for processes that are run with the sender property filter.

22069: Port inconsistencies fixed in multiple solution packages

The following solution packages were set to use an incorrect port in rtvagent.war to communicate with the dataserver: acwmon mqmon mysqlmon ocmon syslog These have been corrected.

Deployment

21919: $rtvTimeZoneOffset substitution has been removed from emcommon and emreference

The $rtvTimeZoneOffset substitution has been removed from emsample\conf\emcommon.properties. This substitution is not used in any standard EM displays. Customers who have created custom displays for use with EM, should check to see if they have used that substitution and if so, add it to their project properties.

Distribution

21983: Fixed an issue with .war file creation

Previously some solution packages could not be built from scratch in a deliverable using the make_wars_package.bat script, due to a file missing from the package library. This has been fixed. The effected solution packages are: Solution Package for Amazon Cloudwatch (acwmon) Solution Package for VMWare (vmwmon) Solution Package for TIBCO ActiveSpaces (tasmon)

RTView Core Functionality

Data Historian

21921: Microsoft SQL Server 2014 and 2016 now supported

Microsoft SQL Server 2014 and 2016 are now supported as databases for use with the Data Historian, provided that the latest JDBC driver is used (sqljdbc41.jar with Java 1.7, sqljdbc42.jar with Java 1.8).

Display Server

21909: Tomcat logs no longer produce gratuitous rtvCleanup errors

In previous releases the following error message appeared in the Tomcat log at shutdown, for each deployed copy of the rtvdisplay servlet: "SEVERE: The web application [/rtvdisplay] appears to have started a thread named [rtvCleanup] but has failed to stop it. This is very likely to create a memory leak." Starting with this release, the error message should be seen less often in the log file, although it may still appear occasionally. In any case, there is no danger of a memory leak when tomcat is shutdown.

21990: Fixed a vulnerability in the thin client

An XSS (cross-site scripting) vulnerability in the thin client login.jsp file has been fixed.

21996: Fixed an issue with thin client resizing

In previous releases, after a display is resized by the thin client to fit the browser window, the black border around the default button (if any) was drawn in the button's original position, rather than the button's new position. This is fixed.

Object Library

21045: Misconfigured table objects no longer cause javascript exceptions in the thin client

A bug in the thin client has been fixed which could cause a javascript exception if the columnFormat on a table object was misconfigured to specify a format for a string column, and a backslash character appeared in the column.

Scripts

22049: EM enhanced to automatically read local project.property files

EM applications have been enhanced to automatically read project.properties if it exists in the directory where they were started. If project.properties does not exist, no error is printed. Upgrade Notes: If you are upgrading from a previous version and your project contains a project.properties file, be aware that this file will be used even if it is not specified on the command line. To avoid this, rename or remove your project.properties file.

Solution Package

Solace

21815: Message Router drop down enhanced to show availability of message routers

The Message Router drop down has been enhanced to indicate the availability of the Message Router. When the Message Router is disconnected, the connection name contains the string [?] appended to indicate the quality state: "No Data". When the Message Router has expired, the connection name contains the string [X] appended to indicate the quality state: "Lost Data". No string is appended to the connection name if the Message Router has no monitoring issues.

21886: Removed unnecessary link in Message Routers navigation tab

The link to the CSPF Neighbors has been removed from the Message Routers navigation tab.

21997: Multiple improvements made to some SOLMON displays

To avoid having the SOLMON Client displays blank when there is an error in the SEMP request that populates the SolClients cache, an improvement in our displays has been introduced to show the data available mainly from the SolClientStats cache and leave the SolClients cache as a secondary source of data. As a result, the All Clients Table can show the data coming from the available SolClientStats cache. The missing columns that are primarily static strings will be blank in this display. In regard the Clients Summary, a quality measurement of the available data is being performed so the display shows the existing data and hides the graphical elements for which we don't have available current data. If the data is Expired, the background of this display is shown grey with the string "[X]" appended to the Client name in the drop down. Finally, the background of the display will be shown as light red and the Alert State grayed out if there is no client available.

22036: Properties related to SOLMON history tables moved to conf directory

The properties that enable/disable the SOLMON history tables have been moved from the sample.properties file to the rtvapm.solmon.properties file located in the conf directory. To change the default settings, follow the instructions provided in the second file.

Version 3.7.0 Release Notes

Distribution

21836: MySQL now provided via Docker Hub

For the convenience of users who utilize Docker, the slcorp repo on Docker Hub now includes an image of MySQL Database configured to work with RTView. This container only works with Docker 1.10 and later. See rtvapm/containers/docker/mysql-rtview/README.txt for more information.

Drill Down

21887: Fixed an issue with navtrees

In previous releases, when drilling down from within a display to another display in the navtree, the tree selection sometimes failed to update correctly. This happened in the case where there were multiple navtree items for the same display with different subs and the user drilled down to that display from within another display. This has been fixed.

RTView Core Functionality

Alerts

21924: Fixed an issue with disabling event alerts

In previous releases, disabling event alerts was sometimes ignored due to a bug that was introduced in RTView Classic 6.7.0, RTView EM 3.2.0. This has been fixed.

Builder

21672: Builder enhanced to remember dialog window sizes and positions

The Display Builder has been enhanced to automatically save and restore the size and location of the following dialogs: - Open (File->Open) - Save (File->Save/Save-As) - Function Results (Function Dialog->Result Button) The Tools->Reset Window Layout menu option and the -resetlayout command line option restore the size and location of these windows in addition to the other windows that were previously reset.

Builder - Property Dialogs

15582: Japanese label for "Update Mode" property now shown on certain dialogs

Previously, the Japanese label for "Update Mode" property was not shown on certain polled ds attach to data dialogs when running on a Japanese OS. The English label was used instead. This is no longer the case. Affected dialogs include the custom polledds and polledds2 example data sources, and the http rest data source

Data Server

21898: Fixed an issue with rtvquery returning errors on valid query strings

In previous releases, the rtvquery servlet would sometimes return an error of "No data received before timeout, query may be invalid" for a specific, valid cache query string, on every attempt. The servlet needed to be restarted to clear the error. This has been fixed.

Display Server

21906: Thin client enhanced to check user role access on each request

In prior releases, after a user had logged into the thin client, the user could manually enter a specific URL in the same browser instance and possibly view data from rtview displays to which the user's role should have denied access. This is fixed.

21908: Enhanced display server with option to limit access to specific panel files

The display server now supports a "permitpanel" option to specify the panel layout files that the server will read. A panel layout for the thin client is requested from the display server with a URL parameter as follows: panels.jsp?file=X where X is the name of the panel layout file that the server should read. By default, the display server will attempt to read any filename on the server that is specified by the URL parameter. If the file is a valid panel layout file, the thin client will use it. But if the file does not exist, a "no such file" error is displayed in the browser, and if the file exists but does not contain the expected layout information, a "no panels found" error is displayed in the browser. The permitpanel option allows you to specify the file(s) which the display server will read in response to a panels.jsp request. Requests from panels.jsp for any other files are rejected with a "Permission denied" error shown in the browser, regardless of whether the file exists or not, and the server will not attempt to read such files. The option may be specified multiple times to allow access to multiple panel files. Command-line example: run_displayserver -permitpanel:PANELS.ini -permitpanel:layout.xml DISPLAYSERVER.ini example: permitpanel PANELS.ini permitpanel layout.xml In addition, the display server supports another new option to prevent attempts to load remote files, as follows: -permitfile:LOCAL_ONLY If that option is specified any rtv or image files that are referenced by URL will not be read and the server will log a message similar to the following: non-local file read permission denied: http://host/somefile

21912: Fixed phishing vulnerabilities in thin client

In prior releases, it was possible to create phishing URLs which appeared to be directed at the rtview thin client but would redirect the user to another site, or download and possibly execute a file. These vulnerabilities have been fixed.

Platform Support

21871: Support for Java 1.6 dropped

RTView is now built with Java 1.7. Java 1.6 is no longer supported.

Version 3.6.0 Release Notes

Deployment

21748: Fixed an issue where Unix data servers sometimes failed to shut down

In previous releases, using stop_rtv on Unix platforms to stop a TIBCO solution package data server process sometimes failed due to a spurious rvd process. This has been fixed.

Distribution

21846: New RTView Monitor for Solace - AMI option

RTView Monitor for Solace is now available pre-installed on an Amazon EC2 Amazon Machine Image (AMI) running Amazon Linux. It comes pre-installed with a 30-day license, and is configured to start all RTView processes and supporting services on restart. The AMI includes the following application stack for convenience of quick deployment. Please refer to /home/ec2-user/amibase/MANIFEST.txt for the full version info: Oracle Java 8 Node Docker MySQL 5.7 (via Docker) for storage of historical data rtvHostAgent (via Docker) for providing host metrics to RTVMGR cadvisor-rtview (via Docker) for providing docker metrics to RTVMGR The scripts used to create the docker containers are included in named subdirectories under /home/ec2-user/amibase, to be used as templates if you wish to recreate the containers with your preferred configuration. The MySQL database data is stored external to the docker container at /home/ec2-user/amibase/mysql/DATA. Initial Setup: You may gain access to the community rtvsolmon-VERSION-YYYYMMDD-community AMI via sl.com, at http://sl.com/solace-ami-free-trial/. We recommend starting with an instance from the t2 family, sized according to the number of Solace appliances you are monitoring. Depending on how much archival data you wish to store in the database, you may wish to increase your disk size past the default 8 GB of the AMI. After creating an instance from the rtvsolmon-VERSION-YYYYMMDD-community AMI, you will need to SSH to your instance to add the connection properties for your Solace appliance(s) to /home/ec2-user/RTViewSolaceMonitor/em-solmon/servers/solmon/sample.properties. Please see the User Guide for full details.

General

21205: Thin client table objects are now rendered as HTML5

The table objects in the EM thin client have been enhanced to provide improved filtering, sorting, and other interactive features. See the release note for 20185 for a detailed description of the new table features.

21813: Fixed an issue with group objects and wrapped diagrams

In the previous release, if the first object in a wrapped diagram was defined to be included in a group, it was not included in the group object. This has been fixed.

RTVMGR

21739: Enhanced the All JVMs Heatmap display with a Source drop down

A drop down for Source has been added to the All JVMs heatmap display.

21740: Enhanced the All JVMs Table display with a Source drop down

A drop down for Source has been added to the All JVMs Table display.

21754: Fixed an issue preventing JVM Runtime data collection

A bug that prevented collection of JVM Runtime data from several versions of Java (6, 7 and 8 versions) has been fixed.

21792: Enhanced the All JVMs Table display with more columns

PID, Host Name, Current Heap, and Used Heap have been added to the All JVMs Table display.

21793: Enhanced the All JVMs Heatmap display

The All JVMs Heatmap display from RTVMGR Solution Package has been enhanced to include PID, Current Heap, and Used Heap. The last two metrics are also included in the Metric drop down.

21838: Enhanced RTVMGR in SOLMON Bundle

The RTVMGR configuration has been enhanced in RTView Monitor for Solace. It now includes monitoring for a MySQL Database, as well as Host and Docker metrics. For users of the RTView Monitor for Solace AMI version, all connection properties populate these displays have been pre-configured in the standard sample.properties file and do not require further configuration. Users of the On Premise version will not see data in the Host or MySQL displays unless they choose to configure these.

RTView Core Functionality

Alerts

21795: Fixed an issue where the Cleared Reason for an alert was incorrect

In prevous releases, the Cleared Reason was sometimes incorrect after an alert was disabled and re-enabled. This has been fixed.

Data Historian

21699: Enhanced Historian compaction to avoid long delays

The Historian smooth compaction code no longer performs a row count. This prevents long delays during smoothing by avoiding Select Count(*) calls.

Display Server

21772: Extra-bold font in Firefox fixed

In the previous release, objects using font index 7 (sans-serif bold) would appear extra bold in some versions of Firefox if the display server was configured to use the extended font feature with arimob.ttf assigned to font 7. This has been fixed.

21853: Fixed an issue with small numbers not updating to zero in the thin client

In previous releases, the value displayed in an obj_rect_ilv object would not change if the previous value was greater than zero and less than one, and a value of zero was applied. This problem occurred only in the thin client and is now fixed.

Scripts

21714: Added Unix scripts to create .war files for a given solution package

The script make_package_wars.sh has been added to the rtvapm distribution. Like make_package_wars.bat, it is used to create an initial set of war files for a given solution package. The war files are created in the <package>/webapps directory. After they are created, update_wars.bat/sh should be run to update them with the correct port numbers. The scripts should be run from the <package>/webapps directory. They take the package name as argument, e.g. "make_package_wars.sh bwmon".

21771: Fixed an issue where ports were misidentified

The rtvapm start/stop/status scripts, when testing the ports of a given server, would incorrectly identify a port as "taken" whose number contained the server's number with a leading or trailing digit. (For example finding 33675 in use and saying 3675 is taken.) This has been corrected.

Solution Package

Solace

21697: Fixed an issue preventing Tomcat from stopping cleanly

A bug that prevented Tomcat from stopping cleanly on UNIX and Linux systems has been fixed. The CATALINA_PID variable is now defined in the Tomcat setenv.sh script for these systems. Also, the start_tomcat.sh script requirement of JAVA_HOME being set in the environment has been changed to require Java available in the PATH. This change will allow starting RTView processes at startup before the user environment has been set.

21786: All Endpoints Table display enhanced with two new check boxes

Two new check boxes to filter by Expired and Down have been added to the All Endpoints Table display.

21787: All VPNs Table display enhanced with two new check boxes

Two new check boxes to filter by Expired and Disabled have been added to the All VPNs Table display.

21788: All Clients Table display enhanced with two new check boxes

The All Clients Table display has been enhanced by adding two check boxes to filter by Expired and Internal. By default, Expired and Disabled check boxes are unchecked, meaning that only non-expired of the Primary Type Clients are shown. When checked, all Clients, expired and non-expired as well as Primary and Internal will be respectively shown.

21789: All CSPF Neighbors Table display enhanced with two new check boxes

Two new check boxes for State Ok and Expired have been added to the All CSPF Neighbors Table display. By default both check boxes are unchecked, meaning that all non-expired CSPF Neighbors are shown. When Ok is checked, only CSPF Neighbors with State=Ok are shown. When Expired is checked all CSPF Neighbors, expired and non-expired are shown in the table.

21790: All Bridges Table display enhanced with two new check boxes

Two new check boxes for "Disabled" and "Expired" have been added to the All Bridges Table display. By default the "Expired" check box is unchecked, meaning that only non-expired Bridges are shown, and the "Disabled" check box is checked, which shows all Bridges regardless of their Admin State. When "Disabled" is unchecked, only enabled Bridges with Admin State=Enabled are shown. When "Expired" is checked, all expired Bridges are shown in the table, in addition to the non-expired Bridges.

21799: CSPF cache enhanced with Ingress/Egress metrics

Ingress and Egress metrics for CSPF Neighbor Msg Routers have been added.


21800: New CSPF Ingress/Egress metrics are now available

Ingress/Egress metrics for CSPF Neighbor Msg Routers have been stored in history from the CSPH Neighbor cache. The table creation SQL statement for supported platforms is located in solmon/dbconfig directory. The name of the table is SOL_CSPF_NEIGHBOR. By default, data is being stored in history for this table. To disable storage of historical data, edit the sample.properties file and uncomment the following property: collector.sl.rtview.sub=$SOL_CSPF_NEIGHBOR_TABLE:''

21801: SolAppliances cache enhanced with two new metrics

Two new metrics have been included in the SolAppliances cache. Host Address and Connected. The later keeps track of the connection state of the Msg Router.

21803: Message Router Summary display enhanced with Host Address

The Host Address has been added to the header of the Msg Router Summary display.

21804: EM enhanced with a new alert

A new alert,SolMsgRouterNotConnected, has been added. This alert will be executed when the Msg Router is not ready for collecting monitoring data.

21807: SOLMON tables functionality enhanced

All tabular displays now select a row by single clicking and drill down to the corresponding summary by double clicking. The enhanced displays are the following: - Message Routers->All Message Routers Table - Neighbors-> CSPH Neigbors Table - VPNs->All VPNs Table - Clients->All Clients Table - Bridges-> All Bridges Table - Endpoints-> All Endpoints Table - Capacity Analysis-> All Msg Routers Capacity

21808: All Msg Routers Heatmap display has been enhanced

Two check boxes, "Connected" and "Expired", have been added to the All Msg Routers Heatmap display.

21809: Enhanced some displays to correctly align their contents

The Msg Router and the Capacity displays for the corresponding menu tags have been enhanced to correctly align their contents.

21810: Enhanced EM with a new page for CSPF Neighbors

The CSPF Neighbor Msg Router displays have been organised under a new menu tab named Neighbors.

21812: Msg Router VPN Activity display has been enhanced

The Msg Router VPN Activity display has been enhanced to show the most active VPNs sorted by Client Connections, Ingress/Egress bytes / sec and Pending Msgs. The number of VPNs shown is adjusted to the height of the window.

21814: EM enhanced with new metrics

In Msgs /sec and Out Msgs / sec have been added to the SOLMON-MSGROUTER CI Type as Key Metrics.

21817: Trend Value precision is now one decimal value in Client Summary display

The precision of the trend values has been changed to one decimal value in the Client Summary display.

21827: Enhanced EM by standardizing colors across multiple displays

The following displays have been improved to follow RTView EM standards on color trends: - Message Router Capacity Summary - Message Router Capacity Trends - Single Message Router Summary - Single Bridge Summary - Single Client Summary - Single Endpoint Summary - Single VPN Summary