Re: Tomcat ISAPI Redirector for IIS

2010-08-25 Thread andoridyou2010
check the fitler vs extension here is one post http://androidyou.blogspot.com/2010/08/could-not-get-worker-for-name-ajp13.html doepain wrote: No matter what I try where I go I just keep hitting a wall with this ISAPI redirector for IIS/Tomcat. I have been trying to get this to work since

Re: Tomcat ISAPI Redirector for IIS

2010-08-25 Thread andoridyou2010
http://androidyou.blogspot.com/2010/08/using-iis-7-75-tracing-features-to.html andoridyou2010 wrote: check the fitler vs extension here is one post http://androidyou.blogspot.com/2010/08/could-not-get-worker-for-name-ajp13.html doepain wrote: No matter what I try where I go I just

RE: Tomcat ISAPI Redirector for IIS

2008-02-18 Thread Tim Whittington
It looks like you've got more than one thing going on. The debug log refers to a worker named 'ajp13', which is the default name, and not the one you've got configured in your uriworkermap.properties/worker.properties - This usually points to your filter config and the ISAPI extension DLL (the

Re: Tomcat ISAPI Redirector for IIS

2008-02-18 Thread mgainty
: VWWCUFPEGAUTFJMVRESKPNKMBIPBARHDMNNSKVFVWRKJVZCMHVI To: 'Tomcat Users List' users@tomcat.apache.org Sent: Monday, February 18, 2008 3:28 PM Subject: RE: Tomcat ISAPI Redirector for IIS It looks like you've got more than one thing going on. The debug log refers to a worker named 'ajp13', which is the default

Re: Tomcat ISAPI Redirector for IIS

2008-02-18 Thread Rainer Jung
Start fixing it by *not* commenting out the worker.list=ajp13w and set your connection pool size to something reasonable (default is 1, start with let's say 50). Then follow Tim's adviceand please also tell us which isapi redirector version you are using. Regards, Rainer doepain schrieb: