RE: Connectors for IIS/Tomcat SHOULD make sense - THE END
Well I've admitted defeat and shot not the server but the connector. After 5 days experimenting with various versions of isapi_redirect and isapi_redirector I finally gave up on both and instead installed isapi_redirector2. It was working within 30 minutes. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 4:44 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense yes. sad to say i've already checked that a number of times. also the ps# has been corrected off and on as i've meddled with file. it seems to make no difference. i'm also determined to get it working and to document what i had to do to get it working. but i don't want to clutter up the list with it. unfortunately from what i've seen most of the threads with this problem just seem to fizzle out without resolution. it would be nice to see one get resolved, esp. since it's mine.:-) -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 4:37 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Have you tried giving 'Everyone' full permissions on the directory containing isapi_redirector.dll and on the file itself in the file system (not IIS)? I am determined to get this damn thing working. :) -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connectors for IIS/Tomcat SHOULD make sense - THE END
Sounds to me like you had JK2 configuration files but were using the JK connector, and as soon as you subbed in the connector that matched the files it worked. John On Thu, 26 Jun 2003 16:34:12 -0400, Januski, Ken [EMAIL PROTECTED] wrote: Well I've admitted defeat and shot not the server but the connector. After 5 days experimenting with various versions of isapi_redirect and isapi_redirector I finally gave up on both and instead installed isapi_redirector2. It was working within 30 minutes. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 4:44 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense yes. sad to say i've already checked that a number of times. also the ps# has been corrected off and on as i've meddled with file. it seems to make no difference. i'm also determined to get it working and to document what i had to do to get it working. but i don't want to clutter up the list with it. unfortunately from what i've seen most of the threads with this problem just seem to fizzle out without resolution. it would be nice to see one get resolved, esp. since it's mine.:-) -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 4:37 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Have you tried giving 'Everyone' full permissions on the directory containing isapi_redirector.dll and on the file itself in the file system (not IIS)? I am determined to get this damn thing working. :) -- 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]
RE: Connectors for IIS/Tomcat SHOULD make sense - THE END
It's possible. Someone suggested something similar way back when but never followed up with more detailed instructions on how to fix it if that was indeed the case. -Original Message- From: John Turner [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2003 4:46 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense - THE END Sounds to me like you had JK2 configuration files but were using the JK connector, and as soon as you subbed in the connector that matched the files it worked. John On Thu, 26 Jun 2003 16:34:12 -0400, Januski, Ken [EMAIL PROTECTED] wrote: Well I've admitted defeat and shot not the server but the connector. After 5 days experimenting with various versions of isapi_redirect and isapi_redirector I finally gave up on both and instead installed isapi_redirector2. It was working within 30 minutes. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 4:44 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense yes. sad to say i've already checked that a number of times. also the ps# has been corrected off and on as i've meddled with file. it seems to make no difference. i'm also determined to get it working and to document what i had to do to get it working. but i don't want to clutter up the list with it. unfortunately from what i've seen most of the threads with this problem just seem to fizzle out without resolution. it would be nice to see one get resolved, esp. since it's mine.:-) -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 4:37 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Have you tried giving 'Everyone' full permissions on the directory containing isapi_redirector.dll and on the file itself in the file system (not IIS)? I am determined to get this damn thing working. :) -- 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]
RE: Connectors for IIS/Tomcat SHOULD make sense
Some progress... I haven't spent much time looking at the IIS logs but rather at the isapi_redirect logs. But today I did and happened to notice that the old logs for Tomcat before I upgraded and things stopped working has this when it redirects to Tomcat: GET /jakarta/isapi_redirector.dll - 200 Java1.4.0_01 The new logs where it's failing show this instead: GET /jakarta/isapi_redirector.dll - 200 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) Both show 200 to indicate that they're forwarding successfully I think. But the successful one seems to link to Java and the unsuccessful to the browser. Once I get that figured out I'm hoping problem may be solved. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 6:09 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Thanks Jason, Yes I've edited the registry over and over, trying forward slashes, backslashed backwards slashes, etc. in path name all to know avail. I'm going to call it quits for today and hope that something will make more sense tomorrow. If not I guess I'll just start from scratch with a reinstallation. The fact the the redirect logs say that they've found so many rules and then found matches against those rules makes me think that there is no problem finding the uriworkermap.properties files, since that's where these are defined. But something sure is whacky with the loading of isapi_redirect(or). Maybe tomorrow it will all make more sense. Thanks much for all your efforts in trying to solve it. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 5:21 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 04:53, Januski, Ken wrote: I've honed uriworkermap.properties down to just this simple one below and have only tried accessing pages that it should find, like http://inqtomcat/examples/jsp/index.html I'm taking a guess here that it isn't finding your uriworkermap.properties file and it is trying to load everything including the DLL (which obviously should be loaded by IIS). Have you got all the registry keys setup correctly as per the following page? http://www.onjava.com/pub/a/onjava/2002/12/18/tomcat.html?page=2 Regards, -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connectors for IIS/Tomcat SHOULD make sense
you are trying to use JK2 configs with JK DLL. - Original Message - From: Januski, Ken To: Tomcat Users List Sent: Wednesday, June 25, 2003 8:23 PM Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Some progress... I haven't spent much time looking at the IIS logs but rather at the isapi_redirect logs. But today I did and happened to notice that the old logs for Tomcat before I upgraded and things stopped working has this when it redirects to Tomcat: GET /jakarta/isapi_redirector.dll - 200 Java1.4.0_01 The new logs where it's failing show this instead: GET /jakarta/isapi_redirector.dll - 200 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) Both show 200 to indicate that they're forwarding successfully I think. But the successful one seems to link to Java and the unsuccessful to the browser. Once I get that figured out I'm hoping problem may be solved. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 6:09 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Thanks Jason, Yes I've edited the registry over and over, trying forward slashes, backslashed backwards slashes, etc. in path name all to know avail. I'm going to call it quits for today and hope that something will make more sense tomorrow. If not I guess I'll just start from scratch with a reinstallation. The fact the the redirect logs say that they've found so many rules and then found matches against those rules makes me think that there is no problem finding the uriworkermap.properties files, since that's where these are defined. But something sure is whacky with the loading of isapi_redirect(or). Maybe tomorrow it will all make more sense. Thanks much for all your efforts in trying to solve it. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 5:21 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 04:53, Januski, Ken wrote: I've honed uriworkermap.properties down to just this simple one below and have only tried accessing pages that it should find, like http://inqtomcat/examples/jsp/index.html I'm taking a guess here that it isn't finding your uriworkermap.properties file and it is trying to load everything including the DLL (which obviously should be loaded by IIS). Have you got all the registry keys setup correctly as per the following page? http://www.onjava.com/pub/a/onjava/2002/12/18/tomcat.html?page=2 Regards, -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connectors for IIS/Tomcat SHOULD make sense
I don't believe I want JK2. Can you tell me how to set it to JK? -Original Message- From: Dominic Parry [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 2:32 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense you are trying to use JK2 configs with JK DLL. - Original Message - From: Januski, Ken To: Tomcat Users List Sent: Wednesday, June 25, 2003 8:23 PM Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Some progress... I haven't spent much time looking at the IIS logs but rather at the isapi_redirect logs. But today I did and happened to notice that the old logs for Tomcat before I upgraded and things stopped working has this when it redirects to Tomcat: GET /jakarta/isapi_redirector.dll - 200 Java1.4.0_01 The new logs where it's failing show this instead: GET /jakarta/isapi_redirector.dll - 200 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) Both show 200 to indicate that they're forwarding successfully I think. But the successful one seems to link to Java and the unsuccessful to the browser. Once I get that figured out I'm hoping problem may be solved. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 6:09 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Thanks Jason, Yes I've edited the registry over and over, trying forward slashes, backslashed backwards slashes, etc. in path name all to know avail. I'm going to call it quits for today and hope that something will make more sense tomorrow. If not I guess I'll just start from scratch with a reinstallation. The fact the the redirect logs say that they've found so many rules and then found matches against those rules makes me think that there is no problem finding the uriworkermap.properties files, since that's where these are defined. But something sure is whacky with the loading of isapi_redirect(or). Maybe tomorrow it will all make more sense. Thanks much for all your efforts in trying to solve it. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 5:21 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 04:53, Januski, Ken wrote: I've honed uriworkermap.properties down to just this simple one below and have only tried accessing pages that it should find, like http://inqtomcat/examples/jsp/index.html I'm taking a guess here that it isn't finding your uriworkermap.properties file and it is trying to load everything including the DLL (which obviously should be loaded by IIS). Have you got all the registry keys setup correctly as per the following page? http://www.onjava.com/pub/a/onjava/2002/12/18/tomcat.html?page=2 Regards, -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connectors for IIS/Tomcat SHOULD make sense
Just for a sanity check can you export your registry settings for the below key and send them to the list? HKEY_LOCAL_MACHINE SOFTWARE Apache Software Foundation Jakarta Isapi Redirector 1.0 Regards, Jason On Thu, 26 Jun 2003 02:23, Januski, Ken wrote: Some progress... I haven't spent much time looking at the IIS logs but rather at the isapi_redirect logs. But today I did and happened to notice that the old logs for Tomcat before I upgraded and things stopped working has this when it redirects to Tomcat: GET /jakarta/isapi_redirector.dll - 200 Java1.4.0_01 The new logs where it's failing show this instead: GET /jakarta/isapi_redirector.dll - 200 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) Both show 200 to indicate that they're forwarding successfully I think. But the successful one seems to link to Java and the unsuccessful to the browser. Once I get that figured out I'm hoping problem may be solved. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 6:09 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Thanks Jason, Yes I've edited the registry over and over, trying forward slashes, backslashed backwards slashes, etc. in path name all to know avail. I'm going to call it quits for today and hope that something will make more sense tomorrow. If not I guess I'll just start from scratch with a reinstallation. The fact the the redirect logs say that they've found so many rules and then found matches against those rules makes me think that there is no problem finding the uriworkermap.properties files, since that's where these are defined. But something sure is whacky with the loading of isapi_redirect(or). Maybe tomorrow it will all make more sense. Thanks much for all your efforts in trying to solve it. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 5:21 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 04:53, Januski, Ken wrote: I've honed uriworkermap.properties down to just this simple one below and have only tried accessing pages that it should find, like http://inqtomcat/examples/jsp/index.html I'm taking a guess here that it isn't finding your uriworkermap.properties file and it is trying to load everything including the DLL (which obviously should be loaded by IIS). Have you got all the registry keys setup correctly as per the following page? http://www.onjava.com/pub/a/onjava/2002/12/18/tomcat.html?page=2 Regards, -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connectors for IIS/Tomcat SHOULD make sense
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation] [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector] [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0] extension_uri=/jakarta/isapi_redirector.dll log_file=C:Tomcat4112logsisapi.log log_level=debug worker_file=C:/Tomcat4112/conf/workers.properties worker_mount_file=C:/Tomcat4112/conf/uriworkermap.properties @= -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 2:36 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Just for a sanity check can you export your registry settings for the below key and send them to the list? HKEY_LOCAL_MACHINE SOFTWARE Apache Software Foundation Jakarta Isapi Redirector 1.0 Regards, Jason On Thu, 26 Jun 2003 02:23, Januski, Ken wrote: Some progress... I haven't spent much time looking at the IIS logs but rather at the isapi_redirect logs. But today I did and happened to notice that the old logs for Tomcat before I upgraded and things stopped working has this when it redirects to Tomcat: GET /jakarta/isapi_redirector.dll - 200 Java1.4.0_01 The new logs where it's failing show this instead: GET /jakarta/isapi_redirector.dll - 200 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) Both show 200 to indicate that they're forwarding successfully I think. But the successful one seems to link to Java and the unsuccessful to the browser. Once I get that figured out I'm hoping problem may be solved. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 6:09 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Thanks Jason, Yes I've edited the registry over and over, trying forward slashes, backslashed backwards slashes, etc. in path name all to know avail. I'm going to call it quits for today and hope that something will make more sense tomorrow. If not I guess I'll just start from scratch with a reinstallation. The fact the the redirect logs say that they've found so many rules and then found matches against those rules makes me think that there is no problem finding the uriworkermap.properties files, since that's where these are defined. But something sure is whacky with the loading of isapi_redirect(or). Maybe tomorrow it will all make more sense. Thanks much for all your efforts in trying to solve it. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 5:21 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 04:53, Januski, Ken wrote: I've honed uriworkermap.properties down to just this simple one below and have only tried accessing pages that it should find, like http://inqtomcat/examples/jsp/index.html I'm taking a guess here that it isn't finding your uriworkermap.properties file and it is trying to load everything including the DLL (which obviously should be loaded by IIS). Have you got all the registry keys setup correctly as per the following page? http://www.onjava.com/pub/a/onjava/2002/12/18/tomcat.html?page=2 Regards, -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connectors for IIS/Tomcat SHOULD make sense
Next question... Does your jakarta virtual directory in IIS have execute access checked? Regards, -- Jason Bainbridge http://jblinux.org On Thu, 26 Jun 2003 02:41, Januski, Ken wrote: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation] [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector] [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0] extension_uri=/jakarta/isapi_redirector.dll log_file=C:Tomcat4112logsisapi.log log_level=debug worker_file=C:/Tomcat4112/conf/workers.properties worker_mount_file=C:/Tomcat4112/conf/uriworkermap.properties @= -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 2:36 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Just for a sanity check can you export your registry settings for the below key and send them to the list? HKEY_LOCAL_MACHINE SOFTWARE Apache Software Foundation Jakarta Isapi Redirector 1.0 Regards, Jason On Thu, 26 Jun 2003 02:23, Januski, Ken wrote: Some progress... I haven't spent much time looking at the IIS logs but rather at the isapi_redirect logs. But today I did and happened to notice that the old logs for Tomcat before I upgraded and things stopped working has this when it redirects to Tomcat: GET /jakarta/isapi_redirector.dll - 200 Java1.4.0_01 The new logs where it's failing show this instead: GET /jakarta/isapi_redirector.dll - 200 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) Both show 200 to indicate that they're forwarding successfully I think. But the successful one seems to link to Java and the unsuccessful to the browser. Once I get that figured out I'm hoping problem may be solved. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 6:09 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Thanks Jason, Yes I've edited the registry over and over, trying forward slashes, backslashed backwards slashes, etc. in path name all to know avail. I'm going to call it quits for today and hope that something will make more sense tomorrow. If not I guess I'll just start from scratch with a reinstallation. The fact the the redirect logs say that they've found so many rules and then found matches against those rules makes me think that there is no problem finding the uriworkermap.properties files, since that's where these are defined. But something sure is whacky with the loading of isapi_redirect(or). Maybe tomorrow it will all make more sense. Thanks much for all your efforts in trying to solve it. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 5:21 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 04:53, Januski, Ken wrote: I've honed uriworkermap.properties down to just this simple one below and have only tried accessing pages that it should find, like http://inqtomcat/examples/jsp/index.html I'm taking a guess here that it isn't finding your uriworkermap.properties file and it is trying to load everything including the DLL (which obviously should be loaded by IIS). Have you got all the registry keys setup correctly as per the following page? http://www.onjava.com/pub/a/onjava/2002/12/18/tomcat.html?page=2 Regards, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connectors for IIS/Tomcat SHOULD make sense
yes, i've installed it over and over, making sure that i allow execute access. and isapi_filter is green. -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 2:46 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Next question... Does your jakarta virtual directory in IIS have execute access checked? Regards, -- Jason Bainbridge http://jblinux.org On Thu, 26 Jun 2003 02:41, Januski, Ken wrote: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation] [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector] [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0] extension_uri=/jakarta/isapi_redirector.dll log_file=C:Tomcat4112logsisapi.log log_level=debug worker_file=C:/Tomcat4112/conf/workers.properties worker_mount_file=C:/Tomcat4112/conf/uriworkermap.properties @= -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 2:36 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Just for a sanity check can you export your registry settings for the below key and send them to the list? HKEY_LOCAL_MACHINE SOFTWARE Apache Software Foundation Jakarta Isapi Redirector 1.0 Regards, Jason On Thu, 26 Jun 2003 02:23, Januski, Ken wrote: Some progress... I haven't spent much time looking at the IIS logs but rather at the isapi_redirect logs. But today I did and happened to notice that the old logs for Tomcat before I upgraded and things stopped working has this when it redirects to Tomcat: GET /jakarta/isapi_redirector.dll - 200 Java1.4.0_01 The new logs where it's failing show this instead: GET /jakarta/isapi_redirector.dll - 200 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) Both show 200 to indicate that they're forwarding successfully I think. But the successful one seems to link to Java and the unsuccessful to the browser. Once I get that figured out I'm hoping problem may be solved. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 6:09 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Thanks Jason, Yes I've edited the registry over and over, trying forward slashes, backslashed backwards slashes, etc. in path name all to know avail. I'm going to call it quits for today and hope that something will make more sense tomorrow. If not I guess I'll just start from scratch with a reinstallation. The fact the the redirect logs say that they've found so many rules and then found matches against those rules makes me think that there is no problem finding the uriworkermap.properties files, since that's where these are defined. But something sure is whacky with the loading of isapi_redirect(or). Maybe tomorrow it will all make more sense. Thanks much for all your efforts in trying to solve it. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 5:21 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 04:53, Januski, Ken wrote: I've honed uriworkermap.properties down to just this simple one below and have only tried accessing pages that it should find, like http://inqtomcat/examples/jsp/index.html I'm taking a guess here that it isn't finding your uriworkermap.properties file and it is trying to load everything including the DLL (which obviously should be loaded by IIS). Have you got all the registry keys setup correctly as per the following page? http://www.onjava.com/pub/a/onjava/2002/12/18/tomcat.html?page=2 Regards, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connectors for IIS/Tomcat SHOULD make sense
Hmmm was just browsing the source directories and came across the attached (well hopefully it makes it to the list atleast) .vbs script to automate the install somewhat, this should be much more visible to users... Anyway can you give it a go and see how you go? I haven't even run it myself so I have no idea if it will work or not but it can't hurt. :) Regards, Jason On Thu, 26 Jun 2003 02:51, Januski, Ken wrote: yes, i've installed it over and over, making sure that i allow execute access. and isapi_filter is green. -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 2:46 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Next question... Does your jakarta virtual directory in IIS have execute access checked? Regards, -- Jason Bainbridge http://jblinux.org isapi.zip Description: Zip archive - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connectors for IIS/Tomcat SHOULD make sense
On Thu, 26 Jun 2003 03:00, Jason Bainbridge wrote: Hmmm was just browsing the source directories and came across the attached (well hopefully it makes it to the list atleast) .vbs script to automate the install somewhat, this should be much more visible to users... *mental note to self* Next time rename the .vbs to .txt before sending even if it is zipped, I'm getting rejections galore from all the paranoid servers out there... -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connectors for IIS/Tomcat SHOULD make sense
yes i saw the first couple and hoped that was the end. i guess that's the thanks you get for trying to do a good deed and help me get this albatross off my neck. -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 3:08 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Thu, 26 Jun 2003 03:00, Jason Bainbridge wrote: Hmmm was just browsing the source directories and came across the attached (well hopefully it makes it to the list atleast) .vbs script to automate the install somewhat, this should be much more visible to users... *mental note to self* Next time rename the .vbs to .txt before sending even if it is zipped, I'm getting rejections galore from all the paranoid servers out there... -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connectors for IIS/Tomcat SHOULD make sense
Any idea why it is trying to map the below? '/inqtomcat/jakarta/isapi_redirector.dll' Have you got your IIS setup like that? If you do it has to be: '/jakarta/isapi_redirector.dll' I just re-read your original email over and over, whilst scanning through the source and that jumped out at me, it could be nothing and is validly including your host name but it's worth checking out atleast... Regards, Jason On Thu, 26 Jun 2003 02:41, Januski, Ken wrote: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation] [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector] [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0] extension_uri=/jakarta/isapi_redirector.dll log_file=C:Tomcat4112logsisapi.log log_level=debug worker_file=C:/Tomcat4112/conf/workers.properties worker_mount_file=C:/Tomcat4112/conf/uriworkermap.properties @= -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 2:36 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Just for a sanity check can you export your registry settings for the below key and send them to the list? HKEY_LOCAL_MACHINE SOFTWARE Apache Software Foundation Jakarta Isapi Redirector 1.0 Regards, Jason On Thu, 26 Jun 2003 02:23, Januski, Ken wrote: Some progress... I haven't spent much time looking at the IIS logs but rather at the isapi_redirect logs. But today I did and happened to notice that the old logs for Tomcat before I upgraded and things stopped working has this when it redirects to Tomcat: GET /jakarta/isapi_redirector.dll - 200 Java1.4.0_01 The new logs where it's failing show this instead: GET /jakarta/isapi_redirector.dll - 200 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) Both show 200 to indicate that they're forwarding successfully I think. But the successful one seems to link to Java and the unsuccessful to the browser. Once I get that figured out I'm hoping problem may be solved. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 6:09 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Thanks Jason, Yes I've edited the registry over and over, trying forward slashes, backslashed backwards slashes, etc. in path name all to know avail. I'm going to call it quits for today and hope that something will make more sense tomorrow. If not I guess I'll just start from scratch with a reinstallation. The fact the the redirect logs say that they've found so many rules and then found matches against those rules makes me think that there is no problem finding the uriworkermap.properties files, since that's where these are defined. But something sure is whacky with the loading of isapi_redirect(or). Maybe tomorrow it will all make more sense. Thanks much for all your efforts in trying to solve it. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 5:21 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 04:53, Januski, Ken wrote: I've honed uriworkermap.properties down to just this simple one below and have only tried accessing pages that it should find, like http://inqtomcat/examples/jsp/index.html I'm taking a guess here that it isn't finding your uriworkermap.properties file and it is trying to load everything including the DLL (which obviously should be loaded by IIS). Have you got all the registry keys setup correctly as per the following page? http://www.onjava.com/pub/a/onjava/2002/12/18/tomcat.html?page=2 Regards, -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connectors for IIS/Tomcat SHOULD make sense
I think that it appends the hostname regardless of what it is. So logs show it trying inqtomcat/jakarta/isapi_redirector.dll or localhost/jakarta/isapi_redirector.dll depending on what I put for host in worker.properties. A few lines later in logs it tries to do the same thing with just /jakarta/isapi_redirector.dll and also fails, and in fact that's the final error that show up on the tomcat error page. But I think that it really shouldn't be trying to find them at any path. Instead it should be executing the filter. And I think that's why the IIS log shows the browser after the get isapi_redirector.dll rather than java as the old successful log does. -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 3:46 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Any idea why it is trying to map the below? '/inqtomcat/jakarta/isapi_redirector.dll' Have you got your IIS setup like that? If you do it has to be: '/jakarta/isapi_redirector.dll' I just re-read your original email over and over, whilst scanning through the source and that jumped out at me, it could be nothing and is validly including your host name but it's worth checking out atleast... Regards, Jason On Thu, 26 Jun 2003 02:41, Januski, Ken wrote: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation] [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector] [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0] extension_uri=/jakarta/isapi_redirector.dll log_file=C:Tomcat4112logsisapi.log log_level=debug worker_file=C:/Tomcat4112/conf/workers.properties worker_mount_file=C:/Tomcat4112/conf/uriworkermap.properties @= -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 2:36 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Just for a sanity check can you export your registry settings for the below key and send them to the list? HKEY_LOCAL_MACHINE SOFTWARE Apache Software Foundation Jakarta Isapi Redirector 1.0 Regards, Jason On Thu, 26 Jun 2003 02:23, Januski, Ken wrote: Some progress... I haven't spent much time looking at the IIS logs but rather at the isapi_redirect logs. But today I did and happened to notice that the old logs for Tomcat before I upgraded and things stopped working has this when it redirects to Tomcat: GET /jakarta/isapi_redirector.dll - 200 Java1.4.0_01 The new logs where it's failing show this instead: GET /jakarta/isapi_redirector.dll - 200 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) Both show 200 to indicate that they're forwarding successfully I think. But the successful one seems to link to Java and the unsuccessful to the browser. Once I get that figured out I'm hoping problem may be solved. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 6:09 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Thanks Jason, Yes I've edited the registry over and over, trying forward slashes, backslashed backwards slashes, etc. in path name all to know avail. I'm going to call it quits for today and hope that something will make more sense tomorrow. If not I guess I'll just start from scratch with a reinstallation. The fact the the redirect logs say that they've found so many rules and then found matches against those rules makes me think that there is no problem finding the uriworkermap.properties files, since that's where these are defined. But something sure is whacky with the loading of isapi_redirect(or). Maybe tomorrow it will all make more sense. Thanks much for all your efforts in trying to solve it. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 5:21 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 04:53, Januski, Ken wrote: I've honed uriworkermap.properties down to just this simple one below and have only tried accessing pages that it should find, like http://inqtomcat/examples/jsp/index.html I'm taking a guess here that it isn't finding your uriworkermap.properties file and it is trying to load everything including the DLL (which obviously should be loaded by IIS). Have you got all the registry keys setup correctly as per the following page? http://www.onjava.com/pub/a/onjava/2002/12/18/tomcat.html?page=2 Regards, -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail
Re: Connectors for IIS/Tomcat SHOULD make sense
The saga continues... Can you add the below to your workers.properties? worker.ajp13.lbfactor=50 worker.ajp13.cachesize=10 worker.ajp13.cache_timeout=600 worker.ajp13.socket_keepalive=1 worker.ajp13.socket_timeout=300 Also try renaming your worker to something other than ajp13 it could be confusing the server. I'm starting to run out of ideas, like I so often do with anything IIS related -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connectors for IIS/Tomcat SHOULD make sense
I think you should take a 12 ga. shotgun and put that server out of its misery. John On Thu, 26 Jun 2003 04:13:24 +0800, Jason Bainbridge [EMAIL PROTECTED] wrote: The saga continues... Can you add the below to your workers.properties? worker.ajp13.lbfactor=50 worker.ajp13.cachesize=10 worker.ajp13.cache_timeout=600 worker.ajp13.socket_keepalive=1 worker.ajp13.socket_timeout=300 Also try renaming your worker to something other than ajp13 it could be confusing the server. I'm starting to run out of ideas, like I so often do with anything IIS related -- 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]
RE: Connectors for IIS/Tomcat SHOULD make sense
well yes. but you know since i first had a similar problem about 3-4 months ago i've followed most threads where other people had similar problems. and in most cases i never saw a clear cut solution. i'm beginning to think it's the connectors that need to be put out of their misery. -Original Message- From: John Turner [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 4:17 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense I think you should take a 12 ga. shotgun and put that server out of its misery. John On Thu, 26 Jun 2003 04:13:24 +0800, Jason Bainbridge [EMAIL PROTECTED] wrote: The saga continues... Can you add the below to your workers.properties? worker.ajp13.lbfactor=50 worker.ajp13.cachesize=10 worker.ajp13.cache_timeout=600 worker.ajp13.socket_keepalive=1 worker.ajp13.socket_timeout=300 Also try renaming your worker to something other than ajp13 it could be confusing the server. I'm starting to run out of ideas, like I so often do with anything IIS related -- 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]
Re: Connectors for IIS/Tomcat SHOULD make sense
On Thu, 26 Jun 2003 04:17, John Turner wrote: I think you should take a 12 ga. shotgun and put that server out of its misery. Either that and goto management and tell them you have spent X hours on this already to get it to work but if you were allowed to use Apache you'd already have it working... Anyway noticed you had: ps=# in your workers.properties, I'm not sure if that gets used anywhere outside of the properties file but it should be: ps=\ For a windows environment. Failing these last few suggestions can you send me all of the actual configuration files (the files themselves not the text) off list? Regards, -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connectors for IIS/Tomcat SHOULD make sense
Have you tried giving 'Everyone' full permissions on the directory containing isapi_redirector.dll and on the file itself in the file system (not IIS)? I am determined to get this damn thing working. :) -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connectors for IIS/Tomcat SHOULD make sense
yes. sad to say i've already checked that a number of times. also the ps# has been corrected off and on as i've meddled with file. it seems to make no difference. i'm also determined to get it working and to document what i had to do to get it working. but i don't want to clutter up the list with it. unfortunately from what i've seen most of the threads with this problem just seem to fizzle out without resolution. it would be nice to see one get resolved, esp. since it's mine.:-) -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 4:37 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Have you tried giving 'Everyone' full permissions on the directory containing isapi_redirector.dll and on the file itself in the file system (not IIS)? I am determined to get this damn thing working. :) -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connectors for IIS/Tomcat SHOULD make sense
I'm down to last resort stage... Tomorrow if you want to I can invite you to a WebEx online meeting and if you install the Java client (it should be seamless on Windows) I will be able to see your dekstop and check out your IIS configuration as I think that is where the problem is. How's that for dedication? :) Regards, -- Jason Bainbridge http://jblinux.org On Thu, 26 Jun 2003 04:43, Januski, Ken wrote: yes. sad to say i've already checked that a number of times. also the ps# has been corrected off and on as i've meddled with file. it seems to make no difference. i'm also determined to get it working and to document what i had to do to get it working. but i don't want to clutter up the list with it. unfortunately from what i've seen most of the threads with this problem just seem to fizzle out without resolution. it would be nice to see one get resolved, esp. since it's mine.:-) -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 4:37 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Have you tried giving 'Everyone' full permissions on the directory containing isapi_redirector.dll and on the file itself in the file system (not IIS)? I am determined to get this damn thing working. :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connectors for IIS/Tomcat SHOULD make sense
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, -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connectors for IIS/Tomcat SHOULD make sense
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]
RE: Connectors for IIS/Tomcat SHOULD make sense
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
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
RE: Connectors for IIS/Tomcat SHOULD make sense
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
Re: Connectors for IIS/Tomcat SHOULD make sense
Lets get back to basics... Is the ISAPI plugin showing with a green arrow in IIS indicating it has been loaded successfully? What does your uriworkermap.properties file look like? What is throwing the 404? Tomcat or IIS? What URL are you trying to access when you get the 404? Regards, -- Jason Bainbridge http://jblinux.org On Wed, 25 Jun 2003 02:27, Januski, Ken 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
RE: Connectors for IIS/Tomcat SHOULD make sense
Hi Ken, This link explains how to install Tomcat 4.0.5 with IIS. http://support.esri.com/index.cfm?fa=knowledgebase.techarticles.articleShow; d=24055 I followed the instructions and worked. (with some help of this list) I hope it can help you. Regards. Jose Oyervides. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 1:28 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense 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
RE: Connectors for IIS/Tomcat SHOULD make sense
Thanks Jose, Those are the instructions I've been using, and reusing, but I keep getting the 404 errors. Ken -Original Message- From: Jose Santiago Oyervides Gonzalez [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 2:54 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Hi Ken, This link explains how to install Tomcat 4.0.5 with IIS. http://support.esri.com/index.cfm?fa=knowledgebase.techarticles.articleShow; d=24055 I followed the instructions and worked. (with some help of this list) I hope it can help you. Regards. Jose Oyervides. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 1:28 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense 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
Re: Connectors for IIS/Tomcat SHOULD make sense
Have you tried this URL? http://www.onjava.com/pub/a/onjava/2002/12/18/tomcat.html Its the one I would use if I was setting it up. John On Tue, 24 Jun 2003 14:58:48 -0400, Januski, Ken [EMAIL PROTECTED] wrote: Thanks Jose, Those are the instructions I've been using, and reusing, but I keep getting the 404 errors. Ken -Original Message- From: Jose Santiago Oyervides Gonzalez [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 2:54 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Hi Ken, This link explains how to install Tomcat 4.0.5 with IIS. http://support.esri.com/index.cfm?fa=knowledgebase.techarticles.articleShow; d=24055 I followed the instructions and worked. (with some help of this list) I hope it can help you. Regards. Jose Oyervides. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 1:28 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense 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
Re: Connectors for IIS/Tomcat SHOULD make sense
On Wed, 25 Jun 2003 02:58, Januski, Ken wrote: 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. That tells me something is wrong with loading the ISAPI plugin on the IIS side of the fence, so is the green arrow showing in IIS? Regards, -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connectors for IIS/Tomcat SHOULD make sense
Hi Jason, Yes the green arrow is green and pointing up. I've removed and added both the filter and the virtual directory many times. I really seem to have no problem getting it to work. I believe that it's Tomcat that is causing the problem as the log indicates an ajp13 worker is created. Also most of the various urls I've tried get a match in the log. So this indicates to me that the properties files are being used. So for example my minimal worker.properties has /examples/*=ajp13. If I use http://inqtomcat/examples/; the log shows that a match is found in uriworkermap.properties. HttpFilterProc then checks to see if it's a servlet, etc. However the log then shows that it tries to map /jakarta/isapi_redirector.dll and doesn't find a match. I don't think it should be trying to match that or map it. Also I've tried /examples or other files with inqtomcat:8080 and they work fine. So it looks to me like the filter is redirecting from IIS to Tomcat as it should but Tomcat then is trying to do the wrong thing with the file. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 2:54 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Lets get back to basics... Is the ISAPI plugin showing with a green arrow in IIS indicating it has been loaded successfully? What does your uriworkermap.properties file look like? What is throwing the 404? Tomcat or IIS? What URL are you trying to access when you get the 404? Regards, -- Jason Bainbridge http://jblinux.org On Wed, 25 Jun 2003 02:27, Januski, Ken 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
Re: Connectors for IIS/Tomcat SHOULD make sense
Hi Ken I have a suggestion. You should try using JK2 instead of JK, ie use isapi_redirector2.dll. If you want, I can send you all my working configs for this connector. If you don't want to use it, try posting your workers.properties file, and we can try to spot that typo Cheers Dom - Original Message - From: Januski, Ken To: Tomcat Users List Sent: Tuesday, June 24, 2003 9:10 PM Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Hi Jason, Yes the green arrow is green and pointing up. I've removed and added both the filter and the virtual directory many times. I really seem to have no problem getting it to work. I believe that it's Tomcat that is causing the problem as the log indicates an ajp13 worker is created. Also most of the various urls I've tried get a match in the log. So this indicates to me that the properties files are being used. So for example my minimal worker.properties has /examples/*=ajp13. If I use http://inqtomcat/examples/; the log shows that a match is found in uriworkermap.properties. HttpFilterProc then checks to see if it's a servlet, etc. However the log then shows that it tries to map /jakarta/isapi_redirector.dll and doesn't find a match. I don't think it should be trying to match that or map it. Also I've tried /examples or other files with inqtomcat:8080 and they work fine. So it looks to me like the filter is redirecting from IIS to Tomcat as it should but Tomcat then is trying to do the wrong thing with the file. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 2:54 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Lets get back to basics... Is the ISAPI plugin showing with a green arrow in IIS indicating it has been loaded successfully? What does your uriworkermap.properties file look like? What is throwing the 404? Tomcat or IIS? What URL are you trying to access when you get the 404? Regards, -- Jason Bainbridge http://jblinux.org On Wed, 25 Jun 2003 02:27, Januski, Ken 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
RE: Connectors for IIS/Tomcat SHOULD make sense
Thanks Dom, I've wondered about using JK2 but since the ESRI instructions for ArcIMS say that JK should work I thought I'd stick with that. I just don't know much about JK2 so didn't want to perhaps complicate the problem. So for now I'm including worker.properties. If that doesn't help I may take you up on your offer for your JK2 configuration files. # workers.tomcat_home=C:\Tomcat4112 # workers.java_home=C:\java\jdk1.4 # # 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 worker.ajp13.type=ajp13 #*End worker.properties* Thanks to everyone who's spending time on this, Ken -Original Message- From: Dominic Parry [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:30 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Hi Ken I have a suggestion. You should try using JK2 instead of JK, ie use isapi_redirector2.dll. If you want, I can send you all my working configs for this connector. If you don't want to use it, try posting your workers.properties file, and we can try to spot that typo Cheers Dom - Original Message - From: Januski, Ken To: Tomcat Users List Sent: Tuesday, June 24, 2003 9:10 PM Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Hi Jason, Yes the green arrow is green and pointing up. I've removed and added both the filter and the virtual directory many times. I really seem to have no problem getting it to work. I believe that it's Tomcat that is causing the problem as the log indicates an ajp13 worker is created. Also most of the various urls I've tried get a match in the log. So this indicates to me that the properties files are being used. So for example my minimal worker.properties has /examples/*=ajp13. If I use http://inqtomcat/examples/; the log shows that a match is found in uriworkermap.properties. HttpFilterProc then checks to see if it's a servlet, etc. However the log then shows that it tries to map /jakarta/isapi_redirector.dll and doesn't find a match. I don't think it should be trying to match that or map it. Also I've tried /examples or other files with inqtomcat:8080 and they work fine. So it looks to me like the filter is redirecting from IIS to Tomcat as it should but Tomcat then is trying to do the wrong thing with the file. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 2:54 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Lets get back to basics... Is the ISAPI plugin showing with a green arrow in IIS indicating it has been loaded successfully? What does your uriworkermap.properties file look like? What is throwing the 404? Tomcat or IIS? What URL are you trying to access when you get the 404? Regards, -- Jason Bainbridge http://jblinux.org On Wed, 25 Jun 2003 02:27, Januski, Ken 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
Re: Connectors for IIS/Tomcat SHOULD make sense
A couple things: - the file should be workers.properties, not worker.properties - the host parameter has to be something that the redirector can find...so if you aren't using localhost, you are better off with an IP address I'm assuming you made all the registry entries, right? HTH John On Tue, 24 Jun 2003 15:34:40 -0400, Januski, Ken [EMAIL PROTECTED] wrote: Thanks Dom, I've wondered about using JK2 but since the ESRI instructions for ArcIMS say that JK should work I thought I'd stick with that. I just don't know much about JK2 so didn't want to perhaps complicate the problem. So for now I'm including worker.properties. If that doesn't help I may take you up on your offer for your JK2 configuration files. # workers.tomcat_home=C:\Tomcat4112 # workers.java_home=C:\java\jdk1.4 # # 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 worker.ajp13.type=ajp13 #*End worker.properties* Thanks to everyone who's spending time on this, Ken -Original Message- From: Dominic Parry [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:30 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Hi Ken I have a suggestion. You should try using JK2 instead of JK, ie use isapi_redirector2.dll. If you want, I can send you all my working configs for this connector. If you don't want to use it, try posting your workers.properties file, and we can try to spot that typo Cheers Dom - Original Message - From: Januski, Ken To: Tomcat Users List Sent: Tuesday, June 24, 2003 9:10 PM Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Hi Jason, Yes the green arrow is green and pointing up. I've removed and added both the filter and the virtual directory many times. I really seem to have no problem getting it to work. I believe that it's Tomcat that is causing the problem as the log indicates an ajp13 worker is created. Also most of the various urls I've tried get a match in the log. So this indicates to me that the properties files are being used. So for example my minimal worker.properties has /examples/*=ajp13. If I use http://inqtomcat/examples/; the log shows that a match is found in uriworkermap.properties. HttpFilterProc then checks to see if it's a servlet, etc. However the log then shows that it tries to map /jakarta/isapi_redirector.dll and doesn't find a match. I don't think it should be trying to match that or map it. Also I've tried /examples or other files with inqtomcat:8080 and they work fine. So it looks to me like the filter is redirecting from IIS to Tomcat as it should but Tomcat then is trying to do the wrong thing with the file. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 2:54 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Lets get back to basics... Is the ISAPI plugin showing with a green arrow in IIS indicating it has been loaded successfully? What does your uriworkermap.properties file look like? What is throwing the 404? Tomcat or IIS? What URL are you trying to access when you get the 404? Regards, -- Jason Bainbridge http://jblinux.org On Wed, 25 Jun 2003 02:27, Januski, Ken 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
RE: Connectors for IIS/Tomcat SHOULD make sense
Hmm. You know I've found references to both worker.properties and workers.properties and haven't found an explanation of why both seem to be used. I believe I've used both names in my lengthy attempts to get this to work. But I'll change it and see what happens. I've also used the inqtomcat host name in the past when I used Tomcat 4.0 so thought I could use it again. Also I've changed it back to localhost in my many tests but still ran into failures. But I'll also try localhost again just to see. Yes, registry files are consistent with everything else. I'll check them one more time with these new changes and see what happens. -Original Message- From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:40 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense A couple things: - the file should be workers.properties, not worker.properties - the host parameter has to be something that the redirector can find...so if you aren't using localhost, you are better off with an IP address I'm assuming you made all the registry entries, right? HTH John On Tue, 24 Jun 2003 15:34:40 -0400, Januski, Ken [EMAIL PROTECTED] wrote: Thanks Dom, I've wondered about using JK2 but since the ESRI instructions for ArcIMS say that JK should work I thought I'd stick with that. I just don't know much about JK2 so didn't want to perhaps complicate the problem. So for now I'm including worker.properties. If that doesn't help I may take you up on your offer for your JK2 configuration files. # workers.tomcat_home=C:\Tomcat4112 # workers.java_home=C:\java\jdk1.4 # # 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 worker.ajp13.type=ajp13 #*End worker.properties* Thanks to everyone who's spending time on this, Ken -Original Message- From: Dominic Parry [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:30 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Hi Ken I have a suggestion. You should try using JK2 instead of JK, ie use isapi_redirector2.dll. If you want, I can send you all my working configs for this connector. If you don't want to use it, try posting your workers.properties file, and we can try to spot that typo Cheers Dom - Original Message - From: Januski, Ken To: Tomcat Users List Sent: Tuesday, June 24, 2003 9:10 PM Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Hi Jason, Yes the green arrow is green and pointing up. I've removed and added both the filter and the virtual directory many times. I really seem to have no problem getting it to work. I believe that it's Tomcat that is causing the problem as the log indicates an ajp13 worker is created. Also most of the various urls I've tried get a match in the log. So this indicates to me that the properties files are being used. So for example my minimal worker.properties has /examples/*=ajp13. If I use http://inqtomcat/examples/; the log shows that a match is found in uriworkermap.properties. HttpFilterProc then checks to see if it's a servlet, etc. However the log then shows that it tries to map /jakarta/isapi_redirector.dll and doesn't find a match. I don't think it should be trying to match that or map it. Also I've tried /examples or other files with inqtomcat:8080 and they work fine. So it looks to me like the filter is redirecting from IIS to Tomcat as it should but Tomcat then is trying to do the wrong thing with the file. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 2:54 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Lets get back to basics... Is the ISAPI plugin showing with a green arrow in IIS indicating it has been loaded successfully? What does your uriworkermap.properties file look like? What is throwing the 404? Tomcat or IIS? What URL are you trying to access when you get the 404? Regards, -- Jason Bainbridge http://jblinux.org On Wed, 25 Jun 2003 02:27, Januski, Ken 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
Re: Connectors for IIS/Tomcat SHOULD make sense
On Wed, 25 Jun 2003 02:53, Jason Bainbridge wrote: What does your uriworkermap.properties file look like? What is throwing the 404? Tomcat or IIS? What URL are you trying to access when you get the 404? Can you please answer these questions? It will help work out what the actual problem is so we can try to resolve it better... -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connectors for IIS/Tomcat SHOULD make sense
Jason, I just used this address: http://inqtomcat/examples/jsp/index.html It failed with the /jakarta/isapi_redirector.dll is not available error. If I use this address I'm fine: http://inqtomcat/examples/jsp/index.html I can substitute localhost for inqtomcat with same results. The errors are in the isapi_redirector log. Whether IIS or Tomcat is throwing the errors is a matter of guesswork as far as I can tell. This is the exact line from log: [jk_ajp_common.c (461)]: ajp_unmarshal_response: status = 404 I actually was hoping that someone on the list could tell ME what's throwing the error. I think if I knew that I'd be a lot closer to a solution. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:51 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 02:53, Jason Bainbridge wrote: What does your uriworkermap.properties file look like? What is throwing the 404? Tomcat or IIS? What URL are you trying to access when you get the 404? Can you please answer these questions? It will help work out what the actual problem is so we can try to resolve it better... -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connectors for IIS/Tomcat SHOULD make sense
After changing name of file from worker.properties to workers.properties and changing the host back to localhost, and then changing registry to reflect this I still get the same errors: 404, resource /jakarta/isapi_redirector.dll is not available. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:47 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Hmm. You know I've found references to both worker.properties and workers.properties and haven't found an explanation of why both seem to be used. I believe I've used both names in my lengthy attempts to get this to work. But I'll change it and see what happens. I've also used the inqtomcat host name in the past when I used Tomcat 4.0 so thought I could use it again. Also I've changed it back to localhost in my many tests but still ran into failures. But I'll also try localhost again just to see. Yes, registry files are consistent with everything else. I'll check them one more time with these new changes and see what happens. -Original Message- From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:40 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense A couple things: - the file should be workers.properties, not worker.properties - the host parameter has to be something that the redirector can find...so if you aren't using localhost, you are better off with an IP address I'm assuming you made all the registry entries, right? HTH John On Tue, 24 Jun 2003 15:34:40 -0400, Januski, Ken [EMAIL PROTECTED] wrote: Thanks Dom, I've wondered about using JK2 but since the ESRI instructions for ArcIMS say that JK should work I thought I'd stick with that. I just don't know much about JK2 so didn't want to perhaps complicate the problem. So for now I'm including worker.properties. If that doesn't help I may take you up on your offer for your JK2 configuration files. # workers.tomcat_home=C:\Tomcat4112 # workers.java_home=C:\java\jdk1.4 # # 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 worker.ajp13.type=ajp13 #*End worker.properties* Thanks to everyone who's spending time on this, Ken -Original Message- From: Dominic Parry [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:30 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Hi Ken I have a suggestion. You should try using JK2 instead of JK, ie use isapi_redirector2.dll. If you want, I can send you all my working configs for this connector. If you don't want to use it, try posting your workers.properties file, and we can try to spot that typo Cheers Dom - Original Message - From: Januski, Ken To: Tomcat Users List Sent: Tuesday, June 24, 2003 9:10 PM Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Hi Jason, Yes the green arrow is green and pointing up. I've removed and added both the filter and the virtual directory many times. I really seem to have no problem getting it to work. I believe that it's Tomcat that is causing the problem as the log indicates an ajp13 worker is created. Also most of the various urls I've tried get a match in the log. So this indicates to me that the properties files are being used. So for example my minimal worker.properties has /examples/*=ajp13. If I use http://inqtomcat/examples/; the log shows that a match is found in uriworkermap.properties. HttpFilterProc then checks to see if it's a servlet, etc. However the log then shows that it tries to map /jakarta/isapi_redirector.dll and doesn't find a match. I don't think it should be trying to match that or map it. Also I've tried /examples or other files with inqtomcat:8080 and they work fine. So it looks to me like the filter is redirecting from IIS to Tomcat as it should but Tomcat then is trying to do the wrong thing with the file. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 2:54 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Lets get back to basics... Is the ISAPI plugin showing with a green arrow in IIS indicating it has been loaded successfully? What does your uriworkermap.properties file look like? What is throwing the 404? Tomcat or IIS? What URL are you trying to access when you get the 404? Regards, -- Jason Bainbridge http://jblinux.org On Wed, 25 Jun 2003 02:27, Januski, Ken wrote: Thanks John, I wasn't sure
RE: Connectors for IIS/Tomcat SHOULD make sense
Oops. I forgot to put the :8080 in the address that worked below. Basically if I put in :8080 everything is fine but without it I keep getting the same errors. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:59 PM To: Tomcat Users List Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Jason, I just used this address: http://inqtomcat/examples/jsp/index.html It failed with the /jakarta/isapi_redirector.dll is not available error. If I use this address I'm fine: http://inqtomcat/examples/jsp/index.html I can substitute localhost for inqtomcat with same results. The errors are in the isapi_redirector log. Whether IIS or Tomcat is throwing the errors is a matter of guesswork as far as I can tell. This is the exact line from log: [jk_ajp_common.c (461)]: ajp_unmarshal_response: status = 404 I actually was hoping that someone on the list could tell ME what's throwing the error. I think if I knew that I'd be a lot closer to a solution. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:51 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 02:53, Jason Bainbridge wrote: What does your uriworkermap.properties file look like? What is throwing the 404? Tomcat or IIS? What URL are you trying to access when you get the 404? Can you please answer these questions? It will help work out what the actual problem is so we can try to resolve it better... -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connectors for IIS/Tomcat SHOULD make sense
Hi Ken I'm assuming you mean that http://inqtomcat:8080/examples/jsp/index.html is working. Have you set the permissions on the folder containing the isapi dll such that your IUSER has read and execute permissions? -Dom - Original Message - From: Januski, Ken To: Tomcat Users List Sent: Tuesday, June 24, 2003 9:59 PM Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Jason, I just used this address: http://inqtomcat/examples/jsp/index.html It failed with the /jakarta/isapi_redirector.dll is not available error. If I use this address I'm fine: http://inqtomcat/examples/jsp/index.html I can substitute localhost for inqtomcat with same results. The errors are in the isapi_redirector log. Whether IIS or Tomcat is throwing the errors is a matter of guesswork as far as I can tell. This is the exact line from log: [jk_ajp_common.c (461)]: ajp_unmarshal_response: status = 404 I actually was hoping that someone on the list could tell ME what's throwing the error. I think if I knew that I'd be a lot closer to a solution. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:51 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 02:53, Jason Bainbridge wrote: What does your uriworkermap.properties file look like? What is throwing the 404? Tomcat or IIS? What URL are you trying to access when you get the 404? Can you please answer these questions? It will help work out what the actual problem is so we can try to resolve it better... -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connectors for IIS/Tomcat SHOULD make sense
Are you using MSIE? Try turning Friendly HTTP Error messages off, the page you get will then indicate what is throwing the 404, Tomcats will have that blue bar and what not. Also have you checked out the permissions on the DLL? On Wed, 25 Jun 2003 03:59, Januski, Ken wrote: Jason, I just used this address: http://inqtomcat/examples/jsp/index.html It failed with the /jakarta/isapi_redirector.dll is not available error. If I use this address I'm fine: http://inqtomcat/examples/jsp/index.html I can substitute localhost for inqtomcat with same results. The errors are in the isapi_redirector log. Whether IIS or Tomcat is throwing the errors is a matter of guesswork as far as I can tell. This is the exact line from log: [jk_ajp_common.c (461)]: ajp_unmarshal_response: status = 404 I actually was hoping that someone on the list could tell ME what's throwing the error. I think if I knew that I'd be a lot closer to a solution. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:51 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 02:53, Jason Bainbridge wrote: What does your uriworkermap.properties file look like? What is throwing the 404? Tomcat or IIS? What URL are you trying to access when you get the 404? Can you please answer these questions? It will help work out what the actual problem is so we can try to resolve it better... -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connectors for IIS/Tomcat SHOULD make sense
Yes Dom, I did mean http://inqtomcat:8080/examples/jsp/index.html I'm getting tired and making typos I'm afraid. I haven't permissions for IUSER on the folder containing the dll since this is the first time I've seen that suggested. I guess it's another possibility. Ken -Original Message- From: Dominic Parry [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 4:03 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Hi Ken I'm assuming you mean that http://inqtomcat:8080/examples/jsp/index.html is working. Have you set the permissions on the folder containing the isapi dll such that your IUSER has read and execute permissions? -Dom - Original Message - From: Januski, Ken To: Tomcat Users List Sent: Tuesday, June 24, 2003 9:59 PM Subject: RE: Connectors for IIS/Tomcat SHOULD make sense Jason, I just used this address: http://inqtomcat/examples/jsp/index.html It failed with the /jakarta/isapi_redirector.dll is not available error. If I use this address I'm fine: http://inqtomcat/examples/jsp/index.html I can substitute localhost for inqtomcat with same results. The errors are in the isapi_redirector log. Whether IIS or Tomcat is throwing the errors is a matter of guesswork as far as I can tell. This is the exact line from log: [jk_ajp_common.c (461)]: ajp_unmarshal_response: status = 404 I actually was hoping that someone on the list could tell ME what's throwing the error. I think if I knew that I'd be a lot closer to a solution. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:51 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 02:53, Jason Bainbridge wrote: What does your uriworkermap.properties file look like? What is throwing the 404? Tomcat or IIS? What URL are you trying to access when you get the 404? Can you please answer these questions? It will help work out what the actual problem is so we can try to resolve it better... -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connectors for IIS/Tomcat SHOULD make sense
Hi Ken Also you might like to have a look at this thread: http://www.mail-archive.com/[EMAIL PROTECTED]/thrd5.html#93616 - Original Message - From: Jason Bainbridge To: Tomcat Users List Sent: Tuesday, June 24, 2003 10:09 PM Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Are you using MSIE? Try turning Friendly HTTP Error messages off, the page you get will then indicate what is throwing the 404, Tomcats will have that blue bar and what not. Also have you checked out the permissions on the DLL? On Wed, 25 Jun 2003 03:59, Januski, Ken wrote: Jason, I just used this address: http://inqtomcat/examples/jsp/index.html It failed with the /jakarta/isapi_redirector.dll is not available error. If I use this address I'm fine: http://inqtomcat/examples/jsp/index.html I can substitute localhost for inqtomcat with same results. The errors are in the isapi_redirector log. Whether IIS or Tomcat is throwing the errors is a matter of guesswork as far as I can tell. This is the exact line from log: [jk_ajp_common.c (461)]: ajp_unmarshal_response: status = 404 I actually was hoping that someone on the list could tell ME what's throwing the error. I think if I knew that I'd be a lot closer to a solution. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:51 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 02:53, Jason Bainbridge wrote: What does your uriworkermap.properties file look like? What is throwing the 404? Tomcat or IIS? What URL are you trying to access when you get the 404? Can you please answer these questions? It will help work out what the actual problem is so we can try to resolve it better... -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connectors for IIS/Tomcat SHOULD make sense
Friendly messages are turned off but the error page is the familiar Tomcat one. It just slipped my mind that that indicated that Tomcat was throwing the error. I've set up permissions on the dll indentical to the ones that used to work, pretty broad all in all. Dom suggested looking at the IUSR permissions for it but I hadn't heard of that being necessary before. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 4:09 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense Are you using MSIE? Try turning Friendly HTTP Error messages off, the page you get will then indicate what is throwing the 404, Tomcats will have that blue bar and what not. Also have you checked out the permissions on the DLL? On Wed, 25 Jun 2003 03:59, Januski, Ken wrote: Jason, I just used this address: http://inqtomcat/examples/jsp/index.html It failed with the /jakarta/isapi_redirector.dll is not available error. If I use this address I'm fine: http://inqtomcat/examples/jsp/index.html I can substitute localhost for inqtomcat with same results. The errors are in the isapi_redirector log. Whether IIS or Tomcat is throwing the errors is a matter of guesswork as far as I can tell. This is the exact line from log: [jk_ajp_common.c (461)]: ajp_unmarshal_response: status = 404 I actually was hoping that someone on the list could tell ME what's throwing the error. I think if I knew that I'd be a lot closer to a solution. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:51 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 02:53, Jason Bainbridge wrote: What does your uriworkermap.properties file look like? What is throwing the 404? Tomcat or IIS? What URL are you trying to access when you get the 404? Can you please answer these questions? It will help work out what the actual problem is so we can try to resolve it better... -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connectors for IIS/Tomcat SHOULD make sense
On Wed, 25 Jun 2003 04:15, Januski, Ken wrote: Friendly messages are turned off but the error page is the familiar Tomcat one. It just slipped my mind that that indicated that Tomcat was throwing the error. I guess the question then is why is Tomcat trying to load /jakarta/isapi_redirector.dll? do you have a uriworkermap.properties file? -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connectors for IIS/Tomcat SHOULD make sense
I've honed uriworkermap.properties down to just this simple one below and have only tried accessing pages that it should find, like http://inqtomcat/examples/jsp/index.html I was also looking at the Professional Tomcat book and it mentioned running netstat -a to make sure port 8009 was listening. When I did I found two entries: one established and one listening. I'm not sure if that could have anything to do with the problem but I did want to mention it. # #Simple worker configuration file # #Mount the Servlet context to the ajp13 worker # /servlet/*=ajp13 # #Mount the examples context to the ajp13 worker # /examples/*=ajp13 # #Advanced mount of the examples context # #/examples/servlet/*=ajp13 # #*End uriworkermap.properties* -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 4:40 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 04:15, Januski, Ken wrote: Friendly messages are turned off but the error page is the familiar Tomcat one. It just slipped my mind that that indicated that Tomcat was throwing the error. I guess the question then is why is Tomcat trying to load /jakarta/isapi_redirector.dll? do you have a uriworkermap.properties file? -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connectors for IIS/Tomcat SHOULD make sense
On Wed, 25 Jun 2003 04:53, Januski, Ken wrote: I've honed uriworkermap.properties down to just this simple one below and have only tried accessing pages that it should find, like http://inqtomcat/examples/jsp/index.html I'm taking a guess here that it isn't finding your uriworkermap.properties file and it is trying to load everything including the DLL (which obviously should be loaded by IIS). Have you got all the registry keys setup correctly as per the following page? http://www.onjava.com/pub/a/onjava/2002/12/18/tomcat.html?page=2 Regards, -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connectors for IIS/Tomcat SHOULD make sense
I know this will seem trivial... but I've set several systems up now under NT4/W2k JK1 (both versions) and more recently JK2 and you can't beat a good reboot between changes to the configuration. Have you rebooted your server at all during these many tests? Part of the trouble is there are several flavors of JK1 connector and some don't work! Here's part of my diary for 7th February 2003... Decided to try and fix the problem with rebooting the server and Tomcat not coming up properly. Documentation is scarce! I already knew that there were two versions of redirector files; one called isapi_redirect.dll and one called isapi_redirector.dll. I had the notion that the latter was newer and that is what is currently being used on the site. I soon discovered this is no longer the case and the latest version is now called isapi_redirect.dll and can be found here (http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2. 2/bin/win32/). Guess my horror when I discovered a couple of weeks ago that there was yet another connector available (JK2) and all the configuration syntax was different yet again! Regards, David Legg Webmaster - 3Dlabs http://www.3dlabs.com mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connectors for IIS/Tomcat SHOULD make sense
Thanks for the advice David, Yes I've come to realize the value of a reboot. But I just tried once again after changing back to the isapi_redirect.dll and still got the same errors. So, after 8 hours today I'm going to call it quits for the day. Maybe some sort of magic will occur overnight. If not I guess I'll start from scratch again. Ken -Original Message- From: David Legg [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 5:34 PM To: 'Tomcat Users List' Subject: RE: Connectors for IIS/Tomcat SHOULD make sense I know this will seem trivial... but I've set several systems up now under NT4/W2k JK1 (both versions) and more recently JK2 and you can't beat a good reboot between changes to the configuration. Have you rebooted your server at all during these many tests? Part of the trouble is there are several flavors of JK1 connector and some don't work! Here's part of my diary for 7th February 2003... Decided to try and fix the problem with rebooting the server and Tomcat not coming up properly. Documentation is scarce! I already knew that there were two versions of redirector files; one called isapi_redirect.dll and one called isapi_redirector.dll. I had the notion that the latter was newer and that is what is currently being used on the site. I soon discovered this is no longer the case and the latest version is now called isapi_redirect.dll and can be found here (http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2. 2/bin/win32/). Guess my horror when I discovered a couple of weeks ago that there was yet another connector available (JK2) and all the configuration syntax was different yet again! Regards, David Legg Webmaster - 3Dlabs http://www.3dlabs.com mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connectors for IIS/Tomcat SHOULD make sense
Thanks Jason, Yes I've edited the registry over and over, trying forward slashes, backslashed backwards slashes, etc. in path name all to know avail. I'm going to call it quits for today and hope that something will make more sense tomorrow. If not I guess I'll just start from scratch with a reinstallation. The fact the the redirect logs say that they've found so many rules and then found matches against those rules makes me think that there is no problem finding the uriworkermap.properties files, since that's where these are defined. But something sure is whacky with the loading of isapi_redirect(or). Maybe tomorrow it will all make more sense. Thanks much for all your efforts in trying to solve it. Ken -Original Message- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 5:21 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense On Wed, 25 Jun 2003 04:53, Januski, Ken wrote: I've honed uriworkermap.properties down to just this simple one below and have only tried accessing pages that it should find, like http://inqtomcat/examples/jsp/index.html I'm taking a guess here that it isn't finding your uriworkermap.properties file and it is trying to load everything including the DLL (which obviously should be loaded by IIS). Have you got all the registry keys setup correctly as per the following page? http://www.onjava.com/pub/a/onjava/2002/12/18/tomcat.html?page=2 Regards, -- Jason Bainbridge http://jblinux.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connectors for IIS/Tomcat SHOULD make sense
Thanks Jason, Yes I've seen the link and read it a number of times but haven't gotten anywhere. I assume that the problem is in worker.properties but still can't find just what it is. I suppose it could be one of those stupid typos that you look at 50 times before recognizing but I'm sure I've looked at least 49 so far. (I'm using also worker rather than workers2 because I believe that should work with Tomcat 4.1.12. by the way. I've considered changing to workers2 but that could open up a whole new can of worms.) I did compare my logs to an old log that was working until I upgraded Tomcat. In that log there's no attempt to map isapi_redirector.dll so I figure that must be where things are going wrong. Thanks for the link to the source. I'm hoping I'll find the answer there. Ken -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, -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
