irc-bot: commit link now points to the GitHub
[BZ 1005922] - Selecting grouped fired alerts in chosen time range does not work - hiding the filters if the alerts are shown in the grouped mode and vice versa.
 [BZ 1034236] fix problem with ldap ssl configuration parsing.
  - this is fallout from a global property change/deprecation that happened
    months back and we missed one property being chnaged from String to boolean.
Bug 1033520 - CLI returns exit code 0 even when an error occurs

In non interactive mode, exit code is 1 if :
* an error occurs while executing a command or a script
* login failed
* script file does not exist
Bug 963160 - CLI does not allow resource group plugin configuration update
Bug 1034218 - EAR subdeployments are not discovered for DomainDeployment
[BZ1034991]  Summary Last Metrics values are different values than Chart Last Metric values.
[BZ 1035022] Allow schema specific exceptions to bubble up without being wrapped into a Runtime exception.
[BZ 1034852] time range change in summary->activity doesn't change time range in monitoring->metrics
[BZ 1035280] - Cannot load metrics for platform resource created using rest api - adding a check whether the agent is the dummy one for MeasurementDataManagerBean.findLiveData() and ResourceManagerBean.getLiveAvailability().
[BZ 891876] - JON login screen does not appear in IE9 - adding the 'noscript' element that will show the warning if the browser has the JavaScript disabled.
 [BZ 1034236] One more property check for original and updated property parsing.
[1023019] Windows 2008 - Upgrade to JON3.2.ER3 freezes on 'Updating RHQ Agent Service'
rhqctl-based  installs will now exit if the password is not set when the RUN_AS
option is specified. The RHQ_XXX_PASSWORD_PROMPT env vars are no
longer relevant or documented for rhqctl-based installs. Note that
the agent is typically installed standalone, outside of rhqctl, and in
that case the RHQ_AGENT_PASSWORD_PROMPT env var is still relevant.

Additionally, rhq-agent.bat had some newly discovered problems handling
certain options (32-bit java install, I think), and has had a decent
amount of reworking to deal with the issues.
[BZ 997669] Tomcat Web Application (WAR)" components stay down when server comes back up.
Submitted by Thomas Segismont (tsegismo@redhat.com)
[BZ 1017961]  JMX Plugin can fail testing for registration
Submitted by Thomas Segismont (tsegismo@redhat.com)
[BZ 1035767] - Enable altering count query along with alterProjection
If CriteriaQueryGeneration.alterProjection changes the projection such
that the actual number of returned results changes (e.g. using distinct),
the default count query would no longer match and the returned results
would be inconsistent with the count found by the count query.

Because alterProjection is essentially free-form JPQL, we need to provide
a similar means to alter the count query so that the data query and count
query can be modified to return consistent data.
Bug 1033130 - [AS7] Exception during discovery of Query Cache resources of RHQ Server resource

Query Cache management nodes have a very long name. So the default discovery class was creating a too long resource key and name.

Now there is a dedicated discovery class for Query Cache resources and the resource key and name are just the hash of the query-name attribute.
[BZ 971615] Tomcat plugin ignores processes if container running as 'rhq' user
Submitted by Elias Ross (genman@noderunner.net)
Bug 1030063 - Clean up plugin update to work synchronously

The plugin update is problematic as it is driven by listener ordering and possibly has many race conditions like seen in Bug 1025844. For example, the listener is actually added before the plugin container starts. Although effectively, the dependent systems are initialized before be the listener is called, this is not something predictable or clear.

The other weird thing is a lot of polling (of directory states, etc.) for a count of files. There is no notion of completed state, i.e. the update actually completed.

I've seen agents come up with the old version of plugins (like if the server blocked for a very long time), etc.

Using marker files isn't terribly reliable either, and not really helpful. Maybe it is a diagnostic feature, but why not use a static semaphore to order updates?

Anyway, my patch is simply having AgentMain do (more or less):

   new PluginUpdate(...).updatePlugins()

when the server starts.
[BZ 1035816] Fix handling of "disable after fire" definitions.