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.
I have Glassfish 3 installed locally and on a remote server. The remote server has a domain named "Integration". When I go through the "Add Server..." process (right click on Servers under the Services tab), I am able to "Register the Remote Domain". Once registered, NetBeans makes an incorrect choice for the web-app port. The remote domain is running with a portbase of 8300. This means its admin port is 8348 and its web-app ports are 8380 and 8381. When I register the remote domain I do specify that 8348 as the admin port while filling in the form. Once the remote domain is registered, I right-click on the new server under the servers node under the Services tab and select Properties. It shows Location as <proper server name>:8080. 8080 is incorrect and I can not edit it. Also, NetBeans thinks the domain is not running. When I right click on the server and select "View Admin Console" I get an error stating "The server must be running...". It is running. I am able to get to the remote servers admin console via the web browser. In short, two problems: 1. the port number for the HTTP web app access for a remote registered domain come up incorrect. In my case 8080 instead of 8380. 2. netbeans thinks the domain is not running when it is - I can not deploy to it, nor can I bring up the admin console.
I can replicate this behavior with the trunk build, too. I have the IDE running on a Solaris box. The server is running on a Windows box. The network has a proxy... that appears to be flakey... some connections complete, some do not, some requests timeout, others do not... Do you have a proxy in your environment? I was able to work-around the problem locally by adding my Windows 7 machine to the no-proxy host list. Working on finding a way to provide a user message... but not too often when this type of configuration error occurs.
*** Bug 197109 has been marked as a duplicate of this bug. ***
filer indicated 'no proxy' by direct email
Integrated into 'main-golden', will be available in build *201104020400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/9f1bffe5b12f User: Vince Kraemer <vkraemer@netbeans.org> Log: #197199 : State of remote domains not getting detected correctly. This change is more diagnostic than correctional.
These changes addressed the issue that I saw... which may be different than what you are seeing. Please try it out in the DEV build and mark this as VERIFIED or REOPENED. If you reopen the issue, please include any additional data from the IDE's log and the server log.
Tried it in RC2 and got the same issue.
yes. the change is not in the RC2 build. at this point, any fix must be vetted in the dev build and reviewed, BEFORE it is included in the RC build... setting the TM to Dev. marking as Fixed. Please test against the DEV build (like the one linked in the message from quality) and REOPEN if the change did not address the issue or mark as VERIFIED if the changes address the problem.
I tested using build *201104020400*. As soon as I started the IDE it asked for an update of J2EE Directory Module (or something like this). I accepted the update. Then tried to reproduce the problem without any success. Changing the status to VERIFIED. Thanks