tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Januski, Ken" <kjanu...@phillynews.com>
Subject RE: Connectors for IIS/Tomcat SHOULD make sense
Date Tue, 24 Jun 2003 17:10:33 GMT
Another day's experimentation and no more progress. One thing I notice is
that the source code seems to refer to isapi_redirector2 and I'm using
isapi_redirector.dll. I'm using that because I'm following instructions from
ESRI for preparing IIS and Tomcat for an ArcIMS upgrade. Their instructions
indicate that isapi_redirector.dll should work with Tomcat 4.1.12 and I, at
least so far, have no reason to doubt them.

I've also edited my worker.properties files to a minimum just for testing.
I'm including it below. But I'm still puzzled as to why I'm getting the 404
error. The log indicates that an ajp13 worker is being created successfully
and I don't really see any errors related to it, other than the 404.

[Tue Jun 24 12:47:34 2003]  [jk_worker.c (132)]: Into wc_get_worker_for_name
ajp13
[Tue Jun 24 12:47:34 2003]  [jk_worker.c (136)]: wc_get_worker_for_name,
done  found a worker
[Tue Jun 24 12:47:34 2003]  [jk_isapi_plugin.c (860)]: HttpExtensionProc got
a worker for name ajp13
[Tue Jun 24 12:47:34 2003]  [jk_ajp_common.c (1352)]: Into
jk_worker_t::get_endpoint
[Tue Jun 24 12:47:34 2003]  [jk_ajp_common.c (1075)]: Into
jk_endpoint_t::service
[Tue Jun 24 12:47:34 2003]  [jk_ajp_common.c (280)]: Into
ajp_marshal_into_msgb
[Tue Jun 24 12:47:34 2003]  [jk_ajp_common.c (413)]: ajp_marshal_into_msgb -
Done
[Tue Jun 24 12:47:34 2003]  [jk_connect.c (116)]: Into jk_open_socket
[Tue Jun 24 12:47:34 2003]  [jk_connect.c (123)]: jk_open_socket, try to
connect socket = 2600
[Tue Jun 24 12:47:34 2003]  [jk_connect.c (132)]: jk_open_socket, after
connect ret = 0
[Tue Jun 24 12:47:34 2003]  [jk_connect.c (140)]: jk_open_socket, set
TCP_NODELAY to on
[Tue Jun 24 12:47:34 2003]  [jk_connect.c (148)]: jk_open_socket, return, sd
= 2600
[Tue Jun 24 12:47:34 2003]  [jk_ajp_common.c (588)]: In
jk_endpoint_t::ajp_connect_to_endpoint, connected sd = 2600
[Tue Jun 24 12:47:34 2003]  [jk_ajp_common.c (612)]: sending to ajp13 #294
[Tue Jun 24 12:47:34 2003]  [jk_ajp_common.c (853)]: ajp_send_request 2:
request body to send 0 - request body to resend 0
[Tue Jun 24 12:47:34 2003]  [jk_ajp_common.c (698)]: received from ajp13 #81
[Tue Jun 24 12:47:34 2003]  [jk_ajp_common.c (461)]: ajp_unmarshal_response:
status = 404
[Tue Jun 24 12:47:34 2003]  [jk_ajp_common.c (466)]: ajp_unmarshal_response:
Number of headers is = 2
[Tue Jun 24 12:47:34 2003]  [jk_ajp_common.c (506)]: ajp_unmarshal_response:
Header[0] [Content-Type] = [text/html;charset=ISO-8859-1]
[Tue Jun 24 12:47:34 2003]  [jk_ajp_common.c (506)]: ajp_unmarshal_response:
Header[1] [Content-Language] = [en-US]
[Tue Jun 24 12:47:34 2003]  [jk_isapi_plugin.c (428)]: Into
jk_ws_service_t::start_response
[Tue Jun 24 12:47:34 2003]  [jk_ajp_common.c (698)]: received from ajp13
#756
[Tue Jun 24 12:47:34 2003]  [jk_isapi_plugin.c (562)]: Into
jk_ws_service_t::write
[Tue Jun 24 12:47:34 2003]  [jk_ajp_common.c (698)]: received from ajp13 #2
[Tue Jun 24 12:47:34 2003]  [jk_isapi_plugin.c (872)]: HttpExtensionProc
service() returned OK
[Tue Jun 24 12:47:34 2003]  [jk_ajp_common.c (1307)]: Into
jk_endpoint_t::done

I had assumed that it was the mapping to isapi_redirector.dll, that I noted
in the first message, that was the problem. But I don't really know. That's
why I'm looking for some guidance on what the log should be showing. In an
old log for a connection that worked there was not attempt to map
isapi_redirector.dll so I assume that part of the problem is there. I just
can't figure out what would cause Tomcat to try to map the dll.

This is the worker.properties. The only thing unusual is that I've changed
localhost to the name of the server: inqtomcat. I've also changed it back to
localhost and it's not made any difference.

Thanks for any more ideas.

Ken



# 
worker.ajp13.type=ajp13 
# 
#Specifies the load balance factor when used with a load balancing worker. 
#Note: 
#-----> lbfactor must be > 0 
#-----> Low lbfactor means less work done by the worker. 
# 
worker.ajp13.lbfactor=1 
# 
#Specify the size of the open connection cache. 
#worker.ajp13.cachesize 
# 
#------DEFAULT LOAD BALANCER WORKER DEFINITION----------- 
# 
#The loadbalancer (type lb) worker perform weighted round-robin 
#load balancing with sticky sessions. 
#Note: 
#---> If a worker dies, the load balancer will check its state once 
#in a while. Until then all work is redirected to peer worker. 
# 
worker.loadbalancer.type=lb 
worker.loadbalancer.balanced_workers=ajp13 
# 
#worker.tomcat_home should point to the location where you installed 
#tomcat. This is where you have your conf, webapps and lib directories. 
#Note: Please make sure to enter the appropriate path from your machine. 
# 
worker.tomcat_home=C:\Tomcat4112
# 
#worker.java_home should point to your Java installation. 
#Normally you should have a bin and lib directories beneath it. 
#Note: Please make sure to enter the appropriate path from your machine. 
# 
worker.java_home=C:\java\jdk1.4 
# 
#You should configure your environment slash...ps=\on NT and / on UNIX 
#and may be different elsewhere. 
# 
ps=# 
#-------ADVANCED MODE------- 
#------------------------------ 
# 
# 
#-------DEFAULT worker list------ 
#---------------------------------- 
# 
#The worker that your plugins should create and work with 
# 
worker.list=ajp13 
# 
#----DEFAULT ajp13 WORKER DEFINITION----- 
# 
#Defining a worker named ajp13 and of type ajp13 
#Note that the name and the type do not have to match. 
# 
worker.ajp13.port=8009 
worker.ajp13.host=inqtomcat
#*****End worker.properties*****



-----Original Message-----
From: Jason Bainbridge [mailto:jason@jblinux.org]
Sent: Monday, June 23, 2003 1:31 PM
To: Tomcat Users List
Subject: Re: Connectors for IIS/Tomcat SHOULD make sense


What entries have you got in your workers2.properties? Sounds like something

is wrong with your setup... I'm assuming you have seen this howto? 

http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/installhowto.html

As for making sense of the process, gotta love open source:

http://tinyurl.com/f1lo

Nothing beats reading the source itself. :)

Regards,
-- 
Jason Bainbridge
http://jblinux.org

On Tue, 24 Jun 2003 01:19, Januski, Ken wrote:
> but I've yet found any sensible explanation of hooking up IIS and Tomcat.
I
> have found step by step instructions but not any explanations. What's more
> embarrassing is that I posted a similar IIS/Tomcat problem 3-4 months ago,
> finally solved it, and now I've upgraded Tomcat and have it again.
>
> Though there are a number of howtos on getting IIS and Tomcat working
> together I'm still looking for some help in making sense of the actual
> process, in other words I ought to be able to look at the redirector logs
> and figure out what the problem is, or at least where to start looking.
The
> redirector logs seem to be full of useful information and yet I see
> numerous people posting messages here asking for help with them. So I
guess
> what I'm asking is if there is any resource that can help explain the
logs.
> I'd really like to just read them and diagnose the problem based on that.
> Can anyone point me to such a resource?
>
> I believe that my current problem is that Tomcat is trying to map the
> redirector when it should be doing something else. So I'm getting log
> entries that say:
>
> [jk_isapi_plugin.c (759)-- 
Jason Bainbridge
http://jblinux.org]: In HttpFilterProc Virtual Host redirection of
> /inqtomcat/jakarta/isapi_redirector.dll
> [jk_uri_worker_map.c (460)]: Into jk_uri_worker_map_t::map_uri_to_worker
> [jk_uri_worker_map.c (477)]: Attempting to map URI
> '/inqtomcat/jakarta/isapi_redirector.dll'
> [jk_uri_worker_map.c (599)]: jk_uri_worker_map_t::map_uri_to_worker, done
> without a match
> [jk_isapi_plugin.c (765)]: In HttpFilterProc test Default redirection of
> /jakarta/isapi_redirector.dll
> [jk_uri_worker_map.c (460)]: Into jk_uri_worker_map_t::map_uri_to_worker
> [jk_uri_worker_map.c (477)]: Attempting to map URI
> '/jakarta/isapi_redirector.dll'
> [jk_uri_worker_map.c (599)]: jk_uri_worker_map_t::map_uri_to_worker, done
> without a match
>
> I'm pretty sure that Tomcat shouldn't be trying to map the dll though
> that's just a guess. That's why I believe that if I could find some
> explanation of the whole process I could figure out the answer on my own,
> and perhaps others could as well, rather than sending so many message here
> regarding it.
>
> By the way I have looked at archives and seen a number of entries that
come
> close to solving the above problem. But none of them work for me and they
> don't really explain what is going on, or if they do I'm just missing it.
> As I said I think if I could figure out what is going on in the connector
> process that I could figure it out for myself.
>
> Thanks for any help.
>
> Ken


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message