glassfish
  1. glassfish
  2. GLASSFISH-17956

Cluster creation should fail if MQ configuration fails

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.2_b14
    • Fix Version/s: 3.1.2_b14
    • Component/s: admin_gui
    • Labels:
      None

      Description

      From DHQA: cluster creation should fail if MQ configuration fails, since it is very hard for users to fix the MQ configuration issues (outside of Admin Console).

        Activity

        Hide
        Anissa Lam added a comment -

        I think printing out the error or warning should be enough, no ? It is up to the user whether they want to delete and re-create another cluster.

        Show
        Anissa Lam added a comment - I think printing out the error or warning should be enough, no ? It is up to the user whether they want to delete and re-create another cluster.
        Hide
        Jason Lee added a comment -

        Changes committed to branch (r51435) and trunk (r51436).

        Show
        Jason Lee added a comment - Changes committed to branch (r51435) and trunk (r51436).
        Hide
        lidiam added a comment -

        This was tested by Sarada and error messages are displayed. Details below (the first item is not configurable on this screen, so does not apply to this bug).

        1. If you provide wrong MQ information (like wrong user/password for jdbc or forget to copy jdbc driver) then instances will run successfully but broker fails to start.

        In that case you can always go back to availability page to correct the information you have provided with the recent changes to admin gui.

        2. Validating the fields

        If you don't provide jdbc url for mq in create cluster page then the glassfish admin throws the appropriate error

        The server cluster has NOT been created. An error occurred while configuring the JMS cluster:
        No JDBC URL specified

        Similarly, for the wrong db vendor:

        The server cluster has NOT been created. An error occurred while configuring the JMS cluster:
        Invalid DB Vednor specified

        Show
        lidiam added a comment - This was tested by Sarada and error messages are displayed. Details below (the first item is not configurable on this screen, so does not apply to this bug). 1. If you provide wrong MQ information (like wrong user/password for jdbc or forget to copy jdbc driver) then instances will run successfully but broker fails to start. In that case you can always go back to availability page to correct the information you have provided with the recent changes to admin gui. 2. Validating the fields If you don't provide jdbc url for mq in create cluster page then the glassfish admin throws the appropriate error The server cluster has NOT been created. An error occurred while configuring the JMS cluster: No JDBC URL specified Similarly, for the wrong db vendor: The server cluster has NOT been created. An error occurred while configuring the JMS cluster: Invalid DB Vednor specified

          People

          • Assignee:
            Jason Lee
            Reporter:
            lidiam
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: