glassfish
  1. glassfish
  2. GLASSFISH-16106

change-master-broker command does not map all the JMX error codes to corresponding error messages

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1
    • Fix Version/s: 4.0_b63
    • Component/s: jms
    • Labels:
      None

      Description

      The change-master-broker command currently does not map all the JMX codes returned by MQ to corresponding error messages. The following error messages are returned by imq change-masterbroker implimentation:

      Please note that the returned errorCode string from MQ JMX interface changeMasterBroker call also contains
      the statusCode in string form (like "OK", "BAD_REQUEST", ..).

      "The MQ JMX changeMasterBroker operation can return following status

      a) OK
      The operation has returned successfully. It is guaranteed that both the old master broker
      and the new master broker have switched its master broker to the new master broker.
      Any broker that is not running or network partitioned with the master broker when this command is running,
      would need to be restarted with explicit new master broker configuration.

      b) BAD_REQUEST, NOT_ALLOWED, UNAVAILABLE, PRECONDITION_FAILED
      When these status are returned, the current master broker configuration in
      the cluster is not affected.

      c) An error status other than a) and b)
      The cluster should be shutdown and configured with the new master broker as the
      master broker then restarts. "

      Except OK statusCode, all other status in string form is contained in the returned errorCode String.

        Activity

        Hide
        David Zhao added a comment -

        Revision: 56906

        Show
        David Zhao added a comment - Revision: 56906

          People

          • Assignee:
            David Zhao
            Reporter:
            Satish Kumar
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: