This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
NB 6.0 200709280000 Web and Java 2 EE & jdk 1.6 u1. All the setups are done with Administrator. Install netbeans without GF V2 in C:\Program Files unselect the GF V2 bundled. Download GF V2 FCS and install in cluster mode, Use the 'ant -f setup-cluster.xml' in C:\Program Files follow the instructions from Vince: 1- create a testpassword.txt file with the 2 lines AS_ADMIN_PASSWORD=adminadmin AS_ADMIN_MASTERPASSWORD=changeit saved as C:\Program Files\glassfish-v2-fcs\testpassword.txt 2. In A command prompt window, change directory till C:\Program Files\glassfish-v2-fcs\glassfish\bin and execute: > asadmin start-domain > asadmin create-node-agent na > asadmin start-node-agent --startinstances=false --passwordfile /tmp/testpassword na > asadmin create-cluster c1 > asadmin create-instance --cluster c1 --nodeagent na i1 3. Start IDE and register the server domain1-cluster, type GF V2, Platform Location C:\Program Files\glassfish-v2-fcs\glassfish admin user: admin password: adminadmin =>>> status is OK domain start in normal mode 4. Create a new web application (Hello World jsp.index), Run the project =>>> deployment is ok, got the browser 5. Create a new web application (BreakGFix), add to it a Web Service with two operations: String op1(), String op2(String) 6. In project "Undeploy & Deploy" BreakGFix ==>>> deployment is ok (expand Services/Servers/domain1-cluster) 7. Stop the server using "Stop" item in Services/Servers/domain1-cluster) ==>>> ok status is stopped 8. Start the server in normal mode using "Start" item in Services/Servers/domain1-cluster ===>>> Got the IDE-ERROR window: <<The Sun Java System Application Server could not start. More information about the cause is in the Server log file. with the 5 reasons >> will join the server.log file, and the snapshot of the window.
Created attachment 49864 [details] domain1 (cluster) log file
Created attachment 49865 [details] rdesktop & IDE windows
The domain1-cluster server in IDE has the status stopped, "Refresh" item from Services/servers/domain1-cluster does not change the status. > asadmin list-domains ==>> domain1 is running > asadmin list-clusters and list-node-agents ==>> Unable to connect to admin-server at given host: [localhost] and port: [4848]. Please check if this server is up and running and that the host and port provided are correct. CLI137 Command list-clusters failed. changing the priority from P3-P2.
Created attachment 49866 [details] na nodeagent server.log
Created attachment 49867 [details] i1 server.log
in 2. cmd executed is as: > asadmin start-node-agent --startinstances=false --passwordfile C:\Program Files\glassfish-v2-fcs\testpassword.txt na
*** was able to stop the domain using asadmin. WEB0303: Stopping Sun-Java-System/Application-Server. WEB0713: Stopping Sun-Java-System/Application-Server HTTP/1.1 on 8080 WEB0713: Stopping Sun-Java-System/Application-Server HTTP/1.1 on 8181 WEB0713: Stopping Sun-Java-System/Application-Server HTTP/1.1 on 4848 CORE5051: Shutting down all J2EE applications ... EJB5122:EJB Timer Service shutdown at [2007/10/01 12:52:28] CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ... MQJMSRA_RA1101: SJSMQ JMSRA stopping... MQJMSRA_RA1101: SJSMQ JMSRA stopped. RAR7094: jmsra shutdown successful. RAR7094: __xa shutdown successful. CORE 5061 : Resource adapters Stop() Complete CORE5052: Application shutdown complete. Leaving GMS group c1 with shutdown type set to InstanceShutdown [AutoDeploy] Disabling AutoDeployment service. JBIFW0042: JBI framework termination complete. *** was able to start the domain using asadmin. "Refresh" in Services/servers/domain1-cluster shows the start status.
was able to stop the instance with "Stop" item in Services, and to start the instance with "Start" item.
Nitya... please try to reproduce this. I have not been able to do it.
Unable to reproduce. I was able to successfully start the server from IDE and Services/Servers does indicate a server running as expected. Server's log file is the same as one attached by Nouar
Lowering to P3 and marking as future so we can keep an eye on it. Nouar seems to have been getting the pop up window cause by the timeout w.r.t server starting
Retested this behavior and cannot reproduce. Closing. Please reopen if you see this issue again.