RE: Tomcat scalability
You would be better off to use a load balancer in front of a cluster of Tomcat servers. It gives you very good scalability, with good fault tolerance. -Original Message- From: ryan [mailto:rsburgess;shaw.ca] Sent: 03 November, 2002 12:39 AM To: [EMAIL PROTECTED] Subject: Tomcat scalability 1. For a project my company is working on we have transactions requirements of 1600 transactions per second. The transactions consists of processing a servlet in Tomcat, doing a database call and then displaying the results to the user so the effective number of transactions Tomcat has to process is actually greater than 1600. Can Tomcat cope with 1600 requests in a second(a 4 processor Sunfire machine will be used)? Based upon our current application architecture(our java application has tomcat running inside it), 1600 request per second means we may have 1600 threads open simultaneously. 2. From one article I read at linux journal, Tomcat 3 didn't scale very well with multiple processors because of JVM issues. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
JSP Compilation Problem: Tomcat 4.1.12
I posted this several days ago on tomcat-user and haven't gotten any responses so I am reposting it here. I am running into a problem with JSP pages under 4.1.12. I looked through the release notes, and the documentation and I can't find anything that seems to apply. Given a Servlet with the line: %@ page import=WebApp, CalServlet % where WebApp and CalServlet are classes in my application WEB-INF/classes directory that compiles under 4.0.4, when I try to run the servlet under 4.1.12, it crashes on compile with the following message: /usr/local/jakarta-tomcat-4.1.12/work/Standalone/localhost/caldev/index_jsp. java:7: '.' expected import WebApp; I turned on debugging, and the classpath looks correct: [javac] index_jsp.java added as /usr/local/jakarta-tomcat-4.1.12/work/Standalone/localhost/caldev/index_jsp. class doesn't exist. [javac] Compiling 1 source file [javac] Using modern compiler [javac] Compilation arguments: [javac] '-classpath' [javac] '/usr/java/lib/tools.jar:/usr/local/jakarta-tomcat-4.1.12/bin/bootstrap.jar: /home/gsexton/cdaily/WEB-INF/classes:/home/gsexton/cdaily/WEB-INF/lib/PNGEnc oder.jar:/home/gsexton/cdaily/WEB-INF/lib/activation.jar:/home/gsexton/cdail y/WEB-INF/lib/cryptix32.jar:/home/gsexton/cdaily/WEB-INF/lib/jdbc7.1-1.2.jar :/home/gsexton/cdaily/WEB-INF/lib/mail.jar:/usr/local/jakarta-tomcat-4.1.12/ shared/classes:/usr/local/jakarta-tomcat-4.1.12/common/classes:/usr/local/ja karta-tomcat-4.1.12/common/endorsed/xmlParserAPIs.jar:/usr/local/jakarta-tom cat-4.1.12/common/endorsed/xercesImpl.jar:/usr/local/jakarta-tomcat-4.1.12/c ommon/lib/activation.jar:/usr/local/jakarta-tomcat-4.1.12/common/lib/jasper- runtime.jar:/usr/local/jakarta-tomcat-4.1.12/common/lib/jasper-compiler.jar: /usr/local/jakarta-tomcat-4.1.12/common/lib/naming-resources.jar:/usr/local/ jakarta-tomcat-4.1.12/common/lib/commons-collections.jar:/usr/local/jakarta- tomcat-4.1.12/common/lib/naming-common.jar:/usr/local/jakarta-tomcat-4.1.12/ common/lib/commons-logging-api.jar:/usr/local/jakarta-tomcat-4.1.12/common/l ib/ant.jar:/usr/local/jakarta-tomcat-4.1.12/common/lib/mail.jar:/usr/local/j akarta-tomcat-4.1.12/common/lib/commons-dbcp.jar:/usr/local/jakarta-tomcat-4 .1.12/common/lib/servlet.jar:/usr/local/jakarta-tomcat-4.1.12/common/lib/jdb c2_0-stdext.jar:/usr/local/jakarta-tomcat-4.1.12/common/lib/commons-pool.jar :/usr/local/jakarta-tomcat-4.1.12/common/lib/jndi.jar:/usr/local/jakarta-tom cat-4.1.12/common/lib/naming-factory.jar:/usr/local/jakarta-tomcat-4.1.12/co mmon/lib/jta.jar:/usr/local/jakarta-tomcat-4.1.12/common/lib/MHS.jar:/usr/lo cal/jakarta-tomcat-4.1.12/common/lib/jdbc7.1-1.2.jar:/usr/local/jakarta-tomc at-4.1.12/common/lib/jconn2.jar' [javac] '-sourcepath' [javac] '/usr/local/jakarta-tomcat-4.1.12/work/Standalone/localhost/caldev' [javac] '-encoding' [javac] 'ISO-8859-1' [javac] '-g' [javac] [javac] The ' characters around the executable and arguments are [javac] not part of the command. [javac] File to be compiled: [javac] /usr/local/jakarta-tomcat-4.1.12/work/Standalone/localhost/caldev/index_jsp. java I tried this with Tomcat running as root and got the same result. I am using: java version 1.4.1 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-b21) Java HotSpot(TM) Client VM (build 1.4.1-b21, mixed mode) On RedHat 7.2 w/ all patches applied. Any ideas on this would be appreciated. George Sexton MH Software, Inc. Home of Connect Daily Web Calendar Software http://www.mhsoftware.com/connectdaily.htm Voice: 303 438 9585 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JSP Compilation Problem: Tomcat 4.1.12
I'm confused by the change in behavior. I can use JDK 1.4 w/ Tomcat 4.0.4 and it works. -Original Message- From: peter lin [mailto:[EMAIL PROTECTED]] Sent: 02 October, 2002 8:56 AM To: Tomcat Developers List Subject: Re: JSP Compilation Problem: Tomcat 4.1.12 if you're using jdk 1.4, you have to have package names for your classes. If you do not, it won't load the class correctly. have you tried giving your classes a package name and trying it again? peter Sexton, George wrote: I posted this several days ago on tomcat-user and haven't gotten any responses so I am reposting it here. I am running into a problem with JSP pages under 4.1.12. I looked through the release notes, and the documentation and I can't find anything that seems to apply. Given a Servlet with the line: %@ page import=WebApp, CalServlet % where WebApp and CalServlet are classes in my application WEB-INF/classes directory that compiles under 4.0.4, when I try to run the servlet under 4.1.12, it crashes on compile with the following message: /usr/local/jakarta-tomcat-4.1.12/work/Standalone/localhost/caldev/index_jsp. java:7: '.' expected import WebApp; I turned on debugging, and the classpath looks correct: -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JSP Compilation Problem: Tomcat 4.1.12
Never mind. I found this described in Bug #10036. -Original Message- From: Sexton, George [mailto:[EMAIL PROTECTED]] Sent: 02 October, 2002 9:03 AM To: Tomcat Developers List Subject: RE: JSP Compilation Problem: Tomcat 4.1.12 I'm confused by the change in behavior. I can use JDK 1.4 w/ Tomcat 4.0.4 and it works. -Original Message- From: peter lin [mailto:[EMAIL PROTECTED]] Sent: 02 October, 2002 8:56 AM To: Tomcat Developers List Subject: Re: JSP Compilation Problem: Tomcat 4.1.12 if you're using jdk 1.4, you have to have package names for your classes. If you do not, it won't load the class correctly. have you tried giving your classes a package name and trying it again? peter Sexton, George wrote: I posted this several days ago on tomcat-user and haven't gotten any responses so I am reposting it here. I am running into a problem with JSP pages under 4.1.12. I looked through the release notes, and the documentation and I can't find anything that seems to apply. Given a Servlet with the line: %@ page import=WebApp, CalServlet % where WebApp and CalServlet are classes in my application WEB-INF/classes directory that compiles under 4.0.4, when I try to run the servlet under 4.1.12, it crashes on compile with the following message: /usr/local/jakarta-tomcat-4.1.12/work/Standalone/localhost/caldev/index_jsp. java:7: '.' expected import WebApp; I turned on debugging, and the classpath looks correct: -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [Bug 6832] - Locale of the browser is ignored by the AJP13 connector
This is not an IIS problem. I had it under Linux all the way up through 4.0.4-b1. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 18 June, 2002 4:31 AM To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 6832] - Locale of the browser is ignored by the AJP13 connector DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6832. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6832 Locale of the browser is ignored by the AJP13 connector --- Additional Comments From [EMAIL PROTECTED] 2002-06-18 10:30 --- Didn't have such problem with tomcat 4.0.4 and latest JTC, with Apache 2.0.36 + mod_jk 1.2.0. May be only IIS related but Nacho could take a look at it... -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [Bug 6832] - Locale of the browser is ignored by the AJP13 connector
I just tested this with Tomcat 4.0.4 connector and tomcat 4.0.4 using Apache 1.3.24 on RedHat 7.2 and it is absolutely broken. I find it unusual that a European would not fix such a crucial piece of code for localization of applications. This defect was reported in March It was confirmed by a second source in March. I reported it to you separately in April. I have yet again, confirmed it's existence. To recap my original message sent directly to you in April: I am running into a problem with accept-language/getLocales() when I use mod_jk with the ajp13 connector. System Configuration: RedHat Linux 7.2 Apache 1.3.22 Tomcat 4.0.4-B1 mod_jk.so 4.0.4-B2 version 1.2.0 When I go through mod_jk, getLocales() only returns the default locale of the container. It does not return the locales that are specified by the accept-language header. I looked at the source and didn't see anything really jump out at me. FWIW, the problem is also manifested with the 1.1 connector distributed If I connect to the http 1.1 connector on port 8080, I get: !-- protocol=HTTP/1.1 -- !-- Accept-Language=de,en-us;q=0.8,fr;q=0.5,es;q=0.3 -- !-- Locale=de -- !-- Locale: de -- !-- Locale: en_US -- !-- Locale: fr -- !-- Locale: es -- If I connect through apache using ajp13 and mod_jk 1.2 I get: !-- protocol=HTTP/1.1 -- !-- Accept-Language=de,en-us;q=0.8,fr;q=0.5,es;q=0.3 -- !-- Locale=en_US -- !-- Locale: en_US -- The real difference seems to be going through mod_jk.so. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 18 June, 2002 4:31 AM To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 6832] - Locale of the browser is ignored by the AJP13 connector DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6832. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6832 Locale of the browser is ignored by the AJP13 connector --- Additional Comments From [EMAIL PROTECTED] 2002-06-18 10:30 --- Didn't have such problem with tomcat 4.0.4 and latest JTC, with Apache 2.0.36 + mod_jk 1.2.0. May be only IIS related but Nacho could take a look at it... -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [Bug 6832] - Locale of the browser is ignored by the AJP13 connector
Henri, I apologize. It is never fair to take out one's frustrations on another. I have to admit I have been pretty frustrated with connectors. We are selling a calendaring app, and I really want people in France to see the days of the week in French when you look at my calendar. I want an associate in Germany to transparently see the calendar in German. I also want the calendar to show Monday as the first day of the week. I am seriously planning on having the application translated into the major European languages. I really want the application to transparently run in every ISO-8859-1 language I can. The other character sets will come, but I want these first. All of these things require a working locale sub-system. I switched to mod_webapp because it doesn't have the locale problem. Instead, mod_webapp is broken in that it doesn't pass all requests to tomcat for aliased servlets. I.E. if I alias /context/foo/*.html to DisplayServlet, it doesn't pass the request to Tomcat. So, a connector that I switched to in order to solve one problem, has a different problem. Out of the two problems, I figured locales was the one that would be more practical to resolve. Out in user land, there is a lot of confusion over connectors. It would be nice if there were a roadmap to connectors that said This is the future, and this is the past. Building connectors is insanely difficult. It took me at least a dozen tries to get mod_jk to build correctly. Needless to say, there should be pre-compiled connectors for the unwashed masses. I personally find it stunning that there are no less than 4 connectors for Tomcat. I understand the theories of Open Source darwinism, but it would be nice to have one connector that wasn't broken in some way. Chris Cain suggested that the connectors should be a sub-project and subject to the same sort of discipline that the regular project is, including voting. One thing that I can point out, is that connectors need to be organized into teams. Your comments to the effect that mod_jk works with this configuration so this is not my problem doesn't cut it in user land. In user land, all they know is mod_jk works or it doesn't. If the sections are maintained by different people, then there needs to be much tighter coordination. The C connector is nothing without the Tomcat ajp listener. The Tomcat AJP listener is nothing without the C Module. They are two halves of a whole. I hope that this helps you understand more of how users see things. George Sexton MH Software, Inc. Voice: 303 438 9585 http://www.mhsoftware.com -Original Message- From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Sent: 18 June, 2002 10:39 AM To: Tomcat Developers List Subject: RE: [Bug 6832] - Locale of the browser is ignored by the AJP13 connector I find it unusual that a European would not fix such a crucial piece of code for localization of applications. Thanks god there is many europeans commiters on tomcat to try to fix these problems. This defect was reported in March And will be corrected in June by a French commiter. BTW, ajp13 protocol forward all language, so the patch is needed in java side. It was confirmed by a second source in March. Yep I reported it to you separately in April. ReYep I have yet again, confirmed it's existence. To recap my original message sent directly to you in April: Ok I am running into a problem with accept-language/getLocales() when I use mod_jk with the ajp13 connector. System Configuration: RedHat Linux 7.2 Apache 1.3.22 Tomcat 4.0.4-B1 mod_jk.so 4.0.4-B2 version 1.2.0 It works well with mod_jk 1.2.0 and tomcat 3.3.1 Request Information JSP Request Method: GET Request URI: /examples/jsp/snp/snoop.jsp Request Protocol: HTTP/1.1 Servlet path: /jsp/snp/snoop.jsp Path info: null Path translated: null Query string: null Content length: 0 Content type: null Server name: hgo1.slib.com Server port: 80 Remote user: null Remote address: 172.31.1.85 Remote host: pc0082.slib.com Authorization scheme: null Locale: fr_FR Locales: fr_FR en_US en Secure: false Scheme: http cipher_suite: null key_size: null ssl_session: null The browser you are using is Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
