Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Tomcat failed to initialize

 
Eko Harmawan
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm downloaded tomcat 6.0.18, i extracted it to my disk, and try to start it with startup.bat through my command prompt. It can't be started, and printed exception that telling me the port 8080 is being used. I download the instalation service from tomcat homepage, and running it to install it(to the same directory),but this time with port 8081. Still it not working and telling the same exception. This is the exception

19 Mei 09 21:13:15 org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.6.0\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\Java\jdk1.6.0\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\ASUS Security Center\ASUS Security Protect Manager\bin
19 Mei 09 21:13:15 org.apache.coyote.http11.Http11Protocol init
SEVERE: Error initializing endpoint
java.net.BindException: Address already in use: JVM_Bind<null>:8080
at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:502)
at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:176)
at org.apache.catalina.connector.Connector.initialize(Connector.java:1058)
at org.apache.catalina.core.StandardService.initialize(StandardService.java:677)
at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:795)
at org.apache.catalina.startup.Catalina.load(Catalina.java:530)
at org.apache.catalina.startup.Catalina.load(Catalina.java:550)
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:597)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:260)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:412)
...(continued)

Please tell me why and how to solve this problem. Thankyou.
 
Ulf Dittmer
Rancher
Posts: 42968
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This is the important part:
java.net.BindException: Address already in use: JVM_Bind<null>:8080

It means that there's a process running already that listens on port 8080. You either need to stop that process (most likely some other web server), or configure Tomcat to use some other port.

Update: Just noticed that you tried switching to port 8081, but apparently that didn't work. Where did you change that? That setting is in the file $TOMCAT_HOME/conf/server.xml.
 
Eko Harmawan
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm using service installation. Ok, I'll try to change it. Thanks Ulf. I'm totally newbie with JSP and this Tomcat.
 
Eko Harmawan
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Oww...That's complicated file...which value that i should change to 8081???
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13064
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I strongly recommend that you do not start your experiments with Tomcat by running it as a service. A running service causes all sorts of complications, in fact it may be the running service at 8080 which is preventing starting a new Tomcat instance.

Delete the service entirely and install Tomcat as a regular application, you will be stopping and restarting it frequently as your experiments progress.

Bill
 
Eko Harmawan
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks everyone, finally i manage to run the Tomcat. , but there's something bothering me, the command line saying there's some Tomcat action can't be done because the port is used. Despite the action can't be executed, the tomcat running succesfully. Here is the message, please tell me what the action that can't be done. and how to fix it.

20 Mei 09 10:38:34 org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performanc
e in production environments was not found on the java.library.path: C:\Program
Files\Java\jdk1.6.0\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows
;C:\Program Files\Java\jdk1.6.0\bin;C:\Windows\system32;C:\Windows;C:\Windows\Sy
stem32\Wbem;C:\Program Files\ASUS Security Center\ASUS Security Protect Manager\
bin
20 Mei 09 10:38:34 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8081
20 Mei 09 10:38:34 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 369 ms
20 Mei 09 10:38:34 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
20 Mei 09 10:38:34 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.18
20 Mei 09 10:38:35 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8081
20 Mei 09 10:38:35 org.apache.jk.common.ChannelSocket init
INFO: Port busy 8009 java.net.BindException: Address already in use: JVM_Bind

20 Mei 09 10:38:35 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8010
20 Mei 09 10:38:35 org.apache.jk.server.JkMain start
INFO: Jk running ID=1 time=1/23 config=null
20 Mei 09 10:38:35 org.apache.catalina.startup.Catalina start
INFO: Server startup in 595 ms
 
Amit Ghorpade
Bartender
Posts: 2854
10
Fedora Firefox Browser Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The default port for AJP 1.3 is busy, you can check who is using it using netstat.
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13064
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator


This says that the package found 8009 busy so it will use 8010 - the message is type INFO, not fatal, so tomcat continues to run.

Bill
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic