[GLASSFISH-19312] Replication is not happening when ' ExecuteOn(value={RuntimeType.DAS, RuntimeType.INSTANCE})' specified. Created: 09/Nov/12  Updated: 07/Feb/13  Resolved: 07/Feb/13

Status: Resolved
Project: glassfish
Component/s: admin
Affects Version/s: 4.0
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: naman_mehta Assignee: Tom Mueller
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified



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.

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}


Comment by Tom Mueller [ 07/Feb/13 ]

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:

{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.

Generated at Sat Aug 29 21:21:08 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.