Japanese on tomcat 4.0.3
Hello, There is an attribute: URIEncoding=UTF-8 which can be put in Connector element, if the connector is Coyote. I use tomcat 4.0.3 (with HttpConnector). In the documentation there is no URIEncoding=UTF-8 for this kind of connector. How do I configure this attribute any way? My problem is that I am running tomcat on a Japanese machine. And if I click on a link of a file which is Japanese, I get a broken link. I.e., I have a context named myFolder, which is mapped to a local folder on the Japanese. Let?s say folder X I can see the folder's content if I open IE on http:\\localhost:8080\myFolder\ But if I click on one of the folder's content which has Japanese name, I get a broken link. On TC 5, with coyote connector and with URIEncoding=UTF-8 attribute, there is no broken link. I need a solution for the broken link to tomcat 4.0.3. I tried this: 1. Added this attribute anyway - didn't help. 2. Added tomcat-coyote.jar to server\lib (taken from 4.1.3 version) + attribute + changed the connector class to coyote class- didn't help. Anyone has an idea how to solve this on 4.0.3? I can't upgrade from 4.0.3. I need a solution in this version. Thanks Yair - Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football
Compression doesn't work :(
I try setting compression-related properties on Connector, but it doesn't compress anything :( Connector port=8080 maxHttpHeaderSize=8192 maxThreads=250 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true compression=on compressionMinSize=2048 / No pages are compressed (nor static, nor servlets) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SV: Compression doesn't work :(
Without knowing the proper way to configure compression, it looks like you have configured it to not compressing anything smaller than 2048kbyte? But I could be wrong on this... yvind Johansen ElectricTimeCar 2802 Gjvik, Norway -Opprinnelig melding- Fra: smmarrt [mailto:[EMAIL PROTECTED] Sendt: 19. juni 2005 14:59 Til: Tomcat Users List Emne: Compression doesn't work :( I try setting compression-related properties on Connector, but it doesn't compress anything :( Connector port=8080 maxHttpHeaderSize=8192 maxThreads=250 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true compression=on compressionMinSize=2048 / No pages are compressed (nor static, nor servlets) - 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: Re: configuration question : the number of connections could be supported by a connector in Tomcat 5.0
I think the http protocol does not allow the parallel processing of requests using a single connection. At least the response of a following request cannot pass the predecessor on the same connection. (How could the responses be matched to the requests?) So parallel processing is not really useful on a single connection. If a client/browser wants to have parallel processing it uses more than one connection to a server. Karl-Heinz - Original Message - From: Feng Xie (fxie) [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Sunday, June 19, 2005 5:25 AM Subject: RE: Re: configuration question : the number of connections could be supported by a connector in Tomcat 5.0 Bill: Thanks for your answer. In my case, the client just directly talks to Tomcat. So, the maxThread means maxConnections. Is it possible for Tomcat ( any version which supports HTTP/1.1 pipelining)'s multiple threads to work on *A same* connection at the same time. I mean, due to pipelining, there might be multiple HTTP requests in this connection waiting for process , therefore, multiple threads in Tomcat are working on processing those pipelined requests simutaneously -- each thread handling a single different request. -Feng -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Friday, June 17, 2005 10:47 PM To: tomcat-user@jakarta.apache.org Subject: Re: configuration question : the number of connections could be supported by a connector in Tomcat 5.0 If you are fronting with Apache, then the mapping between connections and threads is more a function of your MPM. As a result, I'm just going to answer for the stand-alone Connector. In Tomcat 5.0, there is a one-to-one mapping between socket connections and threads. Pipelined HTTP/1.1 keep-alive connections will all use the same thread to process. In 5.5.10+ this will no longer necessarily be the case. It will be possible for Tomcat to handle many (and the value of 'many' is heavily dependent on what your app does :) more socket connections than the configured maxThreads. Feng Xie (fxie) [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] . I like to get some help on how to configure the maximum number of connections could be supported by Tomcat5.0. There is one config attribute called maxThreads, according to Tomcat doc, which isThe maximum number of request processing threads to be created by this Connector, which therefore determines the maximum number of simultaneous requests that can be handled. . My question comes from the fact that there might be multiple HTTP requests pipelined in each HTTP/1.1 connections, so can we still treat the maxThread as the maxConnections. Thanks in advance, Feng - 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] ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SV: Compression doesn't work :(
No, Tomcat treats this value in bytes. :( yvind Johansen : Without knowing the proper way to configure compression, it looks like you have configured it to not compressing anything smaller than 2048kbyte? But I could be wrong on this... yvind Johansen ElectricTimeCar 2802 Gjvik, Norway -Opprinnelig melding- Fra: smmarrt [mailto:[EMAIL PROTECTED] Sendt: 19. juni 2005 14:59 Til: Tomcat Users List Emne: Compression doesn't work :( I try setting compression-related properties on Connector, but it doesn't compress anything :( Connector port=8080 maxHttpHeaderSize=8192 maxThreads=250 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true compression=on compressionMinSize=2048 / No pages are compressed (nor static, nor servlets) - 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: SV: Compression doesn't work :(
How are you testing that nothing is compressed? E.g. which browser? smmarrt wrote: No, Tomcat treats this value in bytes. :( yvind Johansen : Without knowing the proper way to configure compression, it looks like you have configured it to not compressing anything smaller than 2048kbyte? But I could be wrong on this... yvind Johansen ElectricTimeCar 2802 Gjvik, Norway -Opprinnelig melding- Fra: smmarrt [mailto:[EMAIL PROTECTED] Sendt: 19. juni 2005 14:59 Til: Tomcat Users List Emne: Compression doesn't work :( I try setting compression-related properties on Connector, but it doesn't compress anything :( Connector port=8080 maxHttpHeaderSize=8192 maxThreads=250 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true compression=on compressionMinSize=2048 / No pages are compressed (nor static, nor servlets) - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Compression doesn't work :(
Fra: smmarrt [mailto:[EMAIL PROTECTED] Emne: Compression doesn't work :( I try setting compression-related properties on Connector, but it doesn't compress anything :( Connector port=8080 maxHttpHeaderSize=8192 snip compression=on compressionMinSize=2048 / How did you determine that compression was not being applied? It would help if you told us what Tomcat level you're using. Unfortunately, the comments in server.xml appear to be left over from some past life, so actually reading the documentation is a necessity. There is no compressionMinSize attribute identified in the 4.1, 5.0, or 5.5 docs (or the code, as far as I can tell); if you're using a level older than that, you've got other problems to worry about. For 5.5, the actual description for compression is: -- The Connector may use HTTP/1.1 GZIP compression in an attempt to save server bandwidth. The acceptable values for the parameter is off (disable compression), on (allow compression, which causes text data to be compressed), force (forces compression in all cases), or a numerical integer value (which is equivalent to on, but specifies the minimum amount of data before the output is compressed). If the content-length is not known and compression is set to on or more aggressive, the output will also be compressed. If not specified, this attribute is set to off. -- The doc fails to say what the default minimum compression size is, so I tried compression=force, and all the content now appears properly garbled in Ethereal. Also, take a look at compressableMimeType: -- The value is a comma separated list of MIME types for which HTTP compression may be used. The default value is text/html,text/xml,text/plain. -- Note that trying to compress some static content (e.g., jpg, pdf) is a waste of time. - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat, windows and more memory
Hi, Charl. Very useful link, http://www.jchem.com/doc/admin/tomcat.html try to edit ENVIRONMENT VARIABLES - JAVA_OPTS CG How do you configure Tomcat (4.1.31) to be allocated CG more memory in Windows when using the installed CG Programs/Apache Tomcat 4.1/Start Tomcat shortcuts? CG These shortcuts do not seem to use the catalina.bat CG file, so setting the JAVA_OPTS there has no effect. CG I tried putting the java options -Xmx512 as an extra CG shortcut parameter, but then Tomcat didn't even start. CG Thanks CG Charl CG - CG To unsubscribe, e-mail: [EMAIL PROTECTED] CG For additional commands, e-mail: [EMAIL PROTECTED] -- regards, Sergey mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
where can i see log trace logAbandoned
hi all When i say logAbandoned = true in data-source of struts-config.xml , it still does',nt trace abandoned connection .How can i achieve this and where can i see the log? Thanks Vijay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Java Web Parts release
Thought this might be of interest to some... The Java Web Parts SF project I began had its first release this weekend. It's a pre-alpha, but my thinking is to put out smaller releases as frequently as possible so that, theoretically at least, the code will be more solid when a GA release comes out. http://sourceforge.net/projects/javawebparts/ If anyone is interested in contributing, please contact me (either direct eMail or on the project mailing lists or forums). A quick synopsis of the project: Java Web Parts is a collection of small, largely independent utility-type classes and functions for Java web application developers including taglibs, filters, JSP templates, servlets, utility classes and other general-purpose code. -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Differences between service startup and batch startup
I have noticed a difference between starting Tomcat 5.0.28 using the service and the batch file. When I run startup.bat, everything seems to be running fine. I have an ODBC node defined, connecting to an Access database, and I have no trouble retrieving the data through Tomcat. However, when I start Tomcat using the Windows service, Tomcat comes up without any errors, but I cannot retrieve the data from the database. I get the following error: 2005-06-18 23:13:06 StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception com.borland.dx.dataset.DataSetException: General error I am wondering if it has to do with the user accounts. I know that in the Tomcat service configuration, you can specify the account to log on as. I have tried entering in my account info, but it doesn't seem to make a difference. Plus, the ODBC node is defined as a system node, which should be available to all users. Anyway, if anyone can offer any ideas, I would greatly appreciate it. Thanks. John Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
