glassfish
  1. glassfish
  2. GLASSFISH-19312

Replication is not happening when ' ExecuteOn(value={RuntimeType.DAS, RuntimeType.INSTANCE})' specified.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 4.0
    • Fix Version/s: 4.0
    • Component/s: admin
    • Labels:
      None
    • Environment:

      ALL

      Description

      I have CreateJdbcResource command which has '@ExecuteOn(RuntimeType.ALL)' initially and it works fine with proper replication of domain.xml changes.

      Now I changed it to 'ExecuteOn(value=

      {RuntimeType.DAS, RuntimeType.INSTANCE})' but couldn't find replication is happening on stand alone instance and clustered instances.

      I have also SetLogLevel command which has '@ExecuteOn({RuntimeType.DAS, RuntimeType.INSTANCE}

      )' and it works fine with proper replication. It updates logging.properties file under instance config directory also.

      So,
      1. Why domain.xml changes is not replicated for CreateJdbcResource command during 'ExecuteOn(value=

      {RuntimeType.DAS, RuntimeType.INSTANCE})'? It works fine when we have '@ExecuteOn(RuntimeType.ALL)'.
      2. What is the difference between @ExecuteOn(value={RuntimeType.ALL}) and ExecuteOn(value={RuntimeType.DAS, RuntimeType.INSTANCE}

      )?

        Activity

        Hide
        Tom Mueller added a comment -

        I tried reproducing this on the latest build but I'm not seeing it. Here's what I did:

        1) Change the @ExecuteOn in CreateJdbcResource.java to:
        @ExecuteOn(value=

        {RuntimeType.DAS, RuntimeType.INSTANCE}

        )

        2) Run the following commands after a fresh install

        $ asadmin start-domain
        $ asadmin create-local-instance i1
        $ asadmin start-local-instance i1
        $ asadmin create-jdbc-resource --connectionpoolid DerbyPool --target i1 jdbc/j2
        JDBC resource jdbc/j2 created successfully.
        JDBC resource jdbc/j2 created successfully.
        Command create-jdbc-resource executed successfully.

        After this command was executed, I checked the domain.xml for the i1 instance and it had the jdbc/j2 entry, so the command was replicated.

        If you are still seeing this, please reopen the issue and provide more detailed instructions as to how to reproduce this problem.

        Show
        Tom Mueller added a comment - I tried reproducing this on the latest build but I'm not seeing it. Here's what I did: 1) Change the @ExecuteOn in CreateJdbcResource.java to: @ExecuteOn(value= {RuntimeType.DAS, RuntimeType.INSTANCE} ) 2) Run the following commands after a fresh install $ asadmin start-domain $ asadmin create-local-instance i1 $ asadmin start-local-instance i1 $ asadmin create-jdbc-resource --connectionpoolid DerbyPool --target i1 jdbc/j2 JDBC resource jdbc/j2 created successfully. JDBC resource jdbc/j2 created successfully. Command create-jdbc-resource executed successfully. After this command was executed, I checked the domain.xml for the i1 instance and it had the jdbc/j2 entry, so the command was replicated. If you are still seeing this, please reopen the issue and provide more detailed instructions as to how to reproduce this problem.

          People

          • Assignee:
            Tom Mueller
            Reporter:
            naman_mehta
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: