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.
[ BUILD # : 200601052030 ] [ JDK VERSION : 1.5.0_05 ] I have registered the server Sun Java System Application Server as a remote server with host localhost, port 4848. The server registration looks fine but it doesn't work: No subnodes are displayed when I expand the server node in the Runtime tab. When I choose View Server Log, a message box tells me that "/logs/server.log" doesn't exist. Technically correct but I'd prefer to see the log. Since I can't be 100% sure that there is nothing wrong with my server registration, I set the plugin logging level to FINE but still no error message is shown and nothing is written to the NetBeans log.
reassigning to appserver module for evaluation
Is there any reason to register local appserver as remote? If you register it as Local Domain, everything works well, so this is not P2.
> Is there any reason to register local appserver as remote? Yes there is; Since the app server I wanted to register is run as a service I don't want the Start/Stop/Restart actions to be enabled since they don't work anyway. I have tried both localhost and the "real" host name for my machine with the same result. I wrongly assumed that I that if a remote registration doesn't work on server running on my host it wouldn't work with another host. I have just tested on an almost really remote machine (XP running in VMware but that is about as remote as I can get on a single physical box) and since this works I agree that P3 is sufficient. I have rephrased the summary accordingly.
What happen if instead of localhost, you use the fully qualified machine name or the ip address?
This happens even if fully qualified machine name or ip address is used. It appears that the plugin in this case always returns a empty target list and hence the runtime tree is not created. Check for isLocal() in SunDeploymentManager and all it's usages should be updated to handle scenario wherein a local server is registered as a remote instance.
this looks like it is related to another bug that I am working on...
the fix for 72693 appears to have addressed this issue, too. http://serverplugins.netbeans.org/source/browse/serverplugins/sun/appsrv81/src/org/netbeans/modules/j2ee/sun/ide/dm/SunDeploymentManager.java?r1=1.10.4.5.2.6&r2=1.10.4.5.2.7