Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Apache: Users

mod_jk error

 

 

Apache users RSS feed   Index | Next | Previous | View Threaded


Nehal.Sangoi at gexpro

Aug 8, 2007, 7:20 AM

Post #1 of 5 (1040 views)
Permalink
mod_jk error

Hi

I am running apache 2.0.59 on linux machine with the mod_jk 1.2.19
binary as connector to tomcat 5.5.23.
For one of the workers in mod_jk, its giving me following error.

[Tue Aug 07 20:41:03 2007] [22993:22208] [debug] jk_handler::mod_jk.c
(2047): Service finished with status=404 for worker=tss1

I tried to search the fressh mod_jk binary for the given apache version,
but it seems, its not available anymore. Hence, I tried to build from
the source code, but that option also did not work.

What could be the possible reason for the error mentioned and how it can
be resolved?


Thanks
Nehal


Nehal.Sangoi at gexpro

Aug 9, 2007, 2:21 PM

Post #2 of 5 (969 views)
Permalink
RE: mod_jk error [In reply to]

In continuation to below error, I have few more lines of log.

[Thu Aug 09 20:09:27 2007] [28566:38592] [debug]
wc_get_worker_for_name::jk_worker.c (114): found a worker iat1
[Thu Aug 09 20:09:27 2007] [28566:38592] [debug]
wc_get_name_for_type::jk_worker.c (290): Found worker type 'ajp13'
[Thu Aug 09 20:09:27 2007] [28566:38592] [debug]
init_ws_service::mod_jk.c (607): Service protocol=HTTP/1.1 method=GET
host=(null) addr=10.33.84.4 name=gexprdweb.gexo.com port=7001
auth=(null) user=(null) laddr=10.33.4.151 raddr=10.33.84.4


==============================

[Thu Aug 09 20:10:50 2007] [28567:38592] [debug]
map_uri_to_worker::jk_uri_worker_map.c (616): Found a wildchar match
'/custdash/*=custdash1'
[Thu Aug 09 20:10:50 2007] [28567:38592] [debug] jk_handler::mod_jk.c
(2111): Into handler jakarta-servlet worker=custdash1 r->proxyreq=0
[Thu Aug 09 20:10:50 2007] [28567:38592] [debug]
wc_get_worker_for_name::jk_worker.c (114): found a worker custdash1
[Thu Aug 09 20:10:50 2007] [28567:38592] [debug]
wc_get_name_for_type::jk_worker.c (290): Found worker type 'ajp13'
[Thu Aug 09 20:10:50 2007] [28567:38592] [debug]
init_ws_service::mod_jk.c (607): Service protocol=HTTP/1.1 method=GET
host=(null) addr=10.33.84.4 name=gexprdweb.gexo.com port=80 auth=(null)
user=(null) laddr=10.33.4.151 raddr=10.33.84.4

==============================

[Thu Aug 09 20:49:17 2007] [29047:38592] [debug]
wc_get_worker_for_name::jk_worker.c (114): found a worker ecatalog1
[Thu Aug 09 20:49:17 2007] [29047:38592] [debug]
wc_get_name_for_type::jk_worker.c (290): Found worker type 'ajp13'
[Thu Aug 09 20:49:17 2007] [29047:38592] [debug]
init_ws_service::mod_jk.c (607): Service protocol=HTTP/1.1 method=GET
host=(null) addr=10.33.84.4 name=gexprdweb.gexo.com port=8
0 auth=(null) user=(null) laddr=10.33.4.151 raddr=10.33.84.4


In the above bold lines, my URL port is getting changed from 7001 to 80
mysteriously. My instance is running over 7001 and application too, is
pointing to 7001 in all of the configuration. What could be the reason
for getting it redirected to port 80?

Thanks
Nehal

________________________________

From: Sangoi, Nehal (Gexpro, consultant)
Sent: Wednesday, August 08, 2007 10:20 AM
To: users [at] httpd
Subject: [users [at] http] mod_jk error


Hi

I am running apache 2.0.59 on linux machine with the mod_jk 1.2.19
binary as connector to tomcat 5.5.23.
For one of the workers in mod_jk, its giving me following error.

[Tue Aug 07 20:41:03 2007] [22993:22208] [debug] jk_handler::mod_jk.c
(2047): Service finished with status=404 for worker=tss1

I tried to search the fressh mod_jk binary for the given apache version,
but it seems, its not available anymore. Hence, I tried to build from
the source code, but that option also did not work.

What could be the possible reason for the error mentioned and how it can
be resolved?


Thanks
Nehal


jeffb at cyberxape

Aug 9, 2007, 4:51 PM

Post #3 of 5 (971 views)
Permalink
RE: mod_jk error [In reply to]

Can you post the relevant configuration from workers.properties, apache
config and the server.xml please?





Thanks,



Jeff



From: Sangoi, Nehal (Gexpro, consultant) [mailto:Nehal.Sangoi [at] gexpro]
Sent: Thursday, August 09, 2007 3:22 PM
To: users [at] httpd
Subject: RE: [users [at] http] mod_jk error



In continuation to below error, I have few more lines of log.



[Thu Aug 09 20:09:27 2007] [28566:38592] [debug]
wc_get_worker_for_name::jk_worker.c (114): found a worker iat1
[Thu Aug 09 20:09:27 2007] [28566:38592] [debug]
wc_get_name_for_type::jk_worker.c (290): Found worker type 'ajp13'
[Thu Aug 09 20:09:27 2007] [28566:38592] [debug] init_ws_service::mod_jk.c
(607): Service protocol=HTTP/1.1 method=GET host=(null) addr=10.33.84.4
name=gexprdweb.gexo.com port=7001 auth=(null) user=(null) laddr=10.33.4.151
raddr=10.33.84.4




==============================



[Thu Aug 09 20:10:50 2007] [28567:38592] [debug]
map_uri_to_worker::jk_uri_worker_map.c (616): Found a wildchar match
'/custdash/*=custdash1'
[Thu Aug 09 20:10:50 2007] [28567:38592] [debug] jk_handler::mod_jk.c
(2111): Into handler jakarta-servlet worker=custdash1 r->proxyreq=0
[Thu Aug 09 20:10:50 2007] [28567:38592] [debug]
wc_get_worker_for_name::jk_worker.c (114): found a worker custdash1
[Thu Aug 09 20:10:50 2007] [28567:38592] [debug]
wc_get_name_for_type::jk_worker.c (290): Found worker type 'ajp13'
[Thu Aug 09 20:10:50 2007] [28567:38592] [debug] init_ws_service::mod_jk.c
(607): Service protocol=HTTP/1.1 method=GET host=(null) addr=10.33.84.4
name=gexprdweb.gexo.com port=80 auth=(null) user=(null) laddr=10.33.4.151
raddr=10.33.84.4



==============================



[Thu Aug 09 20:49:17 2007] [29047:38592] [debug]
wc_get_worker_for_name::jk_worker.c (114): found a worker ecatalog1
[Thu Aug 09 20:49:17 2007] [29047:38592] [debug]
wc_get_name_for_type::jk_worker.c (290): Found worker type 'ajp13'
[Thu Aug 09 20:49:17 2007] [29047:38592] [debug] init_ws_service::mod_jk.c
(607): Service protocol=HTTP/1.1 method=GET host=(null) addr=10.33.84.4
name=gexprdweb.gexo.com port=8
0 auth=(null) user=(null) laddr=10.33.4.151 raddr=10.33.84.4





In the above bold lines, my URL port is getting changed from 7001 to 80
mysteriously. My instance is running over 7001 and application too, is
pointing to 7001 in all of the configuration. What could be the reason for
getting it redirected to port 80?



Thanks

Nehal

_____

From: Sangoi, Nehal (Gexpro, consultant)
Sent: Wednesday, August 08, 2007 10:20 AM
To: users [at] httpd
Subject: [users [at] http] mod_jk error

Hi



I am running apache 2.0.59 on linux machine with the mod_jk 1.2.19 binary as
connector to tomcat 5.5.23.

For one of the workers in mod_jk, its giving me following error.



[Tue Aug 07 20:41:03 2007] [22993:22208] [debug] jk_handler::mod_jk.c
(2047): Service finished with status=404 for worker=tss1



I tried to search the fressh mod_jk binary for the given apache version, but
it seems, its not available anymore. Hence, I tried to build from the source
code, but that option also did not work.



What could be the possible reason for the error mentioned and how it can be
resolved?





Thanks

Nehal


Nehal.Sangoi at gexpro

Aug 9, 2007, 5:08 PM

Post #4 of 5 (978 views)
Permalink
RE: mod_jk error [In reply to]

httpd.conf :

Listen 7001
# Load Mod_JK Module for Tomcat Connector
LoadModule jk_module modules/mod_jk.so
#SiteMinder Configs Begin - by ssoteam - 0729
LoadModule sm_module
/data01/netegrity/siteminder5qmr7/webagent/lib/libmod_sm20.so
SmInitFile /data01/expd/conf/WebAgent.conf
#SiteMinder Configs End

#
# Where to find workers.properties
JkWorkersFile /data01/expd/conf/workers.properties
# Where to put jk logs
JkLogFile /data01/expd/logs/mod_jk.log
# Set the jk log level [debug/error/info]
JkLogLevel debug
JkMount /sso/* sso1
JkMount /iat/* iat1
JkMount /custdash/* custdash1


workers.properties :

workers.java_home=/usr/java
ps=/
worker.list=iat1,sso1,custdash1
## SSO CONNECTOR
worker.sso1.port=7103
worker.sso1.host=10.33.9.71
worker.sso1.type=ajp13
## IAT CONNECTOR
worker.iat1.port=7123
worker.iat1.host=10.33.9.71
worker.iat1.type=ajp13
## CUSTDASH CONNECTOR
worker.custdash1.port=7183
worker.custdash1.host=10.33.9.71
worker.custdash1.type=ajp13


server.xml :

<Server port="7184" shutdown="SHUTDOWN">
<!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
<Connector port="7181" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25"
maxSpareThreads="75"
enableLookups="false" redirectPort="8443"
acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />
<!-- Note : To disable connection timeouts, set connectionTimeout
value
to 0 -->

<!-- Note : To use gzip compression you could set the following
properties :

compression="on"
compressionMinSize="2048"
noCompressionUserAgents="gozilla, traviata"
compressableMimeType="text/html,text/xml"
-->

<!-- Define a SSL HTTP/1.1 Connector on port 8443 -->
<!--
<Connector port="7182" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25"
maxSpareThreads="75"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS" />
-->

<!-- Define an AJP 1.3 Connector on port 8009 -->
<Connector port="7183"
enableLookups="false" redirectPort="8443"
protocol="AJP/1.3" />


====================================================

My request is not even reaching uptil my tomcat server. It stucks on
apache webserver itself.

________________________________

From: Jeff Beard [mailto:jeffb [at] cyberxape]
Sent: Thursday, August 09, 2007 7:52 PM
To: users [at] httpd
Subject: RE: [users [at] http] mod_jk error



Can you post the relevant configuration from workers.properties, apache
config and the server.xml please?





Thanks,



Jeff



From: Sangoi, Nehal (Gexpro, consultant)
[mailto:Nehal.Sangoi [at] gexpro]
Sent: Thursday, August 09, 2007 3:22 PM
To: users [at] httpd
Subject: RE: [users [at] http] mod_jk error



In continuation to below error, I have few more lines of log.



[Thu Aug 09 20:09:27 2007] [28566:38592] [debug]
wc_get_worker_for_name::jk_worker.c (114): found a worker iat1
[Thu Aug 09 20:09:27 2007] [28566:38592] [debug]
wc_get_name_for_type::jk_worker.c (290): Found worker type 'ajp13'
[Thu Aug 09 20:09:27 2007] [28566:38592] [debug]
init_ws_service::mod_jk.c (607): Service protocol=HTTP/1.1 method=GET
host=(null) addr=10.33.84.4 name=gexprdweb.gexo.com port=7001
auth=(null) user=(null) laddr=10.33.4.151 raddr=10.33.84.4




==============================



[Thu Aug 09 20:10:50 2007] [28567:38592] [debug]
map_uri_to_worker::jk_uri_worker_map.c (616): Found a wildchar match
'/custdash/*=custdash1'
[Thu Aug 09 20:10:50 2007] [28567:38592] [debug] jk_handler::mod_jk.c
(2111): Into handler jakarta-servlet worker=custdash1 r->proxyreq=0
[Thu Aug 09 20:10:50 2007] [28567:38592] [debug]
wc_get_worker_for_name::jk_worker.c (114): found a worker custdash1
[Thu Aug 09 20:10:50 2007] [28567:38592] [debug]
wc_get_name_for_type::jk_worker.c (290): Found worker type 'ajp13'
[Thu Aug 09 20:10:50 2007] [28567:38592] [debug]
init_ws_service::mod_jk.c (607): Service protocol=HTTP/1.1 method=GET
host=(null) addr=10.33.84.4 name=gexprdweb.gexo.com port=80 auth=(null)
user=(null) laddr=10.33.4.151 raddr=10.33.84.4



==============================



[Thu Aug 09 20:49:17 2007] [29047:38592] [debug]
wc_get_worker_for_name::jk_worker.c (114): found a worker ecatalog1
[Thu Aug 09 20:49:17 2007] [29047:38592] [debug]
wc_get_name_for_type::jk_worker.c (290): Found worker type 'ajp13'
[Thu Aug 09 20:49:17 2007] [29047:38592] [debug]
init_ws_service::mod_jk.c (607): Service protocol=HTTP/1.1 method=GET
host=(null) addr=10.33.84.4 name=gexprdweb.gexo.com port=8
0 auth=(null) user=(null) laddr=10.33.4.151 raddr=10.33.84.4





In the above bold lines, my URL port is getting changed from 7001 to 80
mysteriously. My instance is running over 7001 and application too, is
pointing to 7001 in all of the configuration. What could be the reason
for getting it redirected to port 80?



Thanks

Nehal

________________________________

From: Sangoi, Nehal (Gexpro, consultant)
Sent: Wednesday, August 08, 2007 10:20 AM
To: users [at] httpd
Subject: [users [at] http] mod_jk error

Hi



I am running apache 2.0.59 on linux machine with the mod_jk 1.2.19
binary as connector to tomcat 5.5.23.

For one of the workers in mod_jk, its giving me following error.



[Tue Aug 07 20:41:03 2007] [22993:22208] [debug] jk_handler::mod_jk.c
(2047): Service finished with status=404 for worker=tss1



I tried to search the fressh mod_jk binary for the given apache version,
but it seems, its not available anymore. Hence, I tried to build from
the source code, but that option also did not work.



What could be the possible reason for the error mentioned and how it can
be resolved?





Thanks

Nehal


jeffb at cyberxape

Aug 9, 2007, 8:34 PM

Post #5 of 5 (971 views)
Permalink
RE: mod_jk error [In reply to]

First, I noticed that the host in your log entry, gexprdweb.gexo.com, is not
the same domain name as the gexpro.com in your email address. I don't know
what the story is there but I suppose there could be a typo.



Next, I don't know much, if anything, about Siteminder's Apache module and
how it might influence the request cycle. But it looks like the SSO team
added a module into the Apache configuration on 7/29. That's recent enough I
have to ask if you have commented out the Siteminder directives and tested
it?



Also, have you tested directly against the Tomcat instance without going
through Apache? There's a 404 error in the first log message that might have
come from Tomcat. I think you get a different error when the request doesn't
make it through to Tomcat.



The worker in the first log entry doesn't exist in the conf you posted or in
the other log entries. Other than that, everything else seems fairly
"normal" to me.



HTH.



--Jeff



From: Sangoi, Nehal (Gexpro, consultant) [mailto:Nehal.Sangoi [at] gexpro]
Sent: Thursday, August 09, 2007 6:08 PM
To: users [at] httpd
Subject: RE: [users [at] http] mod_jk error



httpd.conf :



Listen 7001
# Load Mod_JK Module for Tomcat Connector
LoadModule jk_module modules/mod_jk.so

#SiteMinder Configs Begin - by ssoteam - 0729
LoadModule sm_module
/data01/netegrity/siteminder5qmr7/webagent/lib/libmod_sm20.so
SmInitFile /data01/expd/conf/WebAgent.conf
#SiteMinder Configs End

#
# Where to find workers.properties
JkWorkersFile /data01/expd/conf/workers.properties
# Where to put jk logs
JkLogFile /data01/expd/logs/mod_jk.log
# Set the jk log level [debug/error/info]
JkLogLevel debug

JkMount /sso/* sso1
JkMount /iat/* iat1
JkMount /custdash/* custdash1





workers.properties :



workers.java_home=/usr/java
ps=/

worker.list=iat1,sso1,custdash1

## SSO CONNECTOR
worker.sso1.port=7103
worker.sso1.host=10.33.9.71
worker.sso1.type=ajp13
## IAT CONNECTOR
worker.iat1.port=7123
worker.iat1.host=10.33.9.71
worker.iat1.type=ajp13
## CUSTDASH CONNECTOR
worker.custdash1.port=7183
worker.custdash1.host=10.33.9.71
worker.custdash1.type=ajp13





server.xml :



<Server port="7184" shutdown="SHUTDOWN">

<!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
<Connector port="7181" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />
<!-- Note : To disable connection timeouts, set connectionTimeout value
to 0 -->

<!-- Note : To use gzip compression you could set the following
properties :

compression="on"
compressionMinSize="2048"
noCompressionUserAgents="gozilla, traviata"
compressableMimeType="text/html,text/xml"
-->

<!-- Define a SSL HTTP/1.1 Connector on port 8443 -->
<!--
<Connector port="7182" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS" />
-->

<!-- Define an AJP 1.3 Connector on port 8009 -->
<Connector port="7183"
enableLookups="false" redirectPort="8443" protocol="AJP/1.3"
/>




====================================================



My request is not even reaching uptil my tomcat server. It stucks on apache
webserver itself.



_____

From: Jeff Beard [mailto:jeffb [at] cyberxape]
Sent: Thursday, August 09, 2007 7:52 PM
To: users [at] httpd
Subject: RE: [users [at] http] mod_jk error

Can you post the relevant configuration from workers.properties, apache
config and the server.xml please?





Thanks,



Jeff



From: Sangoi, Nehal (Gexpro, consultant) [mailto:Nehal.Sangoi [at] gexpro]
Sent: Thursday, August 09, 2007 3:22 PM
To: users [at] httpd
Subject: RE: [users [at] http] mod_jk error



In continuation to below error, I have few more lines of log.



[Thu Aug 09 20:09:27 2007] [28566:38592] [debug]
wc_get_worker_for_name::jk_worker.c (114): found a worker iat1
[Thu Aug 09 20:09:27 2007] [28566:38592] [debug]
wc_get_name_for_type::jk_worker.c (290): Found worker type 'ajp13'
[Thu Aug 09 20:09:27 2007] [28566:38592] [debug] init_ws_service::mod_jk.c
(607): Service protocol=HTTP/1.1 method=GET host=(null) addr=10.33.84.4
name=gexprdweb.gexo.com port=7001 auth=(null) user=(null) laddr=10.33.4.151
raddr=10.33.84.4




==============================



[Thu Aug 09 20:10:50 2007] [28567:38592] [debug]
map_uri_to_worker::jk_uri_worker_map.c (616): Found a wildchar match
'/custdash/*=custdash1'
[Thu Aug 09 20:10:50 2007] [28567:38592] [debug] jk_handler::mod_jk.c
(2111): Into handler jakarta-servlet worker=custdash1 r->proxyreq=0
[Thu Aug 09 20:10:50 2007] [28567:38592] [debug]
wc_get_worker_for_name::jk_worker.c (114): found a worker custdash1
[Thu Aug 09 20:10:50 2007] [28567:38592] [debug]
wc_get_name_for_type::jk_worker.c (290): Found worker type 'ajp13'
[Thu Aug 09 20:10:50 2007] [28567:38592] [debug] init_ws_service::mod_jk.c
(607): Service protocol=HTTP/1.1 method=GET host=(null) addr=10.33.84.4
name=gexprdweb.gexo.com port=80 auth=(null) user=(null) laddr=10.33.4.151
raddr=10.33.84.4



==============================



[Thu Aug 09 20:49:17 2007] [29047:38592] [debug]
wc_get_worker_for_name::jk_worker.c (114): found a worker ecatalog1
[Thu Aug 09 20:49:17 2007] [29047:38592] [debug]
wc_get_name_for_type::jk_worker.c (290): Found worker type 'ajp13'
[Thu Aug 09 20:49:17 2007] [29047:38592] [debug] init_ws_service::mod_jk.c
(607): Service protocol=HTTP/1.1 method=GET host=(null) addr=10.33.84.4
name=gexprdweb.gexo.com port=8
0 auth=(null) user=(null) laddr=10.33.4.151 raddr=10.33.84.4





In the above bold lines, my URL port is getting changed from 7001 to 80
mysteriously. My instance is running over 7001 and application too, is
pointing to 7001 in all of the configuration. What could be the reason for
getting it redirected to port 80?



Thanks

Nehal

_____

From: Sangoi, Nehal (Gexpro, consultant)
Sent: Wednesday, August 08, 2007 10:20 AM
To: users [at] httpd
Subject: [users [at] http] mod_jk error

Hi



I am running apache 2.0.59 on linux machine with the mod_jk 1.2.19 binary as
connector to tomcat 5.5.23.

For one of the workers in mod_jk, its giving me following error.



[Tue Aug 07 20:41:03 2007] [22993:22208] [debug] jk_handler::mod_jk.c
(2047): Service finished with status=404 for worker=tss1



I tried to search the fressh mod_jk binary for the given apache version, but
it seems, its not available anymore. Hence, I tried to build from the source
code, but that option also did not work.



What could be the possible reason for the error mentioned and how it can be
resolved?





Thanks

Nehal

Apache users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.