We're having problems with our tomcat virtualhost setup. See the log
below. We can't explain the "can't 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't
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 *
Dan Nuttle - 12 Mar 2005 04:18 GMT
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 shouldn't 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't explain the "can't resolve localhost:8009" error. If you
[quoted text clipped - 33 lines]
> [Wed Mar 09 13:54:39 2005] [debug] ../../common/jk_uriMap.c(464):
> uriMap: fix uri /servlets-examples/* context /servlets-examples host *