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.
When using netBeans on my power user account on windows, the IDE cannot detect if Sun Java Application Server (8.1 PE 2005Q1) is started up. When the server start up is run in the IDE, it detects the server log just fine. The log itself even reports that startup was successful. It can however, detect it on the Administrator account, which is the account I was in when I installed everything. This implies that netBeans is relying on some user account specific information in order to detect if the server is running. Originally I couldn't even start up the server on my power user acount, I fixed that by giving my account full control to the C:\Sun\Appserver directory. This problem doesn't seem to be exclusive to the latest release of netBeans either, the same problem occurs in Sun Java Studio 8 Enterprise. I have the impression that this problem may have something to do with the appServer itself. It has it's own bugs. For example: When I type asadmin version, the server cannot report it's version. Note: If this is a caused by a bad domain.xml file, it sure would be nice to have netBeans work well enough with sjas to actually go and validate (maybe even auto-fix) my configuration.
Reassigning to j2eeserver, please evaluate. Thanks.
-> sunappserv
Did you install this netbeans or/and this App server instance as this power user? Which NetBeans version do you use? NetBeans is relying on JSR 88 (via a connextion via http or https to the running server) to see if a server is running or not. "giving my account full control to the C:\Sun\Appserver" (i.e change file permissions) is really a bad idea and would not fix security issues and resource access from this process (port numbers like 80 which cannot be used by ramdom users, etc). But the domain used by the IDE has to be fully accessible by the IDE user. You can try to create a new domain and register it to the ide to see if it can start.
It seems that the issue was perhaps caused by a bad domain.xml file after all. For some reason the server has a bad setting on it. This confused me because all netBeans was doing was reporting that an assertion error had been thrown, it wasn't identifying the source of that error. This makes me wonder if netBeans is using the appservers own verification class (com.sun.enterprise.config.serverbeans.validation.DomainXmlVerifier) an implementation of that class, or not even validating the domain.xml file. This bug report might be better off as a request for features. I'll leave it to you guys to decide, I'm still a newb here... Another thing, I found a problem with the appserver itself while playing around with the asadmin utility's verify-domain-xml command. I'll go report that to sun. When you create a new domain then run "asadmin verify-domain-xml" on your brand new domain, it throws an assertion error. Specifially: "SEVERE: /domain[1]/configs[1]: Assertion Failed: There is a config element named "default-config"" That's just not right. (Thanks for all your help so far guys, by deleting and then recreating my default domain and letting it use all the default settings, netBeans can now detect it from any user account.)
TM 5.0->TBD
this appears to be closed according to the filer's note from Nov. 30, 2005