Universal Messaging 10.15 | Resolved Issues | Release 10.4
 
Release 10.4
*NUM-10669 (Channels and queues are not sorted in the EM tree)
The Universal Messaging Enterprise Manager previously did not display newly added channels or queues in alphabetical order.
The issue is resolved.
*NUM-10754 (UM Tools for manipulation of JMS artifacts fail when used with authentication)
The issue is that beside the usual connection which is properly supported for authentication, there is a JNDI connection required where credentials were hardcoded. The credentials provided via the command line are now also used by the JNDI connection.
The issue is resolved.
*NUM-10872 (Enterprise Manager slows down while editing channels or queues)
Previously, when editing channels or queues in the Enterprise Manager, the processing became slower after each save operation. When you edited channels or queues nested in several containers (folders) in the Enterprise Manager, the time for saving your changes increased with each save operation.
The issue is resolved.
*NUM-10944 (Batch Purge performance)
Event purge performance has been improved in the case where there is an indexed durable (Shared or Serial) attached to a store.
*NUM-10945 (Problem when editing a queue in Enterprise Manager)
Editing a queue in the Universal Messaging Enterprise Manager could previously cause some events on the queue to be lost.
The issue is resolved.
*NUM-11166 (Cluster manager doesn't throttle events when queue becomes big)
Previously, in inter-cluster communication, one node could send events faster than the receiving node could process them. This could lead to an out of memory exception.
Now if the event queue becomes too big, the receiving node will throttle.
*NUM-11381 (Universal Messaging C# client only supports secure connection TLS 1.0 and SSL 3.0 protocols)
This issue is now resolved. The Universal Messaging C# client now also supports TLS 1.1 and TLS 1.2 protocols.