simple way to access application in multi instance envirnoment
hello, i'm running a server with multiple instance of tomcat each instance has some apps deployed accessed with host:port like myhost.com:/app1 myhost.com:/app2 myhost.com:/app3 is there any way to hide the port from users making app URL simpler with keeping multi instance ??? like this or any thing near app1.myhost.com app2.myhost.com app3.myhost.com thanks in advance
Re: simple way to access application in multi instance envirnoment
On Mar 9, 2014, at 8:08 AM, Ahmed Dalatony ahmed.dalat...@gmail.com wrote: hello, i'm running a server with multiple instance of tomcat each instance has some apps deployed accessed with host:port like myhost.com:/app1 myhost.com:/app2 myhost.com:/app3 is there any way to hide the port from users making app URL simpler with keeping multi instance ??? like this or any thing near app1.myhost.com app2.myhost.com app3.myhost.com Maybe virtual hosting? http://tomcat.apache.org/tomcat-7.0-doc/virtual-hosting-howto.html Dan thanks in advance - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: simple way to access application in multi instance envirnoment
On Sun, Mar 9, 2014 at 2:13 PM, Daniel Mikusa dmik...@gopivotal.com wrote: On Mar 9, 2014, at 8:08 AM, Ahmed Dalatony ahmed.dalat...@gmail.com wrote: hello, i'm running a server with multiple instance of tomcat each instance has some apps deployed accessed with host:port like myhost.com:/app1 myhost.com:/app2 myhost.com:/app3 is there any way to hide the port from users making app URL simpler with keeping multi instance ??? like this or any thing near app1.myhost.com app2.myhost.com app3.myhost.com Maybe virtual hosting? http://tomcat.apache.org/tomcat-7.0-doc/virtual-hosting-howto.html Dan thanks in advance hello, can you help me little more with example or simpler doc i'm new to tomcat config and i don't understand virtual host thank you
Re: simple way to access application in multi instance envirnoment
Ahmed, On Sun, Mar 9, 2014 at 10:14 AM, Ahmed Dalatony ahmed.dalat...@gmail.comwrote: hello, can you help me little more with example or simpler doc i'm new to tomcat config and i don't understand virtual host thank you Ultimately, if you don't want to show the port number to the end user, the serving process needs to bind to port 80. You mentioned few Tomcat processes, bound to ports , , , each serving few applications. So, here are few alternatives to achieve what you want: ALTERNATIVE_0 - Don't do anything. Each Tomcat instance runs on it's own port number. - Doesn't achieve what you want :) ALTERNATIVE_1 - Host all applications on a single Tomcat instance. Bind Tomcat to port 80 (if linux environment remember port 80 is privileged port, so you have to configure your Tomcat accordingly.) Register all domains to the same IP address. - You can use Tomcat virtual hosting to register different domains to specific applications. - Downside of this approach is that all applications are sharing the same JVM (Tomcat) instance. Spike in one application can bring all other applications down. ALTERNATIVE_2 - Have multiple network interfaces (IP addresses) available. Bind each Tomcat instance to one of the IP addresses. Register each domain to its own IP address. - This approach is better than ALTERNATIVE_1 when it comes to isolation of the processes in their own execution environments. - This approach utilizes many IP addresses, that are usually scarce and not easily justified for numerous applications. ALTERNATIVE_3 - Most common approach I've seen around. - Similar to approach you are currently taking (ALTERNATIVE_0), with a help of external web server that will act as a (reverse) proxy. Typically, I would use Apache Httpd server, but you can use other web servers, e.g. IIS on Windows platform, or nginx. - In this case Apache (or other webserver) would bind to port 80, and based on the requested URL (or host) would point to a specific application (hosted on specific Tomcat on certain port, e.g. , , , etc...) - If you would like to achieve that different hosts point to different applications, register all domains with the same IP address in DNS, and configure virtual hosting on the webserver. Thus, if you run multiple instances of Tomcat - alone, virtual hosting will not help you , since only one process can bind to a single IP address to one port (e.g. port 80). So, either put everything to the same Tomcat (yuck), or bind each tomcat to port 80 on separate IP addresses, or have an external web server routing requests to your multiple Tomcat instances. My preference is the later approach. Here are some questions you want to answer before choosing the alternative: - What is the environment that you run on (windows, linux, etc.)? - What are you requirements? - How many applications do you have? How many instances do you plan to run, on the same machine, on the entire platform? - What are the application usage patterns? (how many users do you plan to serve, spikes, etc..) - What are the service level agreements you have with your customers? - etc... Configuring webserver to route requests to Tomcat instances is pretty straight forward, and you have a choice of HTTP or AJP protocols and depends on the choice of your webserver (Apache HTTPD, IIS, nginx, etc.) Hope that helps. Cheers! Neven
Re: simple way to access application in multi instance envirnoment
On Sun, Mar 9, 2014 at 5:05 PM, Neven Cvetkovic neven.cvetko...@gmail.comwrote: Ahmed, On Sun, Mar 9, 2014 at 10:14 AM, Ahmed Dalatony ahmed.dalat...@gmail.com wrote: hello, can you help me little more with example or simpler doc i'm new to tomcat config and i don't understand virtual host thank you Ultimately, if you don't want to show the port number to the end user, the serving process needs to bind to port 80. You mentioned few Tomcat processes, bound to ports , , , each serving few applications. So, here are few alternatives to achieve what you want: ALTERNATIVE_0 - Don't do anything. Each Tomcat instance runs on it's own port number. - Doesn't achieve what you want :) ALTERNATIVE_1 - Host all applications on a single Tomcat instance. Bind Tomcat to port 80 (if linux environment remember port 80 is privileged port, so you have to configure your Tomcat accordingly.) Register all domains to the same IP address. - You can use Tomcat virtual hosting to register different domains to specific applications. - Downside of this approach is that all applications are sharing the same JVM (Tomcat) instance. Spike in one application can bring all other applications down. ALTERNATIVE_2 - Have multiple network interfaces (IP addresses) available. Bind each Tomcat instance to one of the IP addresses. Register each domain to its own IP address. - This approach is better than ALTERNATIVE_1 when it comes to isolation of the processes in their own execution environments. - This approach utilizes many IP addresses, that are usually scarce and not easily justified for numerous applications. ALTERNATIVE_3 - Most common approach I've seen around. - Similar to approach you are currently taking (ALTERNATIVE_0), with a help of external web server that will act as a (reverse) proxy. Typically, I would use Apache Httpd server, but you can use other web servers, e.g. IIS on Windows platform, or nginx. - In this case Apache (or other webserver) would bind to port 80, and based on the requested URL (or host) would point to a specific application (hosted on specific Tomcat on certain port, e.g. , , , etc...) - If you would like to achieve that different hosts point to different applications, register all domains with the same IP address in DNS, and configure virtual hosting on the webserver. Thus, if you run multiple instances of Tomcat - alone, virtual hosting will not help you , since only one process can bind to a single IP address to one port (e.g. port 80). So, either put everything to the same Tomcat (yuck), or bind each tomcat to port 80 on separate IP addresses, or have an external web server routing requests to your multiple Tomcat instances. My preference is the later approach. Here are some questions you want to answer before choosing the alternative: - What is the environment that you run on (windows, linux, etc.)? - What are you requirements? - How many applications do you have? How many instances do you plan to run, on the same machine, on the entire platform? - What are the application usage patterns? (how many users do you plan to serve, spikes, etc..) - What are the service level agreements you have with your customers? - etc... Configuring webserver to route requests to Tomcat instances is pretty straight forward, and you have a choice of HTTP or AJP protocols and depends on the choice of your webserver (Apache HTTPD, IIS, nginx, etc.) Hope that helps. Cheers! Neven thanks Dan Neven i think 3rd alternative is my way to go i'll start searching about it and see what i get
Stable version
What is the latest stable version of tomcat? The website shows 8.03 is beta. Thanks Visit us on the Web at mesirowfinancial.com This communication may contain privileged and/or confidential information. It is intended solely for the use of the addressee. If you are not the intended recipient, you are strictly prohibited from disclosing, copying, distributing or using any of this information. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Confidential, proprietary or time-sensitive communications should not be transmitted via the Internet, as there can be no assurance of actual or timely delivery, receipt and/or confidentiality. This is not an offer, or solicitation of any offer to buy or sell any security, investment or other product. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Stable version
From: Gallegos, Alfonso [mailto:agalle...@mesirowfinancial.com] Subject: Stable version What is the latest stable version of tomcat? The website shows 8.03 is beta. What does the chart at http://tomcat.apache.org/whichversion.html say? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: The Service Component
2014-03-07 21:21 GMT+04:00 André Warnier a...@ice-sa.com: Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Leo, On 3/7/14, 10:44 AM, Leo Donahue wrote: Who uses more than one Service in their server.xml and why? I get that you can have multiple Connectors if you have multiple Service components but why use multiple connectors? You can already have multiple Connectors per Service but the difference is that all Connectors in Service can access all web applications in that Service. Are there any docs on the use cases for these features? Let's say that you wanted to deploy a non-secure webapp (/open) and a secure webapp (/secure). And let's say that you were terribly paranoid about proper setup: you want to make sure that nobody can access your /secure webapp without going through HTTPS. If you were to simply do this: Service Connector port=80 /!-- let's just be brief -- Connector port=443 / Host appBase=webapps / /Service ... then anyone could access either web application via http:// and https://. (Of course, you'd set CONFIDENTIAL in your web.xml, but remember, we're being paranoid, here). Instead, you can do this: Service Connector port=80 /!-- let's just be brief -- Host appBase=insecure-webapps / /Service Service Connector port=443 / Host appBase=secure-webapps / /Service This way, anyone requesting http:///secure would get a 404. I'm sure you could come up with a real-world use-case for the above, because it's obviously not a very good example I've laid out there. Perhaps a better use-case might be something like a server connected to several VPNs where services need to be separated by port number for isolation. (I'm not sure why you'd isolate the port numbers in that case and not also isolate the JVMs, but it's just a thought). I would be almost ready to bet that nobody has ever tried 2 Service's. It almost sounds like 2 separate Tomcat instances, except that they share the same JVM and the same TOMCAT_BASE, hence the same configuration files (of course), which makes it difficult to think of a real use case, as compared to 2 separate (JVM + Tomcat) instances running off the same codebase. For example, the Manager web application is implemented so that it manages the current Host only, but that is only an implementer's decision. With JMX access you can manage the whole Tomcat. There might be alternative management applications out there that allow to manage the whole Tomcat, while being run in a different Service / Host. My guess would be : when designing Tomcat, it came to pass that somewhere in the logic, Connector's and Engine were related things, but that there was no clear way to design it so that one would be a child of the other or vice-versa. So they just created a Service on top of both, and made them siblings. It may just be so as to make it easier to start the Engine, before starting the corresponding Connector's. Or to run them separately and asynchronously. It is a good question though. I wonder why nobody ever asked on this list before (in my memory). Also, (and also in my memory) I could swear that at some point, there was a document available on the Tomcat website, which gave some overview of the overall Tomcat design. But I can't seem to find that anymore. Docs - Architecture ? http://tomcat.apache.org/tomcat-7.0-doc/architecture/index.html Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Stable version
I'm not sure but they sure make things confusing. As far as I read the download page should show the latest stable version which shows 8.03. The page that explains whichversion says 8.03 is beta. - Original Message - From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: Sunday, March 09, 2014 10:35 AM To: Tomcat Users List users@tomcat.apache.org Subject: RE: Stable version From: Gallegos, Alfonso [mailto:agalle...@mesirowfinancial.com] Subject: Stable version What is the latest stable version of tomcat? The website shows 8.03 is beta. What does the chart at http://tomcat.apache.org/whichversion.html say? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org Visit us on the Web at mesirowfinancial.com This communication may contain privileged and/or confidential information. It is intended solely for the use of the addressee. If you are not the intended recipient, you are strictly prohibited from disclosing, copying, distributing or using any of this information. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Confidential, proprietary or time-sensitive communications should not be transmitted via the Internet, as there can be no assurance of actual or timely delivery, receipt and/or confidentiality. This is not an offer, or solicitation of any offer to buy or sell any security, investment or other product. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Stable version
From: Gallegos, Alfonso [mailto:agalle...@mesirowfinancial.com] Subject: Re: Stable version I'm not sure but they sure make things confusing. As far as I read the download page should show the latest stable version which shows 8.03. No, the download pages show all available current versions. 8.0.3 (not 8.03) is there for people who want to participate in the beta testing. The page that explains whichversion says 8.03 is beta. Which it is. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Stable version
You're correct that it doesn't explicitly say which is the latest stable version, but the description says that 8.x is beta, which would imply that the latest 7.0.x would be the latest stable version, which it is. D On 3/9/2014 11:46 AM, Gallegos, Alfonso wrote: I'm not sure but they sure make things confusing. As far as I read the download page should show the latest stable version which shows 8.03. The page that explains whichversion says 8.03 is beta. - Original Message - From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: Sunday, March 09, 2014 10:35 AM To: Tomcat Users List users@tomcat.apache.org Subject: RE: Stable version From: Gallegos, Alfonso [mailto:agalle...@mesirowfinancial.com] Subject: Stable version What is the latest stable version of tomcat? The website shows 8.03 is beta. What does the chart at http://tomcat.apache.org/whichversion.html say? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org Visit us on the Web at mesirowfinancial.com This communication may contain privileged and/or confidential information. It is intended solely for the use of the addressee. If you are not the intended recipient, you are strictly prohibited from disclosing, copying, distributing or using any of this information. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Confidential, proprietary or time-sensitive communications should not be transmitted via the Internet, as there can be no assurance of actual or timely delivery, receipt and/or confidentiality. This is not an offer, or solicitation of any offer to buy or sell any security, investment or other product. - 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: NIO connector - connections and threads
2014-03-09 2:08 GMT+04:00 John Smith tomcat.ran...@gmail.com: Sorry, forgot: Tomcat 7.0.42 On Fri, Mar 7, 2014 at 3:59 PM, John Smith tomcat.ran...@gmail.com wrote: The NIO connector has two attributes from the standard HTTP Connector implementation, maxConnections and maxThreads with defaults of 1 and 200, respectively. Can anyone shine some light on how these work together? If I'm allowing up to 1 connections, would that mean I only have 200 threads to process through them? It would seem to be a disparity between the defaults. If I'm expecting maxConnection numbers in the area of ~2000 at any given time, wouldn't I want to bump up my maxThreads closer to match that? Production environment is: DELL PowerEdge R720 Single Socket Six Core Intel Xeon E5-2640 2.5GHz 32 GB RAM RHEL 6 Roughly speaking, The new APIs in java NIO and in Apache APR (and ultimately in underlying OS) allow to test whether there are incoming data on a network socket without actually reading it. A thread is needed when Tomcat calls your code in a web application to process a request. When request processing ends and control is returned to Tomcat, the request processing thread is decoupled from connection and is used to process other connections. With keep-alive feature in HTTP/1.1 protocol there may be several HTTP requests on the same HTTP connection, maxConnections = how many open HTTP connection can be hold by Tomcat maxThreads = how many requests are being actively processed at the same time. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: simple way to access application in multi instance envirnoment
On Sun, Mar 9, 2014 at 11:29 AM, Ahmed Dalatony ahmed.dalat...@gmail.comwrote: On Sun, Mar 9, 2014 at 5:05 PM, Neven Cvetkovic neven.cvetko...@gmail.comwrote: Ahmed, On Sun, Mar 9, 2014 at 10:14 AM, Ahmed Dalatony ahmed.dalat...@gmail.com wrote: hello, can you help me little more with example or simpler doc i'm new to tomcat config and i don't understand virtual host thank you What environment do you use? e.g. Windows, Linux, etc. If Linux, what flavour of Linux? e.g. RHEL (CentOS, Fedora), Ubuntu, etc. What webserver would you like to use? e.g. Apache HTTPD, IIS, nginx, etc. They all have different ways to configure your setup. - The easier one to setup is to use mod_proxy, check examples here: https://tomcat.apache.org/tomcat-7.0-doc/proxy-howto.html - More common is to use AJP protocol and mod_jk in Apache, check examples here: http://tomcat.apache.org/connectors-doc/generic_howto/quick.html http://tomcat.apache.org/connectors-doc/reference/apache.html Hope that helps. n.
Re: simple way to access application in multi instance envirnoment
On Sun, Mar 9, 2014 at 7:48 PM, Neven Cvetkovic neven.cvetko...@gmail.comwrote: On Sun, Mar 9, 2014 at 11:29 AM, Ahmed Dalatony ahmed.dalat...@gmail.com wrote: On Sun, Mar 9, 2014 at 5:05 PM, Neven Cvetkovic neven.cvetko...@gmail.comwrote: Ahmed, On Sun, Mar 9, 2014 at 10:14 AM, Ahmed Dalatony ahmed.dalat...@gmail.com wrote: hello, can you help me little more with example or simpler doc i'm new to tomcat config and i don't understand virtual host thank you What environment do you use? e.g. Windows, Linux, etc. If Linux, what flavour of Linux? e.g. RHEL (CentOS, Fedora), Ubuntu, etc. What webserver would you like to use? e.g. Apache HTTPD, IIS, nginx, etc. They all have different ways to configure your setup. - The easier one to setup is to use mod_proxy, check examples here: https://tomcat.apache.org/tomcat-7.0-doc/proxy-howto.html - More common is to use AJP protocol and mod_jk in Apache, check examples here: http://tomcat.apache.org/connectors-doc/generic_howto/quick.html http://tomcat.apache.org/connectors-doc/reference/apache.html Hope that helps. n. hello, I'm using win server 2008 running a combination of tomcat 6, tomcat 7, oc4j 10g on different ports the resources you supplied are very handy but they explain accessing http://www.myhost.com:/App1 from http://www.myhost.com/App1 is it applicable to be accessed from URL like this http://App1.myhost.com thanks,
Re: simple way to access application in multi instance envirnoment
Ahmed, On Sun, Mar 9, 2014 at 3:15 PM, Ahmed Dalatony ahmed.dalat...@gmail.comwrote: I'm using win server 2008 running a combination of tomcat 6, tomcat 7, oc4j 10g on different ports the resources you supplied are very handy but they explain accessing http://www.myhost.com:/App1 from http://www.myhost.com/App1 is it applicable to be accessed from URL like this http://App1.myhost.com Nice! That's exactly a usecase when we want to use a webserver to aggregate the applications under the same domain. So, start first with that setup, e.g. http://www.myhost.com/App1 -- tomcat6_instance1_app1 http://www.myhost.com/App2 -- tomcat6_instance1_app2 http://www.myhost.com/App3 -- tomcat6_instance2_app3 http://www.myhost.com/App4 -- tomcat7_instance1_app4 http://www.myhost.com/App5 -- oc4j_instance1_app5 ... I am mostly familiar with Apache Httpd server (or just simply Apache web server), so I would recommend that solution. However, you could achieve similar setup with IIS as well. Here's Apache configuration example: http://httpd.apache.org/docs/2.2/vhosts/examples.html You can download this version of Apache: http://httpd.apache.org/download.cgi -- Binaries -- win32 e.g. (one of the mirrors gets selected by the download.cgi) http://apache.mirrors.spacedump.net//httpd/binaries/win32/httpd-2.2.25-win32-x86-openssl-0.9.8y.msi Or alternatively, that OC4J might have an instance of OHS already running (which is a version of Apache Httpd server). I don't know which OC4J 10g version you use, probably 10.1.2.0.2 - which had OHS based on Apache 1.3.x. - you might want to upgrade that to the latest Apache or IIS. Cheers! n.
Re: Tomcat7w.exe
On Fri, Mar 7, 2014 at 12:43 PM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: Actually, i hate clicking on things... I use Windows keyboard shortcuts as much as possible. Even when you run the following command, you still get a GUI. Tomcat7w //ES/Tomcat7 Do you Ctrl + Tab your way through that dialog? Plus, I don't know what this is supposed to edit, but it doesn't change the values in the Tomcat7w.exe dialog: Tomcat7 //ES//Tomcat7 --Startup=Auto (or Automatic) Running that command still shows Manual in the Startup type on the General tab.
Re: Difference between process kill and shutdown
kill -15 On Sun, Mar 2, 2014 at 4:42 AM, Mark Thomas ma...@apache.org wrote: On 01/03/2014 12:11, Akash Jain wrote: On our linux boxes, we have multiple users who run tomcat. Currently we are using process kill commands to kill the respective user's tomcat , instead of using shutdown.sh Which signal are you sending to shutdown the process? Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Difference between process kill and shutdown
On 09/03/2014 20:41, Akash Jain wrote: kill -15 On Sun, Mar 2, 2014 at 4:42 AM, Mark Thomas ma...@apache.org wrote: On 01/03/2014 12:11, Akash Jain wrote: On our linux boxes, we have multiple users who run tomcat. Currently we are using process kill commands to kill the respective user's tomcat , instead of using shutdown.sh Which signal are you sending to shutdown the process? In which case you should be fine. Using kill -15 has the same result as using the shutdown script. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat and Spring Framework
On 3/7/2014 4:45 PM, Leo Donahue wrote: On Fri, Mar 7, 2014 at 3:41 PM, Konstantin Kolinko knst.koli...@gmail.comwrote: 2014-03-08 2:30 GMT+04:00 Leo Donahue donahu...@gmail.com: Any Spring developers on the list? http://docs.spring.io/spring/docs/4.0.2.RELEASE/spring-framework-reference/htmlsingle/#overview-usagescenarios A link to htmlsingle page?? That takes a while to load. Yes, sorry. That is the link to the reference on the quick start page here: http://projects.spring.io/spring-framework/#quick-start Here is a quicker one to that chapter 2.3: http://docs.spring.io/spring/docs/4.0.2.RELEASE/spring-framework-reference/html/overview.html#overview-usagescenarios Is that saying that you can use a regular Tomcat for all of that? full-fledged enterprise applications on Tomcat? Yes. Why not? I'm good with that, just asking. New to Spring. Hi, Leo- I've used Spring MVC with Tomcat without any problems. -Terence Bandoian P.S. My apologies for the private e-mail. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: simple way to access application in multi instance envirnoment
On 3/9/2014 10:05 AM, Neven Cvetkovic wrote: Ahmed, On Sun, Mar 9, 2014 at 10:14 AM, Ahmed Dalatony ahmed.dalat...@gmail.comwrote: hello, can you help me little more with example or simpler doc i'm new to tomcat config and i don't understand virtual host thank you Ultimately, if you don't want to show the port number to the end user, the serving process needs to bind to port 80. You mentioned few Tomcat processes, bound to ports , , , each serving few applications. So, here are few alternatives to achieve what you want: ALTERNATIVE_0 - Don't do anything. Each Tomcat instance runs on it's own port number. - Doesn't achieve what you want :) ALTERNATIVE_1 - Host all applications on a single Tomcat instance. Bind Tomcat to port 80 (if linux environment remember port 80 is privileged port, so you have to configure your Tomcat accordingly.) Register all domains to the same IP address. - You can use Tomcat virtual hosting to register different domains to specific applications. - Downside of this approach is that all applications are sharing the same JVM (Tomcat) instance. Spike in one application can bring all other applications down. ALTERNATIVE_2 - Have multiple network interfaces (IP addresses) available. Bind each Tomcat instance to one of the IP addresses. Register each domain to its own IP address. - This approach is better than ALTERNATIVE_1 when it comes to isolation of the processes in their own execution environments. - This approach utilizes many IP addresses, that are usually scarce and not easily justified for numerous applications. ALTERNATIVE_3 - Most common approach I've seen around. - Similar to approach you are currently taking (ALTERNATIVE_0), with a help of external web server that will act as a (reverse) proxy. Typically, I would use Apache Httpd server, but you can use other web servers, e.g. IIS on Windows platform, or nginx. - In this case Apache (or other webserver) would bind to port 80, and based on the requested URL (or host) would point to a specific application (hosted on specific Tomcat on certain port, e.g. , , , etc...) - If you would like to achieve that different hosts point to different applications, register all domains with the same IP address in DNS, and configure virtual hosting on the webserver. Thus, if you run multiple instances of Tomcat - alone, virtual hosting will not help you , since only one process can bind to a single IP address to one port (e.g. port 80). So, either put everything to the same Tomcat (yuck), or bind each tomcat to port 80 on separate IP addresses, or have an external web server routing requests to your multiple Tomcat instances. My preference is the later approach. Here are some questions you want to answer before choosing the alternative: - What is the environment that you run on (windows, linux, etc.)? - What are you requirements? - How many applications do you have? How many instances do you plan to run, on the same machine, on the entire platform? - What are the application usage patterns? (how many users do you plan to serve, spikes, etc..) - What are the service level agreements you have with your customers? - etc... Configuring webserver to route requests to Tomcat instances is pretty straight forward, and you have a choice of HTTP or AJP protocols and depends on the choice of your webserver (Apache HTTPD, IIS, nginx, etc.) Hope that helps. Cheers! Neven Nice explanation. -Terence Bandoian - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat and Spring Framework
On Sun, Mar 9, 2014 at 6:36 PM, Terence M. Bandoian tere...@tmbsw.comwrote: On 3/7/2014 4:45 PM, Leo Donahue wrote: On Fri, Mar 7, 2014 at 3:41 PM, Konstantin Kolinko knst.koli...@gmail.comwrote: 2014-03-08 2:30 GMT+04:00 Leo Donahue donahu...@gmail.com: Any Spring developers on the list? Leo, I've used Spring quite a lot, and Tomcat is very popular choice of platform for Spring developers. Is that saying that you can use a regular Tomcat for all of that? full-fledged enterprise applications on Tomcat? Yes. Why not? I'm good with that, just asking. New to Spring. Hi, Leo- I've used Spring MVC with Tomcat without any problems. Same here. I've used Spring and Tomcat on many projects, with a great success. Spring Framework is a very comprehensive framework that gives you a lot of functionality that traditional JEE appservers (WebSphere, Weblogic, JBoss, etc..) provide and that is not available in pure Tomcat. The Spring project kinda started out of frustration with current state of affairs in the J(2)EE appserver market and EJB specification and implementation. The idea was to offer a viable platform (framework) to write J(2)EE applications without a need for full-fledged (and expensive!) J(2)EE appserver and EJB container (see two Rod Johnson's books below [1] and [2] for more details). Spring Framework and Tomcat shared their mutual love for each other over last 10 years, and was probably one of the reasons why Spring and Tomcat became very popular choice of development environment for many Java developers. Spring naturally evolved to include many new projects, not just the Spring Framework [3]. They even created their own container based on Tomcat server, called tcServer [4] and [5] - later acquired by VMWare. So, yes - there is probably a lot of developers on this list very familiar with Spring framework :))) Hopefully, that answers your question. Cheers! Neven Links: [1] http://www.amazon.com/Expert-One---One-Development-without/dp/0764558315 [2] http://www.amazon.com/Expert-One---One-Design-Development/dp/0764543857 [3] http://spring.io/projects [4] http://www.vmware.com/products/vfabric-tcserver [5] http://static.springsource.com/projects/tc-server/6.0/getstart/cgsdiffs.html
Re: The Service Component
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, On 3/8/14, 6:30 AM, André Warnier wrote: Leon Rosenberg wrote: Hello Leo, On Fri, Mar 7, 2014 at 6:49 PM, Leo Donahue donahu...@gmail.com wrote: On Fri, Mar 7, 2014 at 9:01 AM, Leon Rosenberg rosenberg.l...@gmail.com wrote: Hello, I do use multiple connectors but one service. Multiple connectors to separate user traffic from admin/management traffic. For example if due to overload no threads are available to server http request on the 'main' connector, I still can look into the app, to see what is going on, over my administrative connector. Leon You are just changing the port number then in your administrative connector, in the same Service element? yes: for example Connector executor=tomcatThreadPool port=8080 protocol=HTTP/1.1 connectionTimeout=2 / Connector executor=tomcatThreadPool port=8180 protocol=HTTP/1.1 connectionTimeout=2 / I would then point the front loadbalancer to 8080 and keep 8180 accessible from the administration network only. With the above configuration, both these Connectors share the same pool of threads. If the Connector on port 8080 exhausts the available threads, you will not be able to connect using the Connector on port 8180 (ok, you will be able to connect, but not to do anything). For even more resilience, I would give that port 8180 Connector its own pool of (e.g.) 3 threads, not shared with the Executor. +1 Also, there's only one Service, which was the original subject. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTHQ3pAAoJEBzwKT+lPKRYhT4QALLwYJv/xcBnWrDHfaeIg/M6 q4LhS5PgMGwTYW/nuq8hCOnnjFYIyTlmQMbAPiC8F4CbLAn6VeGWAG/blHsrfA1l B1iml8qEgZ8cHVlTHKa/GFci2oMpNomv1yNcc0jSYQDvOfXLeUoz5QAZWy7mGAXu Q77CEJshxwR9Ixpvhu8lV6yUs2MRBZTU4QgDV10ZSMWLy9NyLWk4DBg4aRqvl5wg 7Z9WLZiHWWA8kpIugHspmNScWHS+jcol/lOQlrwdiipm3JLUlLywpSxEJ4lM1LYz ypwiQCmHPVFuBXtowGbKLdAet4Hx/uPXsO1Z7579d0gsl5ZYnmGO/ZwqkH7Tyhu6 gsFwM00FjgVKAodcY179ivJ8VETGMkvhgJB4YcRSzX+AeZG5JXaFca9SjpnKTn/5 WdSZKGzsyEYIgNOXlvbeDMRTLrJcsIMwXFcGlHVZTWJs4u1rSt4R3r06lqxwJ/1R TT3PzEaPP7G/oK0nCfoT2sDUdAUB379zZSW9PqCK0DNxr9TQd8ZpNcZ1E32R/MoF vAVno8c6jzKJNK3Auc1ZdypeDdRDjsUS/viBG2AKKlrnJZhZXGvW3qwBMLEXQD8J WZI0NDL32SPs035VRt4XNeCN89qk3mHfTDgysxEbBazAacffSFu5MvZfVjcIaN3p pg7Eip/bLjYnbNza5LbF =Fq0A -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 7 Session Persistence disable not working as expected
As documented in https://tomcat.apache.org/tomcat-5.5-doc/config/manager.html#Disable_Session_Persistence, I added the following code piece to disable session persistence in Tomcat 7. Manager pathname= / After this change I can see that SESSIONS.ser is not getting created as expected, but even after restarting tomcat, the previous JSESSIONID is still valid. Why is tomcat not invalidating the previous JSESSIONID ?
Tomcat 7 Session Persistence disable not working as expected
Hi, На понеделник, 10 март 2014 г. Akash Jain akash.delh...@gmail.com написа: As documented in https://tomcat.apache.org/tomcat-5.5-doc/config/manager.html#Disable_Session_Persistence , I added the following code piece to disable session persistence in Tomcat 7. What is the exact version of Tomcat? The correct documentation for Tomcat 7 is [1]. Regards, Violeta [1] http://tomcat.apache.org/tomcat-7.0-doc/config/manager.html#Disable_Session_Persistence Manager pathname= / After this change I can see that SESSIONS.ser is not getting created as expected, but even after restarting tomcat, the previous JSESSIONID is still valid. Why is tomcat not invalidating the previous JSESSIONID ?
Re: Tomcat 7 Session Persistence disable not working as expected
Hi Violeta, Its latest version ( 7.0.52 ) On Sun, Mar 9, 2014 at 10:28 PM, Violeta Georgieva violet...@apache.orgwrote: Hi, На понеделник, 10 март 2014 г. Akash Jain akash.delh...@gmail.com написа: As documented in https://tomcat.apache.org/tomcat-5.5-doc/config/manager.html#Disable_Session_Persistence , I added the following code piece to disable session persistence in Tomcat 7. What is the exact version of Tomcat? The correct documentation for Tomcat 7 is [1]. Regards, Violeta [1] http://tomcat.apache.org/tomcat-7.0-doc/config/manager.html#Disable_Session_Persistence Manager pathname= / After this change I can see that SESSIONS.ser is not getting created as expected, but even after restarting tomcat, the previous JSESSIONID is still valid. Why is tomcat not invalidating the previous JSESSIONID ?
