Start/stop cluster fails if java-config.debug-enabled property set to true

[glassfishrobot]

Experienced with SNAPSHOT build from Nov 04, 2010:

After enabling debug on a cluster via $AS_HOME/bin/asadmin set -config.java-config.debug-enabled=true

and restarting cluster, it is then no longer possible to successfully invoke asadmin stop-cluster/start-cluster commands as the execution of these commands keeps running indefinitely.

Environment

Operating System: All Platform: All

Affected Versions

[3.1]

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/glassfish/issues/14422
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @yaminikb
• Original Issue Closed By:@glassfishrobot

[glassfishrobot]

@glassfishrobot Commented tmueller said: I tested this on Linux using the build from 11/8 and was not able to reproduce the problem. Marking as WORKSFORME. If you are still seeing this with a current build, please reopen the bug and provide more detailed instructions on how to reproduce.

Here's what I did:

bash-3.2$ asadmin start-domain Waiting for domain1 to start ... Successfully started the domain : domain1 domain Location: /scratch/trm/test/glassfish3/glassfish/domains/domain1 Log File: /scratch/trm/test/glassfish3/glassfish/domains/domain1/logs/server.log Admin Port: 4848 Command start-domain executed successfully. bash-3.2$ asadmin create-cluster c1 Command create-cluster executed successfully. bash-3.2$ asadmin create-local-instance --cluster c1 i1 Rendezvoused with DAS on localhost:4848. Port Assignments for server instance i1: JMX_SYSTEM_CONNECTOR_PORT=28686 JMS_PROVIDER_PORT=27676 HTTP_LISTENER_PORT=28080 ASADMIN_LISTENER_PORT=24848 JAVA_DEBUGGER_PORT=29009 IIOP_SSL_LISTENER_PORT=23820 IIOP_LISTENER_PORT=23700 OSGI_SHELL_TELNET_PORT=26666 HTTP_SSL_LISTENER_PORT=28181 IIOP_SSL_MUTUALAUTH_PORT=23920 Command create-local-instance executed successfully. bash-3.2$ asadmin create-local-instance --cluster c1 i2 Using DAS host localhost and port 4848 from existing das.properties for node localhost. To use a different DAS, create a new node using create-node-ssh or create-node-config. Create the instance with the new node and correct host and port: asadmin --host das_host --port das_port create-local-instance --node node_name instance_name. Rendezvoused with DAS on localhost:4848. Port Assignments for server instance i2: JMX_SYSTEM_CONNECTOR_PORT=28687 JMS_PROVIDER_PORT=27677 HTTP_LISTENER_PORT=28081 ASADMIN_LISTENER_PORT=24849 JAVA_DEBUGGER_PORT=29010 IIOP_SSL_LISTENER_PORT=23821 IIOP_LISTENER_PORT=23701 OSGI_SHELL_TELNET_PORT=26667 HTTP_SSL_LISTENER_PORT=28182 IIOP_SSL_MUTUALAUTH_PORT=23921 WARNING : Instance i1 seems to be offline; Command was not replicated to that instance Command create-local-instance executed successfully. bash-3.2$ asadmin start-cluster c1 Command start-cluster executed successfully. bash-3.2$ asadmin set c1-config.java-config.debug-enabled=true i1 : c1-config.java-config.debug-enabled=true

i2 : c1-config.java-config.debug-enabled=true

c1-config.java-config.debug-enabled=true Command set executed successfully. bash-3.2$ asadmin stop-cluster c1 Command stop-cluster executed successfully. bash-3.2$ asadmin start-cluster c1 Command start-cluster executed successfully. bash-3.2$ asadmin stop-cluster c1 Command stop-cluster executed successfully. bash-3.2$ asadmin list-instances i1 not running i2 not running Command list-instances executed successfully. bash-3.2$ asadmin start-cluster c1 Command start-cluster executed successfully. bash-3.2$ asadmin list-instances i1 running i2 running Command list-instances executed successfully. bash-3.2$ asadmin stop-cluster c1 Command stop-cluster executed successfully. bash-3.2$

[glassfishrobot]

@glassfishrobot Commented Was assigned to tmueller

[glassfishrobot]

@glassfishrobot Commented This issue was imported from java.net JIRA GLASSFISH-14422

[glassfishrobot]

@glassfishrobot Commented Reported by @mpotociar

[glassfishrobot]

@glassfishrobot Commented Marked as cannot reproduce on Monday, November 8th 2010, 6:17:59 am