Novell SENTINEL LOG MANAGER 1.0.0.4 - RELEASE NOTES Release Note page 11

5.3 Issues Fixed in Sentinel Log Manager 1.0.0.2 Release
This section lists the issues fixed in Novell Sentinel Log Manager 1.0.0.2 Release.
Issues fixed in Sentinel Log Manager 1.0.0.2 Release
Table 4
Issues Fixed
537273
536377
535736
536589
540119
541858
543029
5.4 Issues Fixed in Sentinel Log Manager 1.0.0.1 Release
This section lists the issues fixed in Novell Sentinel Log Manager 1.0.0.1 Release.
Description
Issue: Non-admin user is able to log in to the Event Source Management
interface by using a cached ESM jnlp file.
Fixed: Only authorized admin user can log in to the Event Source
Management interface.
Issue: Lucene indexes are not being committed on a timely basis.
Fixed: Lucene indexes are now being committed on a timely basis - once a
minute.
Issue: The Rule user interface does not perform the filter validation.
Fixed: The specified filter value is validated by the Rule user interface.
Issue: IndexedLogComponent can get stuck on deactivate when shutting
down under heavy load (high EPS).
Fixed: IndexedLogComponent will now shutdown gracefully under heavy
load.
Issue: When the Sentinel Log Manager Server runs for many days (for
example, 25-40 days), it stores huge amount of EPS data, which is
generated over time. This eps information is transferred to the tomcat
server in a verbose format so it consumes a lot of memory and also while
parsing the eps data it causes out of memory at the tomcat server.
Fixed: The eps data information will now be transferred in a more compact
format from the Sentinel Log manager server to the Tomcat server.
Issue: A few events that are generated on a remote Collector Manager do
not get displayed on the Sentinel Log Manager server.
Fixed: All the events that are generated on a remote Collector Manager
will be displayed on the Sentinel Log Manager server as expected.
Issue: When one Sentinel Log Manager is configured with multiple
Collector Managers. On changing a Collector for an event source under
the Collection > Syslog Server tab, the Collector and the event source gets
assigned to the wrong Collector Manager.
Fixed: On changing a Collector for an event source under the Collection >
Syslog Server tab, the Collector and the event source will be assigned to
their respective Collector Manager.
Novell Sentinel Log Manager 1.0.0.4 Release Notes 11