tomcat woes
2 Message(s) by 2 Author(s) originally posted in java misc
| From: Marc Lambrichs |
Date: Wednesday, March 09, 2005
|
We're having problems with our tomcat virtualhost setup. See the log
below. We can not explain the "can not resolve localhost:8009" error. If you
have a clue, please let us know.
Cheers,
Marc[Wed Mar 09 13:54:39 2005] [notice] Apache/2.0.52 (FreeBSD)
mod_jk2/2.0.2 configured -- resuming normal operations
[Wed Mar 09 13:54:39 2005] [info] Server built: Feb 8 2005 11:14:08
[Wed Mar 09 13:54:39 2005] [debug] prefork.c(955): AcceptMutex: flock
(default: flock)
[Wed Mar 09 13:54:39 2005] [notice] jk2_init() Found
child 39367 in
scoreboard slot 0
[Wed Mar 09 13:54:39 2005] [notice] jk2_init() Found child 39368 in
scoreboard slot 6
[Wed Mar 09 13:54:39 2005] [notice] jk2_init() Found child 39369 in
scoreboard slot 7
[Wed Mar 09 13:54:39 2005] [notice] jk2_init() Found child 39370 in
scoreboard slot 8
[Wed Mar 09 13:54:39 2005] [notice] jk2_init() Found child 39371 in
scoreboard slot 9
[Wed Mar 09 13:54:39 2005] [error] jk2_
channel _
socket _init: can not
resolve localhost:8009 errno=22
[Wed Mar 09 13:54:39 2005] [error] workerEnv.initChannel() init failed
for channel.socket:localhost:8009
[Wed Mar 09 13:54:39 2005] [error] ajp13.init(): No channel localhost:8009
[Wed Mar 09 13:54:39 2005] [error] workerEnv.initWorkers() init failed
for ajp13:localhost:8009
[Wed Mar 09 13:54:39 2005] [debug] ../../common/jk_uriMap.c(377):
uriMap.init() Fixing Host *
[Wed Mar 09 13:54:39 2005] [debug] ../../common/jk_uriMap.c(464):
uriMap: fix uri (null)
context (null)
host *
[Wed Mar 09 13:54:39 2005] [debug] ../../common/jk_uriMap.c(464):
uriMap: fix uri /jkstatus/* context (null) host *
[Wed Mar 09 13:54:39 2005] [debug] ../../common/jk_uriMap.c(464):
uriMap: fix uri /servlets-examples/* context /servlets-examples host *
| From: Dan Nuttle |
Date: Friday, March 11, 2005
|
8009 is the default
port for CoyoteConnector, which (I think) is what Tomcat
uses to create socket connections. I'm not sure if I'm not already telling
you what you know, or how useful this is. Look in
%CATALINA_HOME%/conf/
server .xml, and search for 8009.
Port problems almost always involve firewalls, but I presume this is the
Tomcat log you're showing? So the
machine should not have any trouble
referring to its own port...I think. But firewalls are funny things.
We're having problems with our tomcat virtualhost setup. See the log
below. We can not explain the "can not resolve localhost:8009" error. If you
have a clue, please let us know.
Cheers,
Marc
[Wed Mar 09 13:54:39 2005] [notice] Apache/2.0.52 (FreeBSD)
mod_jk2/2.0.2 configured -- resuming normal operations
[Wed Mar 09 13:54:39 2005] [info] Server built: Feb 8 2005 11:14:08
[Wed Mar 09 13:54:39 2005] [debug] prefork.c(955): AcceptMutex: flock
(default: flock)
[Wed Mar 09 13:54:39 2005] [notice] jk2_init() Found child 39367 in
scoreboard slot 0
[Wed Mar 09 13:54:39 2005] [notice] jk2_init() Found child 39368 in
scoreboard slot 6
[Wed Mar 09 13:54:39 2005] [notice] jk2_init() Found child 39369 in
scoreboard slot 7
[Wed Mar 09 13:54:39 2005] [notice] jk2_init() Found child 39370 in
scoreboard slot 8
[Wed Mar 09 13:54:39 2005] [notice] jk2_init() Found child 39371 in
scoreboard slot 9
[Wed Mar 09 13:54:39 2005] [error] jk2_channel_socket_init: can not
resolve localhost:8009 errno=22
[Wed Mar 09 13:54:39 2005] [error] workerEnv.initChannel() init failed
for channel.socket:localhost:8009
[Wed Mar 09 13:54:39 2005] [error] ajp13.init(): No channel localhost:8009
[Wed Mar 09 13:54:39 2005] [error] workerEnv.initWorkers() init failed
for ajp13:localhost:8009
[Wed Mar 09 13:54:39 2005] [debug] ../../common/jk_uriMap.c(377):
uriMap.init() Fixing Host *
[Wed Mar 09 13:54:39 2005] [debug] ../../common/jk_uriMap.c(464):
uriMap: fix uri (null) context (null) host *
[Wed Mar 09 13:54:39 2005] [debug] ../../common/jk_uriMap.c(464):
uriMap: fix uri /jkstatus/* context (null) host *
[Wed Mar 09 13:54:39 2005] [debug] ../../common/jk_uriMap.c(464):
> uriMap: fix uri /servlets-examples/* context /servlets-examples host *
Next Message: Netbeans does not recognise compiler options ?
Blogs related to tomcat woes
lightning strikes not once but twice
a double dose of brazilian
java... also: projects and communities:
... own awt toolkit and jfilechooser windows
woes weblogs: interruptable rmi calls,
java.net
... today: gosling on ajax hassles and database connection pooling with
tomcat.
Hosting Woes Over
For a while, I had this blog hosted at Kattare to see how their
Java/JSP (
Tomcat) ... So I decided to move to A Small Orange to check out one of their virtual (VPS) ... A dedicated (albeit virtual) machine for $70.00 a month is a really
...
Hosting Woes Over
For a while, I had this blog hosted at Kattare to see how their
Java/JSP (
Tomcat) hosting services stacked up. While my blog was hosted there, I ran into a bug in the awesome Ultimate Tag Warrior 3 WordPress plugin where the plugin
...
3.45 am..Yaaawn
... 'nullPointerException' by
java...and the salt in wounds part is that
JAVA ... Tomcat has been giving me sleepless nights. DB2 gave me sleepless nights,
... To add to all these
woes, i have to implement this whole thing in Linux.
...
Hibernate操作数据库时Broken Pipe错误的分析
Handling Oracle Broken Pipe Errors in JBoss and
Tomcat ... Oracle as its database encounters this issue from time to time: nested exception is
java.sql.
... However, if you too are experiencing some Oracle
woes, try the solutions above.
Hibernate操作数据库时Broken Pipe错误的分析
Handling Oracle Broken Pipe Errors in JBoss and
Tomcat ... Oracle as its database encounters this issue from time to time: nested exception is
java.sql.
... However, if you too are experiencing some Oracle
woes, try the solutions above.