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 133257 - NetBeans IDE hangs on startup if incorrect Glassfish password is given
Summary: NetBeans IDE hangs on startup if incorrect Glassfish password is given
Status: RESOLVED WORKSFORME
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-04-19 13:30 UTC by dgradwell
Modified: 2008-07-23 07:41 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dgradwell 2008-04-19 13:30:24 UTC
NetBeans IDE 6.0.1 hangs on startup when Glassfish is installed. "Opening Main Window" appears in the bottom left of the
NetBeans IDE Main Window.


This is repeatable in that it has happened several times.  The current main project is "hello-jaxws" as distributed with
Glassfish.  It is particularly likely if an incorrect Glassfish administrator password is given or Glassfish is starting up.

Once the problem has occurred, Netbeans IDE can nly be terminated using Task Manager and will not restart correctly
until the machine is restarted.  (Hangs at the same point).

Happy to do further specific testing if required.  Screenshots can be provided by email.

Regards

David Gradwell
Comment 1 Vince Kraemer 2008-04-20 17:19:41 UTC
OK.

I have tried to replicate this issue with 6.1 rc1 on win vista with jdk 6 update 3... but haven't been able to...

So, I guess I need to get a thread dump from you... attached to this issue.

Read through this wiki entry for details on getting a thread dump: http://wiki.netbeans.org/GenerateThreadDump
Comment 2 Vince Kraemer 2008-07-23 07:41:13 UTC
no extra info from filer...  cannot really move forward from this point... closing

Filer: please reopen this issue with additional information if you still encounter this problem.