[BZ 1128779] Add vertical scrollbar to the listGrid if it does not fit the window
Bug 1029409 - Auto-enable ejb3 statistics when a user requests calltime
metrics for EJBs

Whenever callTime metric is requested, ensure that global EJB3 statistics
are enabled on server.
[822173, 1146846] Broken layout on JBossAS7 resource configuration page
Work done for Bug 1144459 was unknowingly trying to fix the problem
reported in Bug 822173.  It succeeded in fixing the column header issue
but caused the regression reported in Bug 1146846.  This (finally) seems
to have fixed the problems for all three BZs, working around the Smartgwt
bug at the root of all of the problems.
[BZ 1144052] - On group creation error, info messages are under fadeout window - the z-index css attribute was ignored, because there were two different so called stacking contexts. By setting the z-index to the default value (which is auto) to all related parent elements we prevent creating new stacking contexts. In other words z-index works correctly only for leave elements in the DOM tree, but if we combine different z-indices in one sub-tree it causes strange behavior.
[BZ 1146228] - Metric detail hover is missing from graphs - this was caused by "! important" in style definition in patternfly.css because it overrided the elements style attribute (where we programatically set if the hover is shown of hidden). I've created a new css style called rhqHidden where the "! important" is not used.
BZ 1145683 - change if-stmt so it can work on solaris 10 - semantics slightly change, but since we don't support JVMs lower than 1.6 that means that effectively this doesn't change functionality
[BZ 1112733] Define expressionScope baseResource to the option-source
[BZ 873471] - Correctly resolve relative paths against not-yet existing deploy dirs.
[BZ 1148186] Use eval to execute the RHQ agent start command. It was incorrectly sourced in the current script. Note that only config and full config were affected. Also, adjusted the order for defining and export RHQ home to allow proper overrides int RHQ environment script.
[BZ 1082805] Simplify the upgrade options for the data migration. Only allow to run the data migration. For a fine control over the upgrade process prompt the users to the migration tool directly.
Bug 1029409 - Auto-enable ejb3 statistics when a user requests calltime
metrics for EJBs

Fix NPE when enable-statistics is undefined
[BZ 1144052] - Setting z-index to auto to all parents of the logout dropdown menu to join its DOM subtree to the global stacking context and make the z-index working again for it. Result is that it will be on the top even if there is a notification. Also hiding the ajax loader gif icon, because it is not needed anymore.
Bug 1144146 - Messaging queue and subscriber runtime is not exposed

Added 2 new resource types to AS7 plugin (for Standalone and Managed server)
with supportsMissingAvailabilityType="true", because runtime-queues and
topic subscribers will likely appear and disappear.

BaseComponent#getAvailability() was fixed to support
supportsMissingAvailabilityType=true whenever it is defined in resource
type.
[BZ 1082805] Simplify the upgrade options for the data migration. Remove more undeeded code.
BZ 1145338 - to support NAT environments, allow server to be configured with a public port/secureport when it is installed
Move purge settings to a new "Advanced Purge Settings" group (hidden by default)
Bug 1145776 - RHQ_PARTITION_EVENT data not purged automatically

Added partition event and partition event details purge
It's disabled by default and configurable through System Settings.

Added partition event test in DataPurgeJobTest

Also, refactoring DataPurgeJob and DataPurgeJobTest
Bug 1139433 - Deadlock in deletion of RHQ_RESOURCE_ERROR, possibly in resource upgrade?

When saving a resource error, we first delete existing errors if the error type is one of:
* INVALID_PLUGIN_CONFIGURATION
* AVAILABILITY_CHECK
* UPGRADE
I'm not sure why we don't if the error type is DISABLED_TYPE.

The goal is to keep only one copy of these error types.

Here's my analysis of the deadlock report attached to the BZ.

Due to the type of locks (row locks) and the queries involved, it looks like the deadlock is the consequence of concurrent calls to ResourceManagerBean#clearResourceConfigErrorByType with the same parameters. Such concurrent calls would not necessarily lead to a deadlock. It would happen only if the row locking order is different. My knowledge of Oracle is limited but I'd say this is possible if the two queries get a different execution plan. I tried to figure out why the same query could lead to a different execution plan and one possible reason would be that one is using the index on resourceId and the other one is not.

This commit addresses the issue by changing the way previous errors are deleted. Now before delete we select an ordered list of primary keys. Then we delete the rows by primary key. Consequently, two competing sessions will never lock rows in different orders.

There's another issue due to the way resource errors are implemented. Two competing sessions will delete previous errors but both will insert a row. A DataPurgeJob task has been added to remove such duplicates, if any.