Release Notes Release Notes

Release Notes Release Notes

Fixed Limitations

The following table lists the issues that are resolved in RulePoint 6.2:
CR
Description
402304
When you configure multiple domains for LDAP, the user and group filters does not function properly.
401961
If the RulePoint processes, such as the UM lbmrd, UM store, grid manager, and node take a long time to start up, the HostAgent process times out.
401795
When you add an application service to the topology, and restart the topology, the dashboard stops unexpectedly if you have not deployed objects in that application service.
401563
If you select the Oracle database for the RulePoint installation, and the password of the RulePoint user begins with special characters, the installation fails.
401110
When you perform CRUD operations on RulePoint objects, the RulePoint java adapter does not work for some locales and generates an exception.
400549
You cannot configure the activity manager for high availability.
400547
When the ActiveMQ server shuts down, the JMS source and responder cannot reconnect to an ActiveMQ instance.
400546
The deployed JMS source and responder display errors on the dashboard if they are unable to connect to the ActiveMQ server. The error continues to appear even after the ActiveMQ server starts and is accessible.
400544
In a topology that contains three UM stores, two of the UM stores do not receive the same messages.
400542
When you specify the event set behavior, you cannot remove all previous events and keep only the latest event in future evaluation.
399373
The host agent process starts when you start the topology process through Windows services.
396443
When you forward RTAM alerts generated for one RulePoint user to other RTAM or RulePoint users, an error occurs.
395974
When you add a web services response to a wizard rule, and then edit the response, the
Edit Response
dialog box displays incorrect property names for the web services responder with nested WSDL.
393645
The input parameters fields for a web services responder in the RulePoint console do not appear correctly.
393576
RulePoint does not support nested WSDLs and xsd.
393575
RulePoint does not support SOAP 1.2 for web services.
393570
If you leave the topic field blank when you configure an event transformer responder, the responder controller in which the event transformer responder is deployed displays an error.
392734
If you configure an event transformer responder with an existing topic, you cannot delete that topic even after you remove its reference from the responder.
392686
RulePoint does not support LDAP with SSL encryption.
392590
If you configure multiple connections in RulePoint configured with the H2 database, the database becomes unstable and RulePoint stops unexpectedly.
392589
A unique constraint violation error occurs when you try to add a schedule to a source.
392580
You might encounter issues starting the RulePoint components if you have Internet connectivity issues.
392570
If you do not set the system default locale to English, the import fails when you import the uploaded files to RulePoint.
390812
You cannot send or receive JMS byte array message types through the JMS source or responders.
390810
If you use the same event transformer in two or more rules, the event transformer does not forward the events to the configured topic.
388807
If you use an event transformer response in a rule that has marker topics, alerts are not sent to target topics.
386520
When you update the OSGI bundle, the states of the objects are not valid.
381784
If you create a rule that contains multiple topics in the DRQL, the rule trace summary on the dashboard does not show the accurate number of activations.
381539
When you copy the wizard rule whose referenced topic property is deleted, an internal server error occurs.
380597
The log viewer might display messages with epoch time instead of the required date format.
380266
Parallel processing for rules is enabled by default.
379778
If you have installed RulePoint on AIX and Solaris, you might not receive RTAM alerts.

0 COMMENTS

We’d like to hear from you!