Re: Port-per-webapp?
Hi Justin, Be sure, of course, that the files you're editing are indeed the ones being read -- for example, make sure that by removing /examples from uriworker.properties, IIS no longer serves the Tomcat examples. Great point... I removed the /examples from uriworkermap.properties, and it's still serving the http://localhost/examples!!! I checked my registry settings, and it's pointing to the exact location to the uriworkermap.properties: Registry for worker_mount_file: c:\\jakarta_tomcat\\appserver\\conf\uriworkermap.properties file location: C:\jakarta_tomcat\appserver\conf\uriworkermap.properties How could this be..? Just in case, I am pasting the worker.properties, uriworkermap.properties, and context from the server.xml. Thank you! ===uriworker.properties= # *** Begin uriworkermap.properties *** # Mount the Servlet context to the ajp13 worker /servlet/*=ajp13 # This webapp works /Analyzer6_Server/*=ajp13 #This works too/examples/*=ajp13 #This does NOT work /examples2/*=ajp13 /examples2/*.jsp=ajp13 == worker.properties== # Begin worker.properties ** worker.ajp13.type=ajp13 # # Specifies the load balance factor when used with # a load balancing worker. # Note: # lbfactor must be 0 # Low lbfactor means less work done by the worker. worker.ajp13.lbfactor=1 # # Specify the size of the open connection cache. #worker.ajp13.cachesize # #-- DEFAULT LOAD BALANCER WORKER DEFINITION -- #- # # # The loadbalancer (type lb) worker perform weighted round-robin # load balancing with sticky sessions. # Note: # If a worker dies, the load balancer will check its state #once in a while. Until then all work is redirected to peer #worker. worker.loadbalancer.type=lb worker.loadbalancer.balanced_workers=ajp13 # # worker.tomcat_home should point to the location where you # installed tomcat. This is where you have your conf, webapps and lib # directories. # worker.tomcat_home=c:\jakarta_tomcat\\appserver # # worker.java_home should point to your Java installation. Normally # you should have a bin and lib directories beneath it. # worker.java_home=c:\jakarta_tomcat\\jdk # # You should configure your environment slash... ps=\ on NT and / on UNIX # and maybe something 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=w2k3dfvm2 # End worker.properties ** == - Original Message - From: Justin Ruthenbeck [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 5:12 PM Subject: Re: Port-per-webapp? Tony, Can you include your full uriworker.properties and worker.properties files (inline in the email) for us to look at? Be sure, of course, that the files you're editing are indeed the ones being read -- for example, make sure that by removing /examples from uriworker.properties, IIS no longer serves the Tomcat examples. If there's something wrong with your config files, we should catch it pretty easily. justin At 01:20 PM 3/16/2004, you wrote: Hi Justin, Thank you very much for your input (and it's nice to know that my email is actually getting distributed). I've looked extensively at the documentation for days now, and I cannot figure it out. The problem I'm having is that the forwarding is selective. I have two webapps: webapp1 and examples that are correctly forwarded by IIS but not the ones that I deploy. In order to test it, I simply copied the examples to examples2 and added the following lines to uriworker.properties: /examples2/*=ajp13 where ajp13 is my worker name that is defined in the worker.properties file. I get 404-file not found error- when I try to access http://localhost/examples2/, but it works if I rename examples2 to examples. So it has to be some configuration error, but I just can' t seem to find out which configuration. Any suggestion helps, thank you! Tony - Original Message - From: Justin Ruthenbeck [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Tuesday, March
Re: Port-per-webapp?
Hi Justin, Thank you very much for your help, but I finally got it to work!! I reconfigured registry settings, cleared cache in Tomcat and IE, restarted all IIS and Tomcat services manually one by one, and it began working. I do have one final question though... In the registry setting tutorials, I see both c:\tomcat\blahblah and c:\\tomcat\\blahblah should we or should we not use escape character as in the second entry? Thanks again! Tony - Original Message - From: Tony Nakamura [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, March 17, 2004 8:16 AM Subject: Re: Port-per-webapp? Hi Justin, Be sure, of course, that the files you're editing are indeed the ones being read -- for example, make sure that by removing /examples from uriworker.properties, IIS no longer serves the Tomcat examples. Great point... I removed the /examples from uriworkermap.properties, and it's still serving the http://localhost/examples!!! I checked my registry settings, and it's pointing to the exact location to the uriworkermap.properties: Registry for worker_mount_file: c:\\jakarta_tomcat\\appserver\\conf\uriworkermap.properties file location: C:\jakarta_tomcat\appserver\conf\uriworkermap.properties How could this be..? Just in case, I am pasting the worker.properties, uriworkermap.properties, and context from the server.xml. Thank you! ===uriworker.properties= # *** Begin uriworkermap.properties *** # Mount the Servlet context to the ajp13 worker /servlet/*=ajp13 # This webapp works /Analyzer6_Server/*=ajp13 #This works too/examples/*=ajp13 #This does NOT work /examples2/*=ajp13 /examples2/*.jsp=ajp13 == worker.properties== # Begin worker.properties ** worker.ajp13.type=ajp13 # # Specifies the load balance factor when used with # a load balancing worker. # Note: # lbfactor must be 0 # Low lbfactor means less work done by the worker. worker.ajp13.lbfactor=1 # # Specify the size of the open connection cache. #worker.ajp13.cachesize # #-- DEFAULT LOAD BALANCER WORKER DEFINITION -- #- # # # The loadbalancer (type lb) worker perform weighted round-robin # load balancing with sticky sessions. # Note: # If a worker dies, the load balancer will check its state #once in a while. Until then all work is redirected to peer #worker. worker.loadbalancer.type=lb worker.loadbalancer.balanced_workers=ajp13 # # worker.tomcat_home should point to the location where you # installed tomcat. This is where you have your conf, webapps and lib # directories. # worker.tomcat_home=c:\jakarta_tomcat\\appserver # # worker.java_home should point to your Java installation. Normally # you should have a bin and lib directories beneath it. # worker.java_home=c:\jakarta_tomcat\\jdk # # You should configure your environment slash... ps=\ on NT and / on UNIX # and maybe something 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=w2k3dfvm2 # End worker.properties ** == - Original Message - From: Justin Ruthenbeck [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 5:12 PM Subject: Re: Port-per-webapp? Tony, Can you include your full uriworker.properties and worker.properties files (inline in the email) for us to look at? Be sure, of course, that the files you're editing are indeed the ones being read -- for example, make sure that by removing /examples from uriworker.properties, IIS no longer serves the Tomcat examples. If there's something wrong with your config files, we should catch it pretty easily. justin At 01:20 PM 3/16/2004, you wrote: Hi Justin, Thank you very much for your input (and it's nice to know that my email is actually getting distributed). I've looked extensively at the documentation for days now, and I cannot figure it out. The problem I'm having is that the forwarding is selective. I have two
Re: Port-per-webapp?
Tony, Glad to hear you got it working. The things you did (clear cache, restart services, reenter configuration) often solve problems like this. Doesn't provide for a clean explanation of what was wrong, but that's a different story. As for the escape chars, whether they should be escaped really depends on who's reading the value. I've never used the IIS plugin, so I have no idea what the behavior is -- an IIS user would have to chime in. justin At 07:24 AM 3/17/2004, you wrote: Hi Justin, Thank you very much for your help, but I finally got it to work!! I reconfigured registry settings, cleared cache in Tomcat and IE, restarted all IIS and Tomcat services manually one by one, and it began working. I do have one final question though... In the registry setting tutorials, I see both c:\tomcat\blahblah and c:\\tomcat\\blahblah should we or should we not use escape character as in the second entry? Thanks again! Tony - Original Message - From: Tony Nakamura [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, March 17, 2004 8:16 AM Subject: Re: Port-per-webapp? Hi Justin, Be sure, of course, that the files you're editing are indeed the ones being read -- for example, make sure that by removing /examples from uriworker.properties, IIS no longer serves the Tomcat examples. Great point... I removed the /examples from uriworkermap.properties, and it's still serving the http://localhost/examples!!! I checked my registry settings, and it's pointing to the exact location to the uriworkermap.properties: Registry for worker_mount_file: c:\\jakarta_tomcat\\appserver\\conf\uriworkermap.properties file location: C:\jakarta_tomcat\appserver\conf\uriworkermap.properties How could this be..? Just in case, I am pasting the worker.properties, uriworkermap.properties, and context from the server.xml. Thank you! ===uriworker.properties= # *** Begin uriworkermap.properties *** # Mount the Servlet context to the ajp13 worker /servlet/*=ajp13 # This webapp works /Analyzer6_Server/*=ajp13 #This works too/examples/*=ajp13 #This does NOT work /examples2/*=ajp13 /examples2/*.jsp=ajp13 == worker.properties== # Begin worker.properties ** worker.ajp13.type=ajp13 # # Specifies the load balance factor when used with # a load balancing worker. # Note: # lbfactor must be 0 # Low lbfactor means less work done by the worker. worker.ajp13.lbfactor=1 # # Specify the size of the open connection cache. #worker.ajp13.cachesize # #-- DEFAULT LOAD BALANCER WORKER DEFINITION -- #- # # # The loadbalancer (type lb) worker perform weighted round-robin # load balancing with sticky sessions. # Note: # If a worker dies, the load balancer will check its state #once in a while. Until then all work is redirected to peer #worker. worker.loadbalancer.type=lb worker.loadbalancer.balanced_workers=ajp13 # # worker.tomcat_home should point to the location where you # installed tomcat. This is where you have your conf, webapps and lib # directories. # worker.tomcat_home=c:\jakarta_tomcat\\appserver # # worker.java_home should point to your Java installation. Normally # you should have a bin and lib directories beneath it. # worker.java_home=c:\jakarta_tomcat\\jdk # # You should configure your environment slash... ps=\ on NT and / on UNIX # and maybe something 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=w2k3dfvm2 # End worker.properties ** == - Original Message - From: Justin Ruthenbeck [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 5:12 PM Subject: Re: Port-per-webapp? Tony, Can you include your full uriworker.properties and worker.properties files (inline in the email) for us to look at? Be sure, of course, that the files you're editing are indeed the ones being read -- for example, make sure that by removing /examples from
Re: Port-per-webapp?
Does anyone not know anything about this? I'm wondering whether this email is even reaching everyone.? - Original Message - From: "Tony Nakamura" [EMAIL PROTECTED] To: "Tomcat Users List" [EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 12:51 PM Subject: Port-per-webapp? Hi, I am encountering something interesting, and I really hope that someone will give me an insight. I'm working on an existing Tomcat 4.1.18 with some webapp deployed by previous developer. I am using IIS5 and isapi_filter, and it redirects fine to the previous webapp that was deployed. And here's the problem: previously deployed webapps are working fine when request was forwarded by IIS5, but my newly deployed webapps only work on port 8080 and outputs 404 - file not found error when I try to access it via IIS. Is there a port specification per-webapp? Thank you in advance!! Tony - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Port-per-webapp?
You have to configure the IIS plugin to path-forward URLs that have your webapp name in them. I don't use IIS, so I don't know specifically how it's done, but it's basically a way of telling IIS that anything matching my.server.com/myApp should go to the connector instead of being served by IIS. You can test to make sure that this is your problem by adding a file to IIS's doc root that matches the url that is supposed to go to Tomcat. If you get the page served by IIS, then your forwarding isn't working (alternately, the 404 page should indicate whether it's coming from IIS or Tomcat). Look at the connector docs -- I'm sure the specific files/steps are in there... Or perhaps an IIS user will respond here. justin At 01:04 PM 3/16/2004, you wrote: Does anyone not know anything about this? I'm wondering whether this email is even reaching everyone.? - Original Message - From: Tony Nakamura [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 12:51 PM Subject: Port-per-webapp? Hi, I am encountering something interesting, and I really hope that someone will give me an insight. I'm working on an existing Tomcat 4.1.18 with some webapp deployed by previous developer. I am using IIS5 and isapi_filter, and it redirects fine to the previous webapp that was deployed. And here's the problem: previously deployed webapps are working fine when request was forwarded by IIS5, but my newly deployed webapps only work on port 8080 and outputs 404 - file not found error when I try to access it via IIS. Is there a port specification per-webapp? Thank you in advance!! Tony - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Justin Ruthenbeck Software Engineer, NextEngine Inc. justinr - AT - nextengine DOT com Confidential. See: http://www.nextengine.com/confidentiality.php __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Port-per-webapp?
Hi Justin, Thank you very much for your input (and it's nice to know that my email is actually getting distributed). I've looked extensively at the documentation for days now, and I cannot figure it out. The problem I'm having is that the forwarding is "selective". I have two webapps: "webapp1 and examples" that are correctly forwarded by IIS but not the ones that I deploy. In order to test it, I simply copied the "examples" to "examples2" and added the following lines to uriworker.properties: /examples2/*=ajp13 where ajp13 is my worker name that is defined in the worker.properties file. I get 404-file not found error- when I try to access http://localhost/examples2/, but it works if I rename "examples2" to "examples". So it has to be some configuration error, but I just can' t seem to find out which configuration. Any suggestion helps, thank you! Tony - Original Message - From: "Justin Ruthenbeck" [EMAIL PROTECTED] To: "Tomcat Users List" [EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 3:10 PM Subject: Re: Port-per-webapp? You have to configure the IIS plugin to path-forward URLs that have your webapp name in them. I don't use IIS, so I don't know specifically how it's done, but it's basically a way of telling IIS that anything matching "my.server.com/myApp" should go to the connector instead of being served by IIS. You can test to make sure that this is your problem by adding a file to IIS's doc root that matches the url that is supposed to go to Tomcat. If you get the page served by IIS, then your forwarding isn't working (alternately, the 404 page should indicate whether it's coming from IIS or Tomcat). Look at the connector docs -- I'm sure the specific files/steps are in there... Or perhaps an IIS user will respond here. justin At 01:04 PM 3/16/2004, you wrote: Does anyone not know anything about this? I'm wondering whether this email is even reaching everyone.? - Original Message - From: "Tony Nakamura" [EMAIL PROTECTED] To: "Tomcat Users List" [EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 12:51 PM Subject: Port-per-webapp? Hi, I am encountering something interesting, and I really hope that someone will give me an insight. I'm working on an existing Tomcat 4.1.18 with some webapp deployed by previous developer. I am using IIS5 and isapi_filter, and it redirects fine to the previous webapp that was deployed. And here's the problem: previously deployed webapps are working fine when request was forwarded by IIS5, but my newly deployed webapps only work on port 8080 and outputs 404 - file not found error when I try to access it via IIS. Is there a port specification per-webapp? Thank you in advance!! Tony - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Justin Ruthenbeck Software Engineer, NextEngine Inc. justinr - AT - nextengine DOT com Confidential. See: http://www.nextengine.com/confidentiality.php __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Port-per-webapp?
Tony, Can you include your full uriworker.properties and worker.properties files (inline in the email) for us to look at? Be sure, of course, that the files you're editing are indeed the ones being read -- for example, make sure that by removing /examples from uriworker.properties, IIS no longer serves the Tomcat examples. If there's something wrong with your config files, we should catch it pretty easily. justin At 01:20 PM 3/16/2004, you wrote: Hi Justin, Thank you very much for your input (and it's nice to know that my email is actually getting distributed). I've looked extensively at the documentation for days now, and I cannot figure it out. The problem I'm having is that the forwarding is selective. I have two webapps: webapp1 and examples that are correctly forwarded by IIS but not the ones that I deploy. In order to test it, I simply copied the examples to examples2 and added the following lines to uriworker.properties: /examples2/*=ajp13 where ajp13 is my worker name that is defined in the worker.properties file. I get 404-file not found error- when I try to access http://localhost/examples2/, but it works if I rename examples2 to examples. So it has to be some configuration error, but I just can' t seem to find out which configuration. Any suggestion helps, thank you! Tony - Original Message - From: Justin Ruthenbeck [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 3:10 PM Subject: Re: Port-per-webapp? You have to configure the IIS plugin to path-forward URLs that have your webapp name in them. I don't use IIS, so I don't know specifically how it's done, but it's basically a way of telling IIS that anything matching my.server.com/myApp should go to the connector instead of being served by IIS. You can test to make sure that this is your problem by adding a file to IIS's doc root that matches the url that is supposed to go to Tomcat. If you get the page served by IIS, then your forwarding isn't working (alternately, the 404 page should indicate whether it's coming from IIS or Tomcat). Look at the connector docs -- I'm sure the specific files/steps are in there... Or perhaps an IIS user will respond here. justin At 01:04 PM 3/16/2004, you wrote: Does anyone not know anything about this? I'm wondering whether this email is even reaching everyone.? - Original Message - From: Tony Nakamura [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 12:51 PM Subject: Port-per-webapp? Hi, I am encountering something interesting, and I really hope that someone will give me an insight. I'm working on an existing Tomcat 4.1.18 with some webapp deployed by previous developer. I am using IIS5 and isapi_filter, and it redirects fine to the previous webapp that was deployed. And here's the problem: previously deployed webapps are working fine when request was forwarded by IIS5, but my newly deployed webapps only work on port 8080 and outputs 404 - file not found error when I try to access it via IIS. Is there a port specification per-webapp? Thank you in advance!! Tony - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Justin Ruthenbeck Software Engineer, NextEngine Inc. justinr - AT - nextengine DOT com Confidential. See: http://www.nextengine.com/confidentiality.php __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Justin Ruthenbeck Software Engineer, NextEngine Inc. justinr - AT - nextengine DOT com Confidential. See: http://www.nextengine.com/confidentiality.php __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
