UMDS Release Notes
Known Limitations for UMDS

The following open limitations applies to the UMDS product.

Change Request

Description

8411

License keys including the UMSM product option are not recognized as valid when running a version of Ultra Messaging earlier than 6.5. The UMSM license is only required to run the System Monitoring components. Enabling monitoring of applications and other products does not require a license containing UMSM.

8579

The UMDSMessage low_seqnum field is not the low sequence number of a fragmented message as documented. Instead, it contains the seqnum field value.

8581

Sending request messages on a topic subscribed by a pre-6.0 UMDS client causes the client to disconnect from the UMDS server with the following log message:

WARNING :Error reading parameter 49:com.latencybusters.umds.UMDS+UMDSException:
Bad data hdrid in UMDSMessageFormatter.parse()

8582

The UMDS web monitor incorrectly displays can-reqresp=1 on the client details page for older UMDS clients that do not have the capability to participate in request/response.

8586

If UM automatic monitoring is enabled on the server with an invalid monitoring configuration, the server does not properly report the configuration error, but instead issues log messages such as the following example:

Warning: Attempt to send data to tidx 0 when source not initialized

8587

For a source that matches a wildcard receiver pattern, creates a per-topic queue, then ends, the per-topic queue is not deleted until the wildcard receiver gets deleted.

8695

If the UMDS Server is running with Ultra Messaging 6.7 or earlier, UMDS Client receivers do not correctly format responses to request messages that have traversed a UM Router from sources in a different Topic Resolution Domain. Instead of delivering such response messages, the originating requester logs the following warning message:

Core-6259-25: Deserialize Response: Context in domain 1 received response with
no domain:...

9078

The UMDS Server might crash under the following conditions:

  • LBM_DEBUG_MASK is set to a value that includes the 0x10 topic resolution bit.
  • The UMDS Server is running with Ultra Messaging 6.7 or earlier.

To avoid this problem, do one of the following:

  • Do not set LBM_DEBUG_MASK to a value that includes the 0x10 topic resolution bit.
  • Upgrade to a version of Ultra Messaging later than 6.7.

9118

The umdsresponse sample application erroneously requires an argument for the wildcard command-line option -W. To work around this limitation, either supply a dummy argument, such as "<tt>-W dummy</tt>" or add a case 'W': near line 90 of the umdsresponse.cs file.

9129

You cannot set option umq_queue_name. If you set this option, instead of flagging error during the source create and exiting the source create, Ultra Messaging attempts to send and then logs the following warning message:

[warning] Umds-8499-2: LBM error while sending message: CoreApi-5688-707:
Not currently registered with enough UMQ queue instances

9130

You cannot use Request-Response with MIM.

9131

If you send a Request on a topic where no topic queue is configured, Ultra Messaging creates a per-topic queue anyway. This queue is unbound in size, although Requests do time out. For full control, configure a topic queue with size limit on these topics.

9132

If a wildcard receiver matches a topic for which no per-topic queue is configured, Ultra Messaging creates a per-topic queue anyway, but then still uses the default queue to deliver that topic's messages, and not the per-topic queue.

9133

If option <server-reconnect> is at the default settings of 0 and client-write=yes, and you have not set the UMDS Client to reconnect with the setProperty() API, a disconnected UMDS Client does not reconnect as expected. To insure proper behavior, use the setProperty() API to configure the UMDS Client for the desired reconnect mode.

9134 Server reports the client authentication indicated by the client not the authentication method used by the server. When the server is configured for authentication none, and the client supplies an application name and / or a user name and password, the server will report that authentication type basic was used, when it was not.