[rhq-project/rhq] f64d2a: Bug 1032039 - JON server cannot restart itself

[Libor Zoubek]

  Branch: refs/heads/release/jon3.3.x
  Home:   https://github.com/rhq-project/rhq
  Commit: f64d2a135b9f4dd6584a97c7601543ea4affe42d
      https://github.com/rhq-project/rhq/commit/f64d2a135b9f4dd6584a97c7601543e...
  Author: Libor Zoubek <lzoubek(a)redhat.com&gt;
  Date:   2015-03-21 (Sat, 21 Mar 2015)

  Changed paths:
    M
modules/plugins/rhq-server/src/main/java/org/rhq/plugins/server/DiscoveryCallbackImpl.java
    M
modules/plugins/rhq-server/src/main/java/org/rhq/plugins/server/ResourceUpgradeCallbackImpl.java

  Log Message:
  -----------
  Bug 1032039 - JON server cannot restart itself

The fix implements DiscoveryCallback and ResourceUpgradeCallback in
rhq-server plugin and sets proper start script parameters (uses rhqctl) for
RHQ Server resources.

When non-HA server is restarted via RHQ Server scheduled operation (agent
attempting to restart the server is also reporting to the same server)
restart operation will not succeed (although server was in fact restarted)
and it will timeout - this happens, because when agent wants to deliver
operation result to server, server goes immediatelly down (as a consequence
of restart operation) and when it comes up, agent is unable to resend
operation result data anymore (this maybe a separate bug/edge case)

(cherry picked from commit a6beed4cb9b976c50ed944e9c590215e2dca1164)
Signed-off-by: Libor Zoubek <lzoubek(a)redhat.com&gt;