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 188747 - The glassfish v3 server cannot start reporting the port is preoccupied
Summary: The glassfish v3 server cannot start reporting the port is preoccupied
Status: RESOLVED INCOMPLETE
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-18 05:32 UTC by daspranab
Modified: 2011-11-16 16:42 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description daspranab 2010-07-18 05:32:06 UTC 
I can start the same domain directly by asadmin start-domain command and do everything which I should be able to do from within glassfish v3.

I have checked all ports: there is no 8080 port running.

With the new problem with netbeans 6.9 can be resolved quickly.

I find from other forums that this has been reported but stands unresolved for a long time.

Even if the problem cannot be replicated on test environment, one can backtrack the logic leading to this error and find if any discrepancy there.  The original developers of Netbeans should be able to fix it in a flash.
Comment 1 Jiri Kovalsky 2010-07-20 09:02:51 UTC 
Guys, can you please investigate this? Thanks!
Comment 2 Vince Kraemer 2010-07-20 14:27:34 UTC 
Please describe your environment a bit more completely...

Where is GF installed?

Where is NetBeans installed?

How did you install GlassFish?

How did you install NetBeans?

Do you have references to the other forums that I might get additional info from?

Note: GlassFish Server uses about 8 different ports, so checking 8080 is not a complete check.
Comment 3 Vince Kraemer 2010-07-20 17:36:13 UTC 
Well, I just tried 6.9 with 3.0.1 onto Windows 7 Pro.

That worked fine.

I do not have access to a machine with XP.

I need to get additional info from the filer to diagnose the issue that they are running into.

I haven't been able to find evidence that this is a wide spread problem... lowering to p3.
Comment 4 Vince Kraemer 2011-01-03 17:12:43 UTC 
after a few months of waiting for info, I guess I should close this as incomplete.

Please feel free to reopen when you have addition actionable info about how to reproduce the problem.