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 65533 - Bind Exception When Starting Tomcat
Summary: Bind Exception When Starting Tomcat
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Sherold Dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-30 15:24 UTC by William Leonard
Modified: 2005-10-06 17:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Image of Tomcat Web Server v3.2 running in my browser (38.51 KB, image/png)
2005-09-30 15:25 UTC, William Leonard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description William Leonard 2005-09-30 15:24:10 UTC
I am not able to start the bundled Tomcat Server. I get the following bind
exception:

Using CATALINA_BASE:   C:\Documents and Settings\Brian
Leonard\.netbeans\5.0beta\jakarta-tomcat-5.5.7_base
Using CATALINA_HOME:   C:\Program
Files\netbeans-5.0beta\enterprise2\jakarta-tomcat-5.5.7
Using CATALINA_TMPDIR: C:\Documents and Settings\Brian
Leonard\.netbeans\5.0beta\jakarta-tomcat-5.5.7_base\temp
Using JAVA_HOME:       C:\jdk1.5.0_04
Sep 30, 2005 10:14:21 AM org.apache.coyote.http11.Http11Protocol init
SEVERE: Error initializing endpoint
java.net.BindException: Address already in use: JVM_Bind:8084
        at
org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:297)
        at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:142)
        at org.apache.catalina.connector.Connector.initialize(Connector.java:918)
        at
org.apache.catalina.core.StandardService.initialize(StandardService.java:580)
        at
org.apache.catalina.core.StandardServer.initialize(StandardServer.java:764)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:490)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:509)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:243)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:408)
Sep 30, 2005 10:14:21 AM org.apache.catalina.startup.Catalina load
SEVERE: Catalina.start
LifecycleException:  Protocol handler initialization failed:
java.net.BindException: Address already in use: JVM_Bind:8084
        at org.apache.catalina.connector.Connector.initialize(Connector.java:920)
        at
org.apache.catalina.core.StandardService.initialize(StandardService.java:580)
        at
org.apache.catalina.core.StandardServer.initialize(StandardServer.java:764)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:490)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:509)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:243)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:408)
Sep 30, 2005 10:14:21 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 671 ms
Sep 30, 2005 10:14:21 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Sep 30, 2005 10:14:21 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.7
Sep 30, 2005 10:14:21 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Sep 30, 2005 10:14:22 AM org.apache.coyote.http11.Http11Protocol start
SEVERE: Error starting endpoint
java.net.BindException: Address already in use: JVM_Bind:8084
        at
org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:297)
        at
org.apache.tomcat.util.net.PoolTcpEndpoint.startEndpoint(PoolTcpEndpoint.java:312)
        at org.apache.coyote.http11.Http11Protocol.start(Http11Protocol.java:181)
        at org.apache.catalina.connector.Connector.start(Connector.java:990)
        at org.apache.catalina.core.StandardService.start(StandardService.java:459)
        at org.apache.catalina.core.StandardServer.start(StandardServer.java:683)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:537)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)
Sep 30, 2005 10:14:22 AM org.apache.catalina.startup.Catalina start
SEVERE: Catalina.start: 
LifecycleException:  Protocol handler start failed: java.net.BindException:
Address already in use: JVM_Bind:8084
        at org.apache.catalina.connector.Connector.start(Connector.java:992)
        at org.apache.catalina.core.StandardService.start(StandardService.java:459)
        at org.apache.catalina.core.StandardServer.start(StandardServer.java:683)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:537)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)
Sep 30, 2005 10:14:22 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 962 ms

Notice is thinks the server has started. As a matter of fact, I can browse to
http://localhost:8084. However, that page implies Tomcat Web Server v3.2 is
running and it just gives me a single directory listing "localhost 8080/". See
that attached image.

I know this is something particular to my machine, but I can't figure out what
it is. I had two other versions of Tomcat installed which I've since removed.
Tomcat in NetBeans 4.1 starts up w/out any problems. I've also searched the
registry for Tomcat and found nothing. I've you'd like to VNC into my machine,
I'd be happy to set that up.

At the moment, this is prohibiting me from using NetBeans 5 to do any sort of
web development.

Regards,
Brian
Comment 1 William Leonard 2005-09-30 15:25:00 UTC
Created attachment 25371 [details]
Image of Tomcat Web Server v3.2 running in my browser
Comment 2 Sherold Dev 2005-10-03 10:23:47 UTC
Actually, this is not a NetBeans issue. Your Tomcat 3.2 installation occupies
ports the Bundled Tomcat is configured to use.

*** This issue has been marked as a duplicate of 59288 ***
Comment 3 William Leonard 2005-10-03 17:22:20 UTC
Stepan,

The issue is that I do not have Tomcat 3.2 installed (as far as I can tell).
Before I try to start Tomcat in NetBeans 5, if I browse to http://localhost:8084
I get: "The connection was refused when attempting to connect to
localhost:8084". It's not until I try to start Tomcat 5.7 that I get the bind
exception and I can browse to localhost:8084 where I see the page attached.
Also, Tomcat 5.7 starts fine for me in NetBeans 4.1. Some something certainly
changed in 5.0. I'd be happy to run a VNC session for you if you'd like. Just
let me know.

Regards,
Brian
Comment 4 Sherold Dev 2005-10-06 17:40:41 UTC
-> INVALID

Think I got it;) Tomcat 3.2 is the NetBeans internal HTTP server, which is used
e.g. by the HTTP Monitor. All you've got to do to resolve your problem is to
change the port number of either Tomcat or internal HTTP server via Server
Manager or "Window | Runtime | HTTP Server | Properties" respectively.