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 152105 - IDE does not recognize GlassFish has started
Summary: IDE does not recognize GlassFish has started
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: PC Windows Vista
: P3 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-01 20:35 UTC by dgradwell
Modified: 2009-09-22 10:17 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Screen shots, description, logs (384.50 KB, text/plain)
2008-11-01 20:36 UTC, dgradwell
Details
Documents further tests but does not take us forward (52.00 KB, text/plain)
2008-11-02 21:12 UTC, dgradwell
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dgradwell 2008-11-01 20:35:27 UTC
I'm using IDE 6.5RC2 and GlassFish V2 both from the bundle downloaded 1st November 2008.

When I start GlassFish from within IDE it starts OK and the log in the IDE sub-window shows an OK start up.

However, an alert window then pops up a few seconds later indicating that the startup failed.  Right clicking on the
Glassfish icon in servers shows only the start service drop down.

A file is attached with more detailed screen shots and log window extracts.  The file shows the problem with Windows UAC
& Firewall on (first) and off (second) but the key problem is the same.  There are some interesting differences noted
but these are not material to the main issue of IDE not reconizing that GlassFish has started successfully.
Comment 1 dgradwell 2008-11-01 20:36:40 UTC
Created attachment 73054 [details]
Screen shots, description, logs
Comment 2 Peter Pis 2008-11-01 22:39:34 UTC
Reassigning.
Comment 3 _ pcw 2008-11-02 01:01:35 UTC
V2 issue, looks like it's related to autoregistration.
Comment 4 Vince Kraemer 2008-11-02 07:21:29 UTC
Part of this sounds similar to issue 150602...  Some other folks have reported similar issues... and most of them
resolve to issues related to firewalls and anti-virus software...  There is a fair number of hints of things to look for
in that issue...

Some questions: 

If you use the 'Refresh' item from the right-click menu of the server node, does the situation correct itself?

Do you have any anti-virus software running on this system?

What output do you see on your system if you follow the procedure outlined in
http://www.netbeans.org/issues/show_bug.cgi?id=150602#desc4... See
http://www.netbeans.org/issues/show_bug.cgi?id=150602#desc8 for an example.

Some other things to check...

content of hosts file... Are you connected or disconnected from the network.... are you running Vista inside something
like VMWare or some other 'virtualization' environment...

The problem that you had with the sudden use of new ports comes from the fact that Vista is very picky about who can
write into the c:\Program Files\ directory tree (and when they can do that)... When NB starts for the first time, it
tries to detect if the user can write into c:\Program Files\glassfish-v2ur2\domains\domain1\logs.  If the user can write
into that directory, then domain1 is registered.  If it cannot, then the IDE creates a domain that is owned by the user
and is writable...  The ports for this domain are chosen "randomly" to try to prevent port conflicts.  This what caused
the ports to be different from the ports that you expected when you first started...

You got a second server in the IDE because you stopped the IDE, turned off User Account Control and restarted the IDE...

The IDE noticed that you did not have C:\Program Files\glassfish-v2ur2\domains\domain1 registered, so it registered
it... because it could this time.
Comment 5 dgradwell 2008-11-02 21:12:04 UTC
Created attachment 73089 [details]
Documents further tests but does not take us forward
Comment 6 Vince Kraemer 2008-11-03 06:02:31 UTC
from e-mail...

1.	Going “Refresh” on the GlassFish Server icon shows a little busy icon for about 10 seconds but no change.

2.	I'm running McAfee Total Protection for Small Business version 4.7.0.538 but with only the anti-virus enabled. 
(Their firewall broke Postgres and their support line were unhelpful (that's being polite) !)

3.	If I follow through the steps mentioned in http://www.netbeans.org/issues/show_bug.cgi?id=150602#desc4 I get
Exception in thread "main" java.net.SocketTimeoutException: Read timed out just like Carol did and a similar
non-exceptional tracert to localhost and 127.0.0.1.

4.	Hosts file has nothing special in it.

127.0.0.1       localhost
::1             localhost
127.0.0.1       djlg.lan
1.2.3.4	    localhost

5.	I'm running Vista Ultimate on raw metal - no VMWare here !

6.	Understood what UAC did !  I've turned it off again !!

I'm wondering whether to disable McAfee.

Also, if I go to the early build of GlassFish v3 is that likely to help this problem ?

Comment 7 Vince Kraemer 2008-11-03 06:33:42 UTC
in response to http://www.netbeans.org/issues/show_bug.cgi?id=152105#desc7

1. Darn...

2. OK.  I would try disabling the antivirus stuff (at least while you test the start-up)

3. HMMM.  That looks suspect to me...  So, your server is running on the port but you get a read time-out...  That is
interesting....

4. I have to disagree about the host file... it seems like it has some very unusual data in it...

The first two lines are the IPv4 and IPv6 loopback addresses (I think) and they should be mapped to localhost.

I guess it is okay to say '127.0.0.1 <something other than localhost>'... but I don't see that very often...

The mapping of '1.2.3.4 localhost' seems mighty suspect... What does it mean? Why is that in your host file?

5. OK.

6. at this point, I don't think UAC has anything to do with the 'undetected start' problem.

Switching to GF v3 might help resolve this... but v3 Prelude is a web-only server...

I am stumped.... I have Vista business on a machine in my office... I have not run into this problem... and have been
trying to replicate it for some time...  Most of the folks that have reported situations similar to yours have had
nextwork config and antivirus issues.  That makes it very hard to reproduce and resolve, since the level of details
necessary to narrow down the root cause is huge...
Comment 8 Michal Mocnak 2009-09-22 10:17:33 UTC
Without requested information for long time - INVALID. We can't do anything in this case. Reporter, please add requested information and reopen issue. 
Thanks in advance.