|
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@xxxxxxxxxx] httpd.conf : Listen 7001 #SiteMinder Configs Begin -
by ssoteam - 0729 JkMount /sso/* sso1 workers.properties : workers.java_home=/usr/java worker.list=iat1,sso1,custdash1 ## SSO CONNECTOR server.xml : <Server
port="7184" shutdown="SHUTDOWN"> <!-- Define a
non-SSL HTTP/1.1 Connector on port 8080 --> ==================================================== My request is not even
reaching uptil my tomcat server. It stucks on apache webserver itself. From:
Jeff Beard [mailto:jeffb@xxxxxxxxxxxxx] 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@xxxxxxxxxx] 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: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:49:17 2007]
[29047:38592] [debug] wc_get_worker_for_name::jk_worker.c (114): found a worker
ecatalog1 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) 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 |
|