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.
full ide #1602 from hudson, GF-v2 b54 (with addons from GlassFish update center - like Identity, OpenESB, SWDP, ... - should be reproducible also w/o these addons), jdk6u2, ubuntu -register GF in the IDE -start it -add -Dcom.sun.xml.ws.transport.http.HttpAdapter.dump=true and -Dcom.sun.xml.ws.transport.http.client.HttpTransportPipe.dump=true to GF instance JVM options -restart the server (using Restart action on the GF node in Services tab) => server is successfully stoped, but its start up fails I've tried this twice and -for the first time I got a generic message which is suggesting to check possible port conflicts etc -next time I got a message that Starting of server has timed out
I am on Mac OS X, jdk 1.5.0_07, with a recently updated NB 6.0 build and GF V2 B55. I created a pe domain and updated it completely. I followed your steps. And I was not able to reproduce the issue. Please attach the server log and reopen.
I'm on linux with JDK6u2 and I can still reproduce this with full build #1690 from Hudson and GF-v2-b55 (w/ CompApps, Identity addons from GF UC and REST stuff from https://jersey.dev.java.net/servlets/ProjectDocumentList?folderID=7653&expandFolder=7653&folderID=0), I have no clear steps for reproducing this now (=> random)... What I did today to get to this state was: -start the IDE, register GF in the IDE, start-stop-restart-stop the server -exit from the IDE, start GF updatetool and install CompApps and Identity addons -install jersey libs to the domain (to ...domains/domain1/lib) -start IDE -start-restart-stop-start-restart-stop the server -restart the IDE -create new web project with entity classes -create REST WS from entities -build project -correct compilation errors -clean & build project (5 times) -run project (server is started) -clean & build project (3 times) -invoke Test Rest... action on the project node -undeploy project from the server -clean project -clean & build project -deploy project -invoke Test Rest... action on the project node -restart server => server is stopped, but it's startup fails
Created attachment 45063 [details] server log
If you Refresh the node, does the resulting node state reflect the correct state of the instance/domain?
Yes, it does - if I refresh the server instance node it shows that the server is stopped. Message in the progress bar (in the right bottom corner of the IDE) is changed to "Starting server" (or sth like that), but the start itself never finish correctly.
ok.
Can't reproduce this anymore. It could be related to recent changes in network config in the office...
v.