RE: Tomcat and IIS revisited!
-Original Message- From: Winer, Matthew [mailto:[EMAIL PROTECTED]] Sent: Monday, June 11, 2001 9:54 AM To: 'Tomcat-User (E-mail) Subject: Tomcat and IIS revisited! Ok well I have made some progress this morning. I now how the green up arrow for the ISAPI filter. I am so excited. Now I just have a couple more questions. Does it matter what the home directory is for my IIS web server? I did put in a virtual directory for jakarta. Now when I go to http://localhost/examples/jsp/index.html it asks for the uname and passwd for that directory. If I put in the correct information I get Cannot Find Server. Every time a request is made for the site I get two entries in the ISAPI.log file. An ISAPI_Close and an ISAPI_free. There is a little more on each line but that is about it. I have seen nothing in my ISS logs referring to jakarta or the GET /jakarta/isapi_redirect.dll One of my other questions is... Do I start the Tomcat Server in conjunction with the IIS. I have tried it both ways and still no success. I would assume that it has to be running being that is the whole Java part of this whole thing. Thank you for you help!! -Matt Winer First, Tomcat must be started before you begin requesting JSP/servlets. Otherwise, you will get a 500 (Internal Server) error. It doesn't matter, however if you stop and start Tomcat again without starting IIS - the filter can deal with it. Second, it sounds like you have the ISAPI debugging set pretty high. This is probably good for production but not debugging. I would suggest changing the debugging level to DEBUG in the registry and then restart IIS (the process, not instance) Lastly, if you are getting the IIS username/password prompt then its because you have restricted access to the virtual directory. Check your directory permissions in both the NT File Explorer and the IIS console - you must have public (anonymous) execute permissions for things to work. Randy
RE: Tomcat and IIS revisited
When I check the IIS log files I see a GET /jakarta/isapi_redirect.dll 401 It is a 401 error. I still have the jk_uri_worker_map_t::uri_worker_map_close, NULL parameter [jk_uri_worker_map.c (185)]: In jk_uri_worker_map_t::uri_worker_map_free, NULL parameters in my isapi.log file and I am about to throw this $#!* out the window. Thank you for you time -Matt Winer
RE: Tomcat and IIS revisited
Your workers file is not correct - from your previous messages, isapi_redirect is finding that the resource should be a redirect to Tomcat. The problem is it can't find the worker for the redirect - the right side of the mapping in uriworkermap.properties is not defined (or not correctly defined) in workers.properties. Randy -Original Message- From: Winer, Matthew [mailto:[EMAIL PROTECTED]] Sent: Monday, June 11, 2001 11:55 AM To: 'Tomcat-User (E-mail) Subject: RE: Tomcat and IIS revisited When I check the IIS log files I see a GET /jakarta/isapi_redirect.dll 401 It is a 401 error. I still have the jk_uri_worker_map_t::uri_worker_map_close, NULL parameter [jk_uri_worker_map.c (185)]: In jk_uri_worker_map_t::uri_worker_map_free, NULL parameters in my isapi.log file and I am about to throw this $#!* out the window. Thank you for you time -Matt Winer
RE: Tomcat and IIS revisited
Here is a copy of my workers.properties and uriworkermap.properties files. I was told that this is where my problem lies. If somebody could take a quick look, maybe see if anything is wrong. Thanks # # $Header: /home/cvs/jakarta-tomcat/src/etc/Attic/wrapper.properties,v 1.2.2.1 2000/10/16 01:59:22 larryi Exp $ # $Revision: 1.2.2.1 $ # $Date: 2000/10/16 01:59:22 $ # # # jk_service.properties - a bootstrup file for the Tomcat NT service. # # This file provides jk_nt_service with the needed information to # start tomcat at a different process. # # As a general note, the characters $( and ) are used internally to define # macros. Do not use them!!! # # Whenever you see a set of lines such as: # x=value # y=$(x)\something # # the final value for y will be value\something # # Normaly all you will need to modify is the first two properties, i.e. # wrapper.tomcat_home and wrapper.java_home. Most of the configuration # is derived from these two. # # # wrapper.tomcat_home should point to the location where you # installed tomcat. This is where you have your conf, webapps and lib # directories. # wrapper.tomcat_home=c:\tomcat\jakarta-tomcat-3.2.2 # # wrapper.java_home should point to your Java installation. Normally # you should have a bin and lib directories beneath it. # wrapper.java_home=c:\jdk1.3.1 # #-- ADVANCED MODE # Make sure that you read the how-to before making too many changes. #- # # # Defining where the service is going to put the standard # output of Tomcat. This is where System.out.println and # System.err.println goes to. # wrapper.stdout=$(wrapper.tomcat_home)\logs\jvm.stdout wrapper.stderr=$(wrapper.tomcat_home)\logs\jvm.stderr # # Additions to the path. put here directories where you store DLLs for # native methods etc. # wrapper.ld_path=d:\ wrapper.ld_path=c:\ # # Defining the classpath. All the rows that belongs to the class_path # property are concatenated to create the classpath for Tomcat. # # If you have additional locations that you would like to add to the # claspath you should add a new wrapper.class_path=location line. # wrapper.class_path=$(wrapper.tomcat_home)\classes wrapper.class_path=$(wrapper.tomcat_home)\lib\jaxp.jar wrapper.class_path=$(wrapper.tomcat_home)\lib\parser.jar wrapper.class_path=$(wrapper.tomcat_home)\lib\webserver.jar wrapper.class_path=$(wrapper.tomcat_home)\lib\servlet.jar wrapper.class_path=$(wrapper.tomcat_home)\lib\jasper.jar # # This is where Javac is located in JDK1.2.x # wrapper.class_path=$(wrapper.java_home)\lib\tools.jar # # and a tribute to JDK1.1.x # #wrapper.class_path=$(wrapper.java_home)\lib\classes.zip # # This is the Java interpreter used for running Tomcat # wrapper.javabin=$(wrapper.java_home)\bin\java.exe # # This is Tomcat's startup class (the class that contains Tomcat's # starting point. # wrapper.startup_class=org.apache.tomcat.startup.Tomcat # # This is the location where tomcat's server.xml configuration file # is located. # wrapper.server_xml=$(wrapper.tomcat_home)\conf\server.xml # # The NT service uses AJP12/AJP13 to shutdown Tomcat. The # wrapper.shutdown_port tells the service the identity of the port that # is used by AJP12/AJP13. # wrapper.shutdown_port=8007 # # Can either be ajp12 or ajp13 depending on your configuration. # # Default value is ajp12 # wrapper.shutdown_protocol=ajp12 # # This is the command line that is used to start Tomcat. You can *add* extra # parameters to it but you can not remove anything. # wrapper.cmd_line=$(wrapper.javabin) -classpath $(wrapper.class_path) $(wrapper.startup_class) -config $(wrapper.server_xml) -home $(wrapper.tomcat_home) #The uriworkermap.properties file # # Simple worker configuration file # # Mount the servlet context to the ajp12 worker /servlet/*=ajp12 # Mount the examples context to the ajp12 worker /examples/*=ajp12 # Advanced mount of the examples context # /examples/*.jsp=ajp12 # /examples/servlet/*=ajp12 *** Can I or should I use this file. I am going to need the uwi and loxt contexts #This is the uriworkermap.properties-auto file # # Auto configuration for the /loxt context starts. # # # The following line mounts all JSP file and the /servlet/ uri to tomcat # /loxt/servlet/*=$(default.worker) /loxt/*.jsp=$(default.worker) # # If you want tomcat to serve all the resources (including static) that # are part of the /loxt context, uncomment the following line # # /loxt/*=$(default.worker) ### # Auto configuration for the /loxt context ends. ###
RE: Tomcat and IIS revisited
-Original Message- From: Winer, Matthew [mailto:[EMAIL PROTECTED]] Sent: Monday, June 11, 2001 1:38 PM To: '[EMAIL PROTECTED]' Subject: RE: Tomcat and IIS revisited Here is a copy of my workers.properties and uriworkermap.properties files. I was told that this is where my problem lies. If somebody could take a quick look, maybe see if anything is wrong. Thanks # # $Header: /home/cvs/jakarta-tomcat/src/etc/Attic/wrapper.properties,v 1.2.2.1 2000/10/16 01:59:22 larryi Exp $ workers.properties, not wrapper.properties.
RE: Tomcat and IIS revisited
/jni_server.xml worker.inprocess.cmd_line=-home worker.inprocess.cmd_line=$(workers.tomcat_home) # # The JVM that we are about to use # # This is for Java2 # worker.inprocess.jvm_lib=$(workers.java_home)$(ps)jre$(ps)bin$(ps)classic$(p s)jvm.dll # # And this is for jdk1.1.X # #worker.inprocess.jvm_lib=$(workers.java_home)$(ps)bin$(ps)javai.dll # # # Setting the place for the stdout and stderr of tomcat # worker.inprocess.stdout=$(workers.tomcat_home)$(ps)inprocess.stdout worker.inprocess.stderr=$(workers.tomcat_home)$(ps)inprocess.stderr # # Setting the tomcat.home Java property # worker.inprocess.sysprops=tomcat.home=$(workers.tomcat_home) # # Java system properties # # worker.inprocess.sysprops=java.compiler=NONE # worker.inprocess.sysprops=myprop=mypropvalue # # Additional path components. # # worker.inprocess.ld_path=d:$(ps)SQLLIB$(ps)bin # -Original Message- From: Randy Layman [mailto:[EMAIL PROTECTED]] Sent: Monday, June 11, 2001 1:36 PM To: [EMAIL PROTECTED] Subject: RE: Tomcat and IIS revisited # $Header: /home/cvs/jakarta-tomcat/src/etc/Attic/wrapper.properties,v 1.2.2.1 2000/10/16 01:59:22 larryi Exp $ workers.properties, not wrapper.properties.
RE: Tomcat and IIS revisited
Now, my question is, have you modified Tomcat's server.xml file? This file indicates that it will try and use ajp12 to connect to localhost:8007 to find Tomcat. From your uriworkermap.properties file we know that this one should be used, and from the log files posted earlier we know that it is being used. So, the only thing that remains that could be wrong, is that Tomcat is not running AJP12 on port 8007. Randy -Original Message- From: Winer, Matthew [mailto:[EMAIL PROTECTED]] Sent: Monday, June 11, 2001 2:17 PM To: '[EMAIL PROTECTED]' Subject: RE: Tomcat and IIS revisited I appoligize here is the correct file # # $Header: /home/cvs/jakarta-tomcat/src/etc/Attic/workers.properties,v 1.3.2.2 2000/10/16 01:59:22 larryi Exp $ # $Revision: 1.3.2.2 $ # $Date: 2000/10/16 01:59:22 $ # # # workers.properties - # # This file provides jk derived plugins with with the needed information to # connect to the different tomcat workers. # # As a general note, the characters $( and ) are used internally to define # macros. Do not use them in your own configuration!!! # # Whenever you see a set of lines such as: # x=value # y=$(x)\something # # the final value for y will be value\something # # Normaly all you will need to modify is the first properties, i.e. # workers.tomcat_home, workers.java_home and ps. Most of the configuration # is derived from these. # # When you are done updating workers.tomcat_home, workers.java_home and ps # you should have 3 workers configured: # # - An ajp12 worker that connects to localhost:8007 # - An ajp13 worker that connects to localhost:8009 # - A jni inprocess worker. # - A load balancer worker # # However by default the plugins will only use the ajp12 worker. To have # the plugins use other workers you should modify the worker.list property. # # # # workers.tomcat_home should point to the location where you # installed tomcat. This is where you have your conf, webapps and lib # directories. # workers.tomcat_home=c:\tomcat\jakarta-tomcat-3.2.2 # # workers.java_home should point to your Java installation. Normally # you should have a bin and lib directories beneath it. # workers.java_home=c:\jdk1.3.1 # # You should configure your environment slash... ps=\ on NT and / on UNIX # and maybe something different elsewhere. # ps=\ # ps=/ # #-- ADVANCED MODE #- # # #-- DEFAULT worket list -- #- # # # The workers that your plugins should create and work with # worker.list=ajp12, ajp13 # #-- DEFAULT ajp12 WORKER DEFINITION -- #- # # # Defining a worker named ajp12 and of type ajp12 # Note that the name and the type do not have to match. # worker.ajp12.port=8007 worker.ajp12.host=localhost worker.ajp12.type=ajp12 # # Specifies the load balance factor when used with # a load balancing worker. # Note: # lbfactor must be 0 # Low lbfactor means less work done by the worker. worker.ajp12.lbfactor=1 # #-- 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=localhost worker.ajp13.type=ajp13 # # Specifies the load balance factor when used with # a load balancing worker. # Note: # lbfactor must be 0 # Low lbfactor means less work done by the worker. worker.ajp13.lbfactor=1 # # Specify the size of the open connection cache. #worker.ajp13.cachesize # #-- DEFAULT LOAD BALANCER WORKER DEFINITION -- #- # # # The loadbalancer (type lb) workers perform wighted round-robin # load balancing with sticky sessions. # Note: # If a worker dies, the load balancer will check its state #once in a while. Until then all work is redirected to peer #workers. worker.loadbalancer.type=lb worker.loadbalancer.balanced_workers=ajp12, ajp13 # #-- DEFAULT JNI WORKER DEFINITION- #- # # # Defining a worker named inprocess and of type jni # Note that the name and the type do not have to match. # worker.inprocess.type=jni # #-- CLASSPATH DEFINITION - #- # # # Additional class path components
RE: Tomcat and IIS revisited
Randy, Here is a clip from my server.xml file: !-- Apache AJP12 support. This is also used to shut down tomcat. -- Connector className=org.apache.tomcat.service.PoolTcpConnector Parameter name=handler value=org.apache.tomcat.service.connector.Ajp12ConnectionHandler/ Parameter name=port value=8007/ /Connector Thank You Matt Winer -Original Message- From: Randy Layman [mailto:[EMAIL PROTECTED]] Sent: Monday, June 11, 2001 1:55 PM To: [EMAIL PROTECTED] Subject: RE: Tomcat and IIS revisited Now, my question is, have you modified Tomcat's server.xml file? This file indicates that it will try and use ajp12 to connect to localhost:8007 to find Tomcat. From your uriworkermap.properties file we know that this one should be used, and from the log files posted earlier we know that it is being used. So, the only thing that remains that could be wrong, is that Tomcat is not running AJP12 on port 8007.
