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.

Bug 197109 - Cannot connect to remote glassfish
Summary: Cannot connect to remote glassfish
Status: RESOLVED DUPLICATE of bug 197199
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: PC Windows 7 x64
: P3 normal (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-26 10:12 UTC by kororos
Modified: 2011-04-01 00:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Screenshots of all steps and errors (1.05 MB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2011-03-26 10:12 UTC, kororos
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kororos 2011-03-26 10:12:04 UTC
Created attachment 107293 [details]
Screenshots of all steps and errors

I am trying to register the remote glassfish v3 server in 6.9.1 in order to deploy a web service (on local instance this works fine). 

I did the following:

1. Select Server - Glassfish v3
2. Set Server Installation
3. Register Remote domain - Set ip address. Port is 4848

No password is requested (although it should). 

In the servers tab, I can see the new server, but when I click on the "plus" sign, the sign disappears and nothing happens. 

When I try to deploy my app to the remote server I get the following error:

"compile-jsps:
C:\Users\eleftherios.kororos\Documents\NetBeansProjects\Jello\Jello-war\nbproject\build-impl.xml:693: Deployment error:
Starting of server GlassFish Server 3 - Remote is not supported. Please, start the server manually.
See the server log for details."

Note, that on the remote server, I forward 4848 TCP and UDP. Firewall was disabled for the test. Normally the traffic TCP and UDP on port 4848 is allowed. 

Finally, accessing the admin console from the browser works fine. 

All screenshots are attached.
Comment 1 Vince Kraemer 2011-03-28 17:21:29 UTC
Need a couple clarifications...

(In reply to comment #0)
> Created an attachment (id=107293) [details]
> Screenshots of all steps and errors
> 
> I am trying to register the remote glassfish v3 server in 6.9.1 in order to
> deploy a web service (on local instance this works fine). 
> 
> I did the following:
> 
> 1. Select Server - Glassfish v3
> 2. Set Server Installation
> 3. Register Remote domain - Set ip address. Port is 4848
> 
> No password is requested (although it should). 

Does the remote server have a password configured for the admin user?

> 
> In the servers tab, I can see the new server, but when I click on the "plus"
> sign, the sign disappears and nothing happens. 
> 
> When I try to deploy my app to the remote server I get the following error:
> 
> "compile-jsps:
> C:\Users\eleftherios.kororos\Documents\NetBeansProjects\Jello\Jello-war\nbproject\build-impl.xml:693:
> Deployment error:
> Starting of server GlassFish Server 3 - Remote is not supported. Please, start
> the server manually.
> See the server log for details."
> 
> Note, that on the remote server, I forward 4848 TCP and UDP. Firewall was
> disabled for the test. Normally the traffic TCP and UDP on port 4848 is
> allowed. 

And there are no proxies that come into play???

> 
> Finally, accessing the admin console from the browser works fine. 
> 
> All screenshots are attached.
Comment 2 kororos 2011-03-29 20:59:14 UTC
Hello, 

* admin password has been setup on the remote server and is different from the default (i.e. different from adminadmin)

* there are no proxies that come into play

However, after a bit more investigation, I realized that the server is Glassfish 3.1 and I understand that Netbeans 6.9.1 does not support 3.1

Having said that, I had similar problems with 7.0Beta2 (which I posted through the IDE). 

Thank you
Comment 3 Vince Kraemer 2011-04-01 00:40:46 UTC
this reads very similar to to issue 197199.

please read through that issue and provide any additional info there.

If you think this is substantially different, reopen the issue with some info on 'why'...

*** This bug has been marked as a duplicate of bug 197199 ***