When a new instance is added to an existing cluster, status for all previously running instances is changed from "running" to "restart required". Adding an instance to a cluster should not require cluster restart. This is specifically problematic, since user cannot look up the reason for restart required messages for instances other than DAS in Admin Console.
Steps to reproduce:
In Admin Console:
1. Create a cluster with one instance, e.g. cl1 with cl1in1, on localhost-domain1 node.
2. Start cluster.
3. Go to cluster cl1, Instances page and click on New.
4. Fill in the instance name, e.g. cl1in2, and click OK. Note that after creation page with instances is displayed and the existing instance, cl1in1, has status "restart required".
The same status is reported by CLI:
/export/sqe/lidia/glassfish3/glassfish/nodes/localhost-domain1/cl1in1/logs % asadmin list-instances
cl1in1 running; requires restart
cl1in2 not running
No errors or warnings are present in DAS server.log and the following warning is present in the first clustered instance server.log (cl1in1):
_ThreadName=Thread-9;|Unprocessed event : UnprocessedChangeEvent
stem-property, OldValue = null, NewValue = GlassFishConfigBean.com.sun.enterpris
e.config.serverbeans.SystemProperty, Source = GlassFishConfigBean.com.sun.enterp
, reason = The system-property, OSGI_SHELL_TELNET
_PORT, that is referenced by the Java configuration, was modified, when = 130991