Thanks John,

I'd just as soon avoid IIS but unfortunately it's something that my company
uses.:-)

I also think that there's enough people who have to/choose to use IIS that
it would be helpful to figure out what causes this problem. The last time I
solved it I'd been beating my head against the wall for so long that I
couldn't remember what I did when it finally did work. Not my preferred
method of problem-solving.....................:-)


Ken

-----Original Message-----
From: John Turner [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 24, 2003 2:40 PM
To: Tomcat Users List
Subject: Re: Connectors for IIS/Tomcat SHOULD make sense



I wish I could help, but I avoid IIS if possible.  The only thing I know to 
suggest is the configuration tutorial at onjava.com.

John

On Tue, 24 Jun 2003 14:27:40 -0400, Januski, Ken <[EMAIL PROTECTED]> 
wrote:

> Thanks John,
>
> I wasn't sure about the loadbalancing. I commented it out but I'm still
> getting the 404 errors, "/jakarta/isapi_redirector.dll is not available."
>
> I've watched other people have this error, including someone about a week
> ago I think, in which you gave some advice. But as far as I can tell the
> problem was never solved. It's surprising to me how fragile the 
> IIS/Tomcat
> connectors seem to be. Most of the documentation finally ends with "this
> should now work. If not please check for typos in worker.properties, 
> etc."
> Perhaps this really is the right advice and I'll eventually see a typo. 
> But
> right now it sure doesn't look like there are any to me and it's hard to
> know where to turn next, other than scouring the web for people who've 
> had
> similar problems.
>
> I guess what I find oddest is that the logs are full of information but 
> no
> one seems to know how to interpret them.... But then again I probably put
> more stock in logs than many people do.
>
> Ken
>
> -----Original Message-----
> From: John Turner [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 24, 2003 1:58 PM
> To: Tomcat Users List
> Subject: Re: Connectors for IIS/Tomcat SHOULD make sense
>
>
>
> There's no need for any of the loadbalancing stuff in workers.properties. 
> You only need the four lines: type, name, port, host.
>
> John
>
> On Tue, 24 Jun 2003 13:10:33 -0400, Januski, Ken 
> <[EMAIL PROTECTED]> wrote:
>
>> 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:[EMAIL PROTECTED]
>> 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,
>
>
>



-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to