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 142905 - NB claims Tomcat default port is in use
Summary: NB claims Tomcat default port is in use
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 6.x
Hardware: All Windows Vista
: P3 blocker (vote)
Assignee: issues@serverplugins
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2008-08-05 12:16 UTC by novakm
Modified: 2008-11-11 09:15 UTC (History)
1 user (show)

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 novakm 2008-08-05 12:16:41 UTC
When I try to start Tomcat from NetBeans I receive only error message reading "Starting of Tomcat failed, the server
port 8084 is already in use". It worked before and I didn't changed any settings. I restarted my OS and used netstat -
nothing on port 8084. I checked programs connected to network with Windows Defender and again - nothing. I started NB
and tried to start the Tomcat - same problem, it claimed the port is in use. After that I saw that Java listens on port
8084 via Windows Defender (wasn't listening before).
  The only thing I recall is that I tried to stop Tomcat from NB and the progress bar labeled "stopping ..." was there
for several minutes. I closed whole netbeans and confirmed it even though the task didn't finished. Maybe it stopped
working after that, but I am not sure.

  Only P3 because I don't know how to reproduce it and using fresh userdir helped. Otherwise I would mark it with higher
priority as it makes Tomcat from NetBeans unusable.

-----
Product Version: NetBeans IDE 6.1 (Build 200805300101)
Java: 1.6.0_07; Java HotSpot(TM) Client VM 10.0-b23
System: Windows Vista version 6.0 running on x86; Cp1250; cs_CZ (nb)  (SP1)
Comment 1 Petr Hejl 2008-09-23 10:33:54 UTC
Jardo can you reproduce this?

Thanks.
Comment 2 Jaroslav Pospisil 2008-09-23 10:43:57 UTC
I don't remember seeing anything like this recently.Tomcat can't start if another server is running on the same
port,like NB Glassfish v2,for example.There could have been some hanged up server in the memory.If it occurs next
time,check please Windows Task Manager to detect running java processes,just to be sure.Anyway, I think keyword RANDOM
is appropriate for this issue.I'll try to do some testing on Tomcat with my Vista and see if there'll be any success in
reproducing the issue.
Comment 3 Jaroslav Pospisil 2008-11-11 09:15:37 UTC
No feedback from reporter,so closing as worksforme.