RE: RES: RES: Tomcat 6.0 on Windows Server 2003 IIS 6.0 connector not functioning
Hi, Just for the record, have you checked if isapi_redirect.dll is blocked by Windows 2003 protection for files downloaded from the internet? If you go in the properties of the dll file, and it is blocked, a big unblock button will be shown. I had this problem on Windows Server 2003 in both 32/64bits. The green arrow shows up, everything seems normal but it won't work if it's blocked. Hope that helps! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: May 14, 2007 4:46 PM To: Tomcat Users List Subject: Re: RES: RES: Tomcat 6.0 on Windows Server 2003 IIS 6.0 connector not functioning I tried adding the following lines to workers.properties from your config files, Marcus, worker.tomcat_home=C:\Program Files\Apache Software Foundation\Tomcat 6.0 worker.java_home=C:\Program Files\Java\jdk1.6.0 I tried using single quotes as well. I also tried your isapi_redirect.dll. Thanks for the contribution, but neither resolved the problem. I think my next step will be to start over and use pathnames without any spaces. It can't hurt anything at this point. Sean McKellips Systems Administrator Associated Grocers 206-767-8725 phone 206-764-7879 fax [EMAIL PROTECTED] [EMAIL PROTECTED] sea.com To 05/14/2007 10:09 Tomcat Users List AMusers@tomcat.apache.org cc Please respond to Subject Tomcat Users Re: RES: RES: Tomcat 6.0 on Windows List Server 2003 IIS 6.0 connector not [EMAIL PROTECTED] functioning che.org I added one specific example explicity to get this: /servlets-examples/*=ajp13w /examples/*=ajp13w /examples/jsp/jsp2/el/basic-arithmetic.jsp=ajp13w /*=ajp13w !/servlets-examples/*.jpeg=ajp13w But I am still getting this from IIS: 2007-05-14 16:54:06 W3SVC1 127.0.0.1 GET /examples/jsp/jsp2/el/basic-arithmetic.jsp - 80 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 404 3 50 And, yes, I've been reseting IIS after every change and frequently tomcat too just to be safe. At this point I'm trying hard not to take anything for granted. I've been stuck on this for more time than I care to admit. Clearly I'm missing something, but I can't seem to find it. Can you think of anything I might be missing in the redirect settings? It seems to me this is the most likely place for my error, since I'm also not getting a log file. Here is the output when I export my registry key: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0] extension_uri=/jakarta/isapi_redirect.dll log_file=C:\\Program Files\\Apache Software Foundation\\Tomcat 6.0 \\logs\\isapi.log log_level=debug worker_file=C:\\Program Files\\Apache Software Foundation\\Tomcat 6.0 \\conf\\workers.properties worker_mount_file=C:\\Program Files\\Apache Software Foundation\\Tomcat 6.0\\conf\\uriworkermap.properties I also have isapi_redirect.properties in C:\Program Files\Apache Software Foundation\Tomcat 6.0\bin: # Configuration file for the Jakarta ISAPI Redirector # The path to the ISAPI Redirector Extension, relative to the website # This must be in a virtual directory with execute privileges extension_uri=/jakarta/isapi_redirect.dll # Full path to the log file for the ISAPI Redirector log_file=C:\Program Files\Apache Software Foundation\Tomcat 6.0 \logs\isapi_redirect.log # Log level (debug, info, warn, error or trace) log_level=debug # Full path to the workers.properties file worker_file=C:\Program Files\Apache Software Foundation\Tomcat 6.0 \conf\workers.properties # Full path to the uriworkermap.properties file worker_mount_file=C:\Program Files\Apache Software Foundation\Tomcat 6.0 \conf\uriworkermap.properties I know that the log file names do not match, but neither is getting created. If it finally does work, the log file name should tell me which one is working. I've also tried cutting and
RE: JK connector issue - Can't get JKStatus working with IIS 6.0
Hi, Thank you everyone for the support, it's really appreciated. I think my problem is a rule priority problem, here is the JK log with debug on: May 14 10:27:59 2007] [2564:2720] [debug] HttpFilterProc::jk_isapi_plugin.c (747): Filter started [Mon May 14 10:27:59 2007] [2564:2720] [debug] HttpFilterProc::jk_isapi_plugin.c (813): Virtual Host redirection of /hostname.domainname.com/jkmanager [Mon May 14 10:27:59 2007] [2564:2720] [debug] map_uri_to_worker::jk_uri_worker_map.c (449): Attempting to map URI '/hostname.domainname.com/jkmanager' from 2 maps [Mon May 14 10:27:59 2007] [2564:2720] [debug] map_uri_to_worker::jk_uri_worker_map.c (461): Attempting to map context URI '/jkmanager' [Mon May 14 10:27:59 2007] [2564:2720] [debug] map_uri_to_worker::jk_uri_worker_map.c (461): Attempting to map context URI '/*' [Mon May 14 10:27:59 2007] [2564:2720] [debug] map_uri_to_worker::jk_uri_worker_map.c (475): Found a wildchar match wlb - /* [Mon May 14 10:27:59 2007] [2564:2720] [debug] HttpFilterProc::jk_isapi_plugin.c (830): check if [/jkmanager] is points to the web-inf directory [Mon May 14 10:27:59 2007] [2564:2720] [debug] HttpFilterProc::jk_isapi_plugin.c (848): [/jkmanager] is a servlet url - should redirect to wlb [Mon May 14 10:27:59 2007] [2564:2720] [debug] wc_get_worker_for_name::jk_worker.c (111): found a worker wlb [Mon May 14 10:27:59 2007] [2564:2720] [debug] HttpExtensionProc::jk_isapi_plugin.c (1003): got a worker for name wlb Is it correct to say that my URI rule /*=wlb Has a higher priority than /jkmanager=jkstatus? If yes, it there a way to tell the JK to match the jkstatus rule prior to the other one? Thank you very much -Original Message- From: Rainer Jung [mailto:[EMAIL PROTECTED] Sent: May 12, 2007 7:02 AM To: Tomcat Users List Subject: Re: JK connector issue - Can't get JKStatus working with IIS 6.0 Since your original config looked OK, could you set your log level for the isapi redirector to trace and log startup and a single test against your configured status URL? Please post the results, so we can see, if the URL got mapped, and why the request didn't get forwarded. Regards, Rainer Mladen Turk wrote: Jean-Francois Beaulac wrote: The Connector itselfs works perfectly, I just want to enable the JKStatus page that shows information about the workers and also allow to make changes at runtime to work. In the documentation I've seen specific configuration for Apache HTTPD to mount the JKStatus, but I could not find similar information for IIS. I presume you have added in workers.properties ... worker.list=jkstatus,... ... worker.jkstatus.type=status Then inside uriworkermap.properties add something like: /one-very-fancy-manger=jkstatus Finally hitting the http://yourhost/one-very-fancy-manger will open you the whole new world :) Regards, Mladen. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- -- kippdata informationstechnologie GmbH Tel: 0228 98549 -0 Bornheimer Str. 33aFax: 0228 98549 -50 53111 Bonn www.kippdata.de HRB 8018 Amtsgericht Bonn / USt.-IdNr. DE 196 457 417 Geschäftsführer: Dr. Thomas Höfer, Rainer Jung, Sven Maurmann === kippdata informationstechnologie GmbH Tel: +49 228 98549 -0 Bornheimer Str. 33aFax: +49 228 98549 -50 D-53111 Bonn www.kippdata.de HRB 8018 Amtsgericht Bonn / USt.-IdNr. DE 196 457 417 Geschäftsführer: Dr. Thomas Höfer, Rainer Jung, Sven Maurmann - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JK connector issue - Can't get JKStatus working with IIS 6.0
Hi, Im currently trying to get the JKStatus to work with the apache JK connector and IIS6.0. Is there some special configuration I have to do in IIS to get it working? The ajp13 connector works fine but I cant get the JKStatus page. It returns me a Tomcat 404 Http error, which is weird since from my understanding Tomcat should not be involved at all with the JKStatus. Here are my workers.properties uriworkermap.properties files: This is my workers.properties file # workers.properties # # This file provides minimal jk configuration properties needed to # connect to Tomcat. # # The workers that jk should create and work with # worker.list=wlb,jkstatus # # Defining a worker named ajp13w and of type ajp13 # Note that the name and the type do not have to match. # worker.ajp13w.type=ajp13 worker.ajp13w.host=localhost worker.ajp13w.port=8023 # # Defining a load balancer # worker.wlb.type=lb worker.wlb.balance_workers=ajp13w # # Define status worker # worker.jkstatus.type=status worket.jkstatus.mount=/jkmanager This is my uriworkermap.properties # uriworkermap.properties - IIS # # This file provides sample mappings for example wlb # worker defined in workermap.properties.minimal # The general syntax for this file is: # [URL]=[Worker name] /*=wlb # # Mount jkstatus to /jkmanager # For production servers you will need to # secure the access to the /jkmanager url # /jkmanager=jkstatus Thank you Jean-Francois Beaulac [EMAIL PROTECTED] Jean-Francois Beaulac - VP Technologies mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] +1 514.598 0406 Beetext - http://www.beetext.com/ www.beetext.com Project Efficiency Solutions Check out our newsletter, The Hive - http://www.beetext.com/newsletter/apr07/index.html http://www.beetext.com/newsletter/apr07/index.html Lisez notre communiqué mensuel, La ruche - http://www.beetext.com/newsletter/apr07/index_fr.html http://www.beetext.com/newsletter/apr07/index_fr.html
RE: JK connector issue - Can't get JKStatus working with IIS 6.0
The Connector itselfs works perfectly, I just want to enable the JKStatus page that shows information about the workers and also allow to make changes at runtime to work. In the documentation I've seen specific configuration for Apache HTTPD to mount the JKStatus, but I could not find similar information for IIS. Thank you -Original Message- From: Milanez, Marcus [mailto:[EMAIL PROTECTED] Sent: May 11, 2007 4:01 PM To: Tomcat Users List Subject: RES: JK connector issue - Can't get JKStatus working with IIS 6.0 Hi Jean, I could succesfully integrate IIS 6 with Tomcat (also 6), and you really need an extra step to het it done: Note that in IIS 6, there is a new item named 'Web Service Extension'. Right click on it and then 'Add new Web Service Extension' . Name it jakarta and point it to your isapi_redirect.dll location. Doing that should solve your problem... Just let us know if it worked! Yours, Marcus -Mensagem original- De: Jean-Francois Beaulac [mailto:[EMAIL PROTECTED] Enviada em: sexta-feira, 11 de maio de 2007 14:49 Para: users@tomcat.apache.org Assunto: JK connector issue - Can't get JKStatus working with IIS 6.0 Hi, I'm currently trying to get the JKStatus to work with the apache JK connector and IIS6.0. Is there some special configuration I have to do in IIS to get it working? The ajp13 connector works fine but I can't get the JKStatus page. It returns me a Tomcat 404 Http error, which is weird since from my understanding Tomcat should not be involved at all with the JKStatus. Here are my workers.properties uriworkermap.properties files: This is my workers.properties file # workers.properties # # This file provides minimal jk configuration properties needed to # connect to Tomcat. # # The workers that jk should create and work with # worker.list=wlb,jkstatus # # Defining a worker named ajp13w and of type ajp13 # Note that the name and the type do not have to match. # worker.ajp13w.type=ajp13 worker.ajp13w.host=localhost worker.ajp13w.port=8023 # # Defining a load balancer # worker.wlb.type=lb worker.wlb.balance_workers=ajp13w # # Define status worker # worker.jkstatus.type=status worket.jkstatus.mount=/jkmanager This is my uriworkermap.properties # uriworkermap.properties - IIS # # This file provides sample mappings for example wlb # worker defined in workermap.properties.minimal # The general syntax for this file is: # [URL]=[Worker name] /*=wlb # # Mount jkstatus to /jkmanager # For production servers you will need to # secure the access to the /jkmanager url # /jkmanager=jkstatus Thank you Jean-Francois Beaulac [EMAIL PROTECTED] Jean-Francois Beaulac - VP Technologies mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] +1 514.598 0406 Beetext - http://www.beetext.com/ www.beetext.com Project Efficiency Solutions Check out our newsletter, The Hive - http://www.beetext.com/newsletter/apr07/index.html http://www.beetext.com/newsletter/apr07/index.html Lisez notre communiqué mensuel, La ruche - http://www.beetext.com/newsletter/apr07/index_fr.html http://www.beetext.com/newsletter/apr07/index_fr.html - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
org.apache.catalina.servlets.DefaultServlet won't deallocate
Hi, Sometimes when I reload/shutdown my application I see this error message in tomcat's console window: 1-Aug-2006 3:06:50 PM org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 26 instance(s) to be deallocated The number of instances is never the same. I made myself a custom tomcat build and added some debug in org.apache.catalina.core.StandardWrapper.unload() to know what class those instances belongs to. The instances which cannot be deallocated are instances of org.apache.catalina.servlets.DefaultServlet. Anybody has an idea of what could cause this? Thank you -- Jean-Francois Beaulac [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
