[rhq-project/rhq] 94a3d1: Hiding the Resource Ancestry column in {Alerts|Eve...
by Jiri Kremser
Branch: refs/heads/master
Home: https://github.com/rhq-project/rhq
Commit: 94a3d1e21acd212cb05409b3f01bbea0e735597f
https://github.com/rhq-project/rhq/commit/94a3d1e21acd212cb05409b3f01bbea...
Author: Jirka Kremser <jkremser(a)redhat.com>
Date: 2014-04-17 (Thu, 17 Apr 2014)
Changed paths:
M modules/enterprise/gui/coregui/src/main/java/org/rhq/coregui/client/alert/AlertDataSource.java
M modules/enterprise/gui/coregui/src/main/java/org/rhq/coregui/client/alert/AlertHistoryView.java
M modules/enterprise/gui/coregui/src/main/java/org/rhq/coregui/client/dashboard/portlets/groups/GroupAlertsPortlet.java
M modules/enterprise/gui/coregui/src/main/java/org/rhq/coregui/client/dashboard/portlets/recent/alerts/AbstractRecentAlertsPortlet.java
M modules/enterprise/gui/coregui/src/main/java/org/rhq/coregui/client/dashboard/portlets/recent/events/AbstractRecentEventsPortlet.java
M modules/enterprise/gui/coregui/src/main/java/org/rhq/coregui/client/inventory/common/event/EventCompositeDatasource.java
Log Message:
-----------
Hiding the Resource Ancestry column in {Alerts|Events} Portlets not to overwhelm user with bazillion columns. It can be shown if necessary. Also fixing a typo that caused to displayed Group Events Portlet instead of Alert Group Portlet.
10 years, 1 month
[rhq-project/rhq] 937cb2: [BZ 1088264] AvailabilityExecutor stops calling ge...
by Libor Zoubek
Branch: refs/heads/master
Home: https://github.com/rhq-project/rhq
Commit: 937cb29ee5450da0bcf04d8e9952310de400e90b
https://github.com/rhq-project/rhq/commit/937cb29ee5450da0bcf04d8e9952310...
Author: Libor Zoubek <lzoubek(a)redhat.com>
Date: 2014-04-17 (Thu, 17 Apr 2014)
Changed paths:
M modules/core/plugin-container/src/main/java/org/rhq/core/pc/inventory/AvailabilityProxy.java
Log Message:
-----------
[BZ 1088264] AvailabilityExecutor stops calling getAvailability() on
ResourceComponent after it previously failed with exception
The issue was in handling exception comming from future. When availability
check failed with exception we cought it, next run, just by calling
future.get() raises the very same exception. We forgot to mark future to be
rescheduled next time = setting it to null. This commit also makes exception
message more verbose so we know more what happened in plugin
10 years, 1 month