Re: deploy application in new service in tomcat
On 07/02/2013 13:03, Anil Goyal -X (anigoyal - Aricent Technologies at Cisco) wrote: Hi, I am creating a new service in tomcat (7.0.20) with service name 'catalina_new' and appBase='webapps' by doing some changes in server.xml. I am keeping the appBase same as that for default service 'catalina' Why? A side effect will be that all apps in webapps are deployed to both services. This is because you've told Tomcat to do that. What do you gain by having the same appBase? I have several applications deployed under webapps. I want only a single application with context '/feeder' to be accesible through new service. Condition: I do not want to have a separate appBase for new service and deployed only the required app under this new appBase. Why not? Why have you invented a spurious and unnecessary condition like this? In short, do we have a context based filtering in tomcat so that tomcat incorporate request only from a specific context path and ignore all others No. p Thanks Anil -- [key:62590808] - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: deploy application in new service in tomcat
Hi Daniel, 'deployIgnore' option work for me. Can you please tell me how we can add multiple context path (context path for multiple applications) in this. -Original Message- From: Daniel Mikusa [mailto:dmik...@vmware.com] Sent: Thursday, February 07, 2013 6:43 PM To: Tomcat Users List Subject: Re: deploy application in new service in tomcat On Feb 7, 2013, at 8:03 AM, Anil Goyal -X (anigoyal - Aricent Technologies at Cisco) wrote: Hi, I am creating a new service in tomcat (7.0.20) This is really old, you should upgrade. with service name 'catalina_new' and appBase='webapps' by doing some changes in server.xml. I am keeping the appBase same as that for default service 'catalina' I have several applications deployed under webapps. I want only a single application with context '/feeder' to be accesible through new service. Condition: I do not want to have a separate appBase for new service and deployed only the required app under this new appBase. In short, do we have a context based filtering in tomcat so that tomcat incorporate request only from a specific context path and ignore all others Not sure I follow what you are trying to do, but it kinda sounds like you might want this? If not, please try to explain your use case a little more. deployIgnore A regular expression defining paths to ignore when autoDeploy and deployOnStartup are set. This allows you to keep your configuration in a version control system, for example, and not deploy a .svn or CVS folder that happens to be in the appBase. https://tomcat.apache.org/tomcat-7.0-doc/config/host.html#Common%20Attributes Dan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: deploy application in new service in tomcat
Hi. On this list, the convention is to not top post. Put your answers either in-line, in the text, or at the end. That is much easier for others to follow the conversation in a logical order. Anil Goyal -X (anigoyal - Aricent Technologies at Cisco) wrote: Thanks for the reply Andre. Let me explain you in detail. Let's suppose we have two applications App1.war and App2.war, deployed in webapps of tomcat. Now I want only App2 to listen additionally on a separate connector port(lets suppose 8181) along with port 8080 to which it is already listen. But I want App1 to listen only on port 8080 not on port 8181. So what I did, I create a new service in tomcat with name 'catalina_new' and appBase='webapps_new' and I add a connector port 8181 in this. Now I deploy my App2.war in webapps_new. So after restart the tomcat, I am able to make App2 to listen on port 8080 as well as port 8181(since App2.war is present in both webapps and webapps_new), and App1 is listen on only port 8080. Till now, everything was fine. Now I do not want to have a separate appBase for service 'catalina_new', means I want appBase='webapps' for service 'catalina_new' as well So by doing this change, my App1 also starts listen on port 8181 which is not required. So what can I do to make only App2 to listen on new port under new service with 'appBase=webapps' Hope you understand my query now! I do understand, approximately. But honestly, your way of thinking about this is different from mine, and I have some trouble following your idea. This may also be because my knowledge of the inner workings of Tomcat is limited, and I am not even sure that what you are currently doing is even supposed to work. In my understanding, what is listening on a given port is not a webapp, it is Tomcat. Tomcat accepts a connection on one of the ports that it is listening to, through one of the Connector elements of that Tomcat. (Until now, the webapps are not involved at all) Then Tomcat allocates this connection to a Thread, to process the HTTP request which has been written by the client to that connection. Then the Thread reads the HTTP request line sent by the client, and the HTTP request header lines. (Until now, the webapps are not involved at all) Then the Thread reads the Host: header line in that request, and determines to which Host this request is addressed. Then the Thread loads the appropriate configuration for that Host, before processing the request any further. (Until now, the webapps are still not involved at all) *Now* the Thread knows that for this Host, the active applications are located somewhere, and it knows to which context path each application should be answering. So *now* the Thread can call the appropriate webapp and give it the incoming request to process. So *now* one of the active webapps is involved. And at this point, it could be any webapp that is active within that Host. What I am trying to say, is that the selection of the port on which a request comes in is not controlled by the webapp, and cannot be. It is done much earlier in the cycle, and depends only on to which port the client connects and sends his request on. At the moment Tomcat accepts such a request, it does not know yet neither the Host, nor the webapp within the Host, which this client wants. And it cannot at that point decide to accept or refuse this request depending on which webapp it will ultimately go to, because it does not know that yet. I must confess that I do not really know if your idea of doing this by having 2 Service elements in Tomcat may or may not provide a way to overcome this. But to me, at this point, the idea seems a bit strange. To say the truth, I don't even know if your basic idea to restrict the access to a webapp based on which port the request comes in, makes really sense for what your basic issue is. But if that is really the issue, then I would do this on the base of a servlet filter configured for that webapp. You could probably use the urlrewrite filter (http://tuckey.org/urlrewrite/) for that, which would be much easier than your current setup. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: deploy application in new service in tomcat
Hi. On this list, the convention is to not top post. Put your answers either in-line, in the text, or at the end. That is much easier for others to follow the conversation in a logical order. Anil Goyal -X (anigoyal - Aricent Technologies at Cisco) wrote: Thanks for the reply Andre. Let me explain you in detail. Let's suppose we have two applications App1.war and App2.war, deployed in webapps of tomcat. Now I want only App2 to listen additionally on a separate connector port(lets suppose 8181) along with port 8080 to which it is already listen. But I want App1 to listen only on port 8080 not on port 8181. So what I did, I create a new service in tomcat with name 'catalina_new' and appBase='webapps_new' and I add a connector port 8181 in this. Now I deploy my App2.war in webapps_new. So after restart the tomcat, I am able to make App2 to listen on port 8080 as well as port 8181(since App2.war is present in both webapps and webapps_new), and App1 is listen on only port 8080. Till now, everything was fine. Now I do not want to have a separate appBase for service 'catalina_new', means I want appBase='webapps' for service 'catalina_new' as well So by doing this change, my App1 also starts listen on port 8181 which is not required. So what can I do to make only App2 to listen on new port under new service with 'appBase=webapps' Hope you understand my query now! I do understand, approximately. But honestly, your way of thinking about this is different from mine, and I have some trouble following your idea. This may also be because my knowledge of the inner workings of Tomcat is limited, and I am not even sure that what you are currently doing is even supposed to work. In my understanding, what is listening on a given port is not a webapp, it is Tomcat. Tomcat accepts a connection on one of the ports that it is listening to, through one of the Connector elements of that Tomcat. (Until now, the webapps are not involved at all) Then Tomcat allocates this connection to a Thread, to process the HTTP request which has been written by the client to that connection. Then the Thread reads the HTTP request line sent by the client, and the HTTP request header lines. (Until now, the webapps are not involved at all) Then the Thread reads the Host: header line in that request, and determines to which Host this request is addressed. Then the Thread loads the appropriate configuration for that Host, before processing the request any further. (Until now, the webapps are still not involved at all) *Now* the Thread knows that for this Host, the active applications are located somewhere, and it knows to which context path each application should be answering. So *now* the Thread can call the appropriate webapp and give it the incoming request to process. So *now* one of the active webapps is involved. And at this point, it could be any webapp that is active within that Host. What I am trying to say, is that the selection of the port on which a request comes in is not controlled by the webapp, and cannot be. It is done much earlier in the cycle, and depends only on to which port the client connects and sends his request on. At the moment Tomcat accepts such a request, it does not know yet neither the Host, nor the webapp within the Host, which this client wants. And it cannot at that point decide to accept or refuse this request depending on which webapp it will ultimately go to, because it does not know that yet. I must confess that I do not really know if your idea of doing this by having 2 Service elements in Tomcat may or may not provide a way to overcome this. But to me, at this point, the idea seems a bit strange. To say the truth, I don't even know if your basic idea to restrict the access to a webapp based on which port the request comes in, makes really sense for what your basic issue is. But if that is really the issue, then I would do this on the base of a servlet filter configured for that webapp. You could probably use the urlrewrite filter (http://tuckey.org/urlrewrite/) for that, which would be much easier than your current setup. The flow that you explain is absolutely fine and even I have the same flow in my mind as well. As you know there is one param 'deployIgnore' in Host Configuration. Can't we use that one for that. As I already explained you earlier that the case is regarding the two services in tomcat pointing to same appBase. If we add connector port lets suppose 8080 in service 1 and 8181 in service 2 then what will happen if I hit the url http://ip-address:8080/App1 http://ip-address:8080/App2 http://ip-address:8181/App1 http://ip-address:8181/App2 It will give 200 Ok response in all the cases . Now what if with port 8181, I want to access App1 only means now what I want is http://ip-address:8080/App1 should be 200OK http://ip-address:8080/App2 should be 200OK http://ip-address:8181/App1 should be 200OK
Re: deploy application in new service in tomcat
Anil Goyal -X (anigoyal - Aricent Technologies at Cisco) wrote: Hi. On this list, the convention is to not top post. Put your answers either in-line, in the text, or at the end. That is much easier for others to follow the conversation in a logical order. Anil Goyal -X (anigoyal - Aricent Technologies at Cisco) wrote: Thanks for the reply Andre. Let me explain you in detail. Let's suppose we have two applications App1.war and App2.war, deployed in webapps of tomcat. Now I want only App2 to listen additionally on a separate connector port(lets suppose 8181) along with port 8080 to which it is already listen. But I want App1 to listen only on port 8080 not on port 8181. So what I did, I create a new service in tomcat with name 'catalina_new' and appBase='webapps_new' and I add a connector port 8181 in this. Now I deploy my App2.war in webapps_new. So after restart the tomcat, I am able to make App2 to listen on port 8080 as well as port 8181(since App2.war is present in both webapps and webapps_new), and App1 is listen on only port 8080. Till now, everything was fine. Now I do not want to have a separate appBase for service 'catalina_new', means I want appBase='webapps' for service 'catalina_new' as well So by doing this change, my App1 also starts listen on port 8181 which is not required. So what can I do to make only App2 to listen on new port under new service with 'appBase=webapps' Hope you understand my query now! I do understand, approximately. But honestly, your way of thinking about this is different from mine, and I have some trouble following your idea. This may also be because my knowledge of the inner workings of Tomcat is limited, and I am not even sure that what you are currently doing is even supposed to work. In my understanding, what is listening on a given port is not a webapp, it is Tomcat. Tomcat accepts a connection on one of the ports that it is listening to, through one of the Connector elements of that Tomcat. (Until now, the webapps are not involved at all) Then Tomcat allocates this connection to a Thread, to process the HTTP request which has been written by the client to that connection. Then the Thread reads the HTTP request line sent by the client, and the HTTP request header lines. (Until now, the webapps are not involved at all) Then the Thread reads the Host: header line in that request, and determines to which Host this request is addressed. Then the Thread loads the appropriate configuration for that Host, before processing the request any further. (Until now, the webapps are still not involved at all) *Now* the Thread knows that for this Host, the active applications are located somewhere, and it knows to which context path each application should be answering. So *now* the Thread can call the appropriate webapp and give it the incoming request to process. So *now* one of the active webapps is involved. And at this point, it could be any webapp that is active within that Host. What I am trying to say, is that the selection of the port on which a request comes in is not controlled by the webapp, and cannot be. It is done much earlier in the cycle, and depends only on to which port the client connects and sends his request on. At the moment Tomcat accepts such a request, it does not know yet neither the Host, nor the webapp within the Host, which this client wants. And it cannot at that point decide to accept or refuse this request depending on which webapp it will ultimately go to, because it does not know that yet. I must confess that I do not really know if your idea of doing this by having 2 Service elements in Tomcat may or may not provide a way to overcome this. But to me, at this point, the idea seems a bit strange. To say the truth, I don't even know if your basic idea to restrict the access to a webapp based on which port the request comes in, makes really sense for what your basic issue is. But if that is really the issue, then I would do this on the base of a servlet filter configured for that webapp. You could probably use the urlrewrite filter (http://tuckey.org/urlrewrite/) for that, which would be much easier than your current setup. The flow that you explain is absolutely fine and even I have the same flow in my mind as well. As you know there is one param 'deployIgnore' in Host Configuration. Can't we use that one for that. As I already explained you earlier that the case is regarding the two services in tomcat pointing to same appBase. If we add connector port lets suppose 8080 in service 1 and 8181 in service 2 then what will happen if I hit the url http://ip-address:8080/App1 http://ip-address:8080/App2 http://ip-address:8181/App1 http://ip-address:8181/App2 It will give 200 Ok response in all the cases . Now what if with port 8181, I want to access App1 only means now what I want is http://ip-address:8080/App1 should be 200OK http://ip-address:8080/App2 should be 200OK
Re: deploy application in new service in tomcat
On Feb 8, 2013, at 5:23 AM, Anil Goyal -X (anigoyal - Aricent Technologies at Cisco) wrote: Hi Daniel, 'deployIgnore' option work for me. Can you please tell me how we can add multiple context path (context path for multiple applications) in this. It's a regular expression and whatever it matches will be ignored. If you need it to match multiple things, just adjust the regular expression so that it matches those things. Dan -Original Message- From: Daniel Mikusa [mailto:dmik...@vmware.com] Sent: Thursday, February 07, 2013 6:43 PM To: Tomcat Users List Subject: Re: deploy application in new service in tomcat On Feb 7, 2013, at 8:03 AM, Anil Goyal -X (anigoyal - Aricent Technologies at Cisco) wrote: Hi, I am creating a new service in tomcat (7.0.20) This is really old, you should upgrade. with service name 'catalina_new' and appBase='webapps' by doing some changes in server.xml. I am keeping the appBase same as that for default service 'catalina' I have several applications deployed under webapps. I want only a single application with context '/feeder' to be accesible through new service. Condition: I do not want to have a separate appBase for new service and deployed only the required app under this new appBase. In short, do we have a context based filtering in tomcat so that tomcat incorporate request only from a specific context path and ignore all others Not sure I follow what you are trying to do, but it kinda sounds like you might want this? If not, please try to explain your use case a little more. deployIgnore A regular expression defining paths to ignore when autoDeploy and deployOnStartup are set. This allows you to keep your configuration in a version control system, for example, and not deploy a .svn or CVS folder that happens to be in the appBase. https://tomcat.apache.org/tomcat-7.0-doc/config/host.html#Common%20Attributes Dan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: deploy application in new service in tomcat
On Feb 7, 2013, at 8:03 AM, Anil Goyal -X (anigoyal - Aricent Technologies at Cisco) wrote: Hi, I am creating a new service in tomcat (7.0.20) This is really old, you should upgrade. with service name 'catalina_new' and appBase='webapps' by doing some changes in server.xml. I am keeping the appBase same as that for default service 'catalina' I have several applications deployed under webapps. I want only a single application with context '/feeder' to be accesible through new service. Condition: I do not want to have a separate appBase for new service and deployed only the required app under this new appBase. In short, do we have a context based filtering in tomcat so that tomcat incorporate request only from a specific context path and ignore all others Not sure I follow what you are trying to do, but it kinda sounds like you might want this? If not, please try to explain your use case a little more. deployIgnore A regular expression defining paths to ignore when autoDeploy and deployOnStartup are set. This allows you to keep your configuration in a version control system, for example, and not deploy a .svn or CVS folder that happens to be in the appBase. https://tomcat.apache.org/tomcat-7.0-doc/config/host.html#Common%20Attributes Dan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: deploy application in new service in tomcat
Anil Goyal -X (anigoyal - Aricent Technologies at Cisco) wrote: Hi, I am creating a new service in tomcat (7.0.20) with service name 'catalina_new' and appBase='webapps' by doing some changes in server.xml. I am keeping the appBase same as that for default service 'catalina' I have several applications deployed under webapps. I want only a single application with context '/feeder' to be accesible through new service. Condition: I do not want to have a separate appBase for new service and deployed only the required app under this new appBase. In short, do we have a context based filtering in tomcat so that tomcat incorporate request only from a specific context path and ignore all others I am not sure if I understand your question correctly, but if I do then there is some kind of contradiction, or impossibility. In tomcat (and in the servlet spec in general) a context /is/ a web application. So if you have a tomcat with an application under CATALINA_BASE/webapps/feeder, and a client asks for the URL http://your_tomcat_host:port/feeder, it will get it. If you do not want this application to be accessible, don't deploy it in your host. Or use a separate Host to give it a separate hostname and/or port and a separate appBase. That's less complicated than running two separate Tomcat instances. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: deploy application in new service in tomcat
André Warnier wrote: Anil Goyal -X (anigoyal - Aricent Technologies at Cisco) wrote: Hi, I am creating a new service in tomcat (7.0.20) with service name 'catalina_new' and appBase='webapps' by doing some changes in server.xml. I am keeping the appBase same as that for default service 'catalina' I have several applications deployed under webapps. I want only a single application with context '/feeder' to be accesible through new service. Condition: I do not want to have a separate appBase for new service and deployed only the required app under this new appBase. In short, do we have a context based filtering in tomcat so that tomcat incorporate request only from a specific context path and ignore all others I am not sure if I understand your question correctly, but if I do then there is some kind of contradiction, or impossibility. In tomcat (and in the servlet spec in general) a context /is/ a web application. So if you have a tomcat with an application under CATALINA_BASE/webapps/feeder, and a client asks for the URL http://your_tomcat_host:port/feeder, it will get it. If you do not want this application to be accessible, don't deploy it in your host. Or use a separate Host to give it a separate hostname and/or port and a separate appBase. That's less complicated than running two separate Tomcat instances. I know that replying to my own posts is bad form, but I also missed something else above. Why would you want to create a new Service in Tomcat, just to deploy an additional application ? I'm not sure exactly what a new Service-level item brings here, but surely that's not the right level at which to do these things, or ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: deploy application in new service in tomcat
Thanks for the reply Andre. Let me explain you in detail. Let's suppose we have two applications App1.war and App2.war, deployed in webapps of tomcat. Now I want only App2 to listen additionally on a separate connector port(lets suppose 8181) along with port 8080 to which it is already listen. But I want App1 to listen only on port 8080 not on port 8181. So what I did, I create a new service in tomcat with name 'catalina_new' and appBase='webapps_new' and I add a connector port 8181 in this. Now I deploy my App2.war in webapps_new. So after restart the tomcat, I am able to make App2 to listen on port 8080 as well as port 8181(since App2.war is present in both webapps and webapps_new), and App1 is listen on only port 8080. Till now, everything was fine. Now I do not want to have a separate appBase for service 'catalina_new', means I want appBase='webapps' for service 'catalina_new' as well So by doing this change, my App1 also starts listen on port 8181 which is not required. So what can I do to make only App2 to listen on new port under new service with 'appBase=webapps' Hope you understand my query now! Thanks -Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: Thursday, February 07, 2013 7:35 PM To: Tomcat Users List Subject: Re: deploy application in new service in tomcat André Warnier wrote: Anil Goyal -X (anigoyal - Aricent Technologies at Cisco) wrote: Hi, I am creating a new service in tomcat (7.0.20) with service name 'catalina_new' and appBase='webapps' by doing some changes in server.xml. I am keeping the appBase same as that for default service 'catalina' I have several applications deployed under webapps. I want only a single application with context '/feeder' to be accesible through new service. Condition: I do not want to have a separate appBase for new service and deployed only the required app under this new appBase. In short, do we have a context based filtering in tomcat so that tomcat incorporate request only from a specific context path and ignore all others I am not sure if I understand your question correctly, but if I do then there is some kind of contradiction, or impossibility. In tomcat (and in the servlet spec in general) a context /is/ a web application. So if you have a tomcat with an application under CATALINA_BASE/webapps/feeder, and a client asks for the URL http://your_tomcat_host:port/feeder, it will get it. If you do not want this application to be accessible, don't deploy it in your host. Or use a separate Host to give it a separate hostname and/or port and a separate appBase. That's less complicated than running two separate Tomcat instances. I know that replying to my own posts is bad form, but I also missed something else above. Why would you want to create a new Service in Tomcat, just to deploy an additional application ? I'm not sure exactly what a new Service-level item brings here, but surely that's not the right level at which to do these things, or ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
