tomcat 4.0.1 and persistent connection problem
Dear Sir I already did some research about this problem. But still be confused. I want to take advantage of the persistent connection of Http/1.1. In my experiement, if HTTP/1.1 client connects to the tomcat 4.0.1 Http/1.1 directly, the persistent connection can be established. However, it is usless because actually all companies employ http proxies. Furthermore, a lot of them such as the squid is a http/1.0 proxy. in my application, the client (http/1.1) - squid proxy(http/1.0) tomcat 4.0.1.(Http/1.1) I found that tomcat 4.0.1 always sends a FIN package after it sends the response even i send the Connection: Keep-Alive in the request header. Also, I know the tomcat does also received Connection: Keep-Alive header via proxy. I did a comparison between tomcat4.0.1 and apache 1.3.9, the results show that if If I add Connection: Keep-Alive header in the request, apache server will keep the connection alive even the proxy/client sends a HTTP/1.0 package. However, It seems that tomcat 4.0.1 doesn't support this feature. I think this feature isn't defined in specification, however, it is so important that it provide the only way(am i right?) to establish persistent connection in real world which is consisted of unexpected HTTP/1.0 proxies. I don't know whether my understanding is correct or not. Any comments are welcome. Thanks a lot. yangyuexiang -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Problem with JAAS and TOMCAT 4.0.1
I have already done this, but I have not found a good solution to make it work. I someone that has put it to work could send me his/her configuration it would be a great help. Cheers Antony Bowesman wrote: Ismael Blesa Part wrote: Hi have modified the sample given with JAAS 1.0. I have developed a jsp that calls the sample.java file. This file has been modificated in several ways, the main method has been changed to a method class and some other changes to adapt it to a web application. The problem is that when I try to run the jsp I get the following error: java.lang.SecurityException: unable to instantiate LoginConfiguration at javax.security.auth.login.Configuration.getConfiguration(Configuration.java:212) at javax.security.auth.login.LoginContext$1.run(LoginContext.java:166) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.LoginContext.init(LoginContext.java:163) at javax.security.auth.login.LoginContext.(LoginContext.java:319) at sample.Sample.run(Sample.java:47) at org.apache.jsp.Login$jsp._jspService(Login$jsp.java:64) I have tried copying the jaas.jar, the sample_jaas.config and the loginmodule classes to all the places where I think that it should work. Have a look at the tomcat-user archives for messages 'JAAS not working any more with Tomcat 4.0'. (Oct 2001) Antony -- 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]
errors starting tomcat 4 on linux
Hi All, Would anyone have any idea what the following error may be caused by when trying to start up tomcat 4 on suse linux 6.2 thanks Function name=(N/A) Library=(N/A) NOTE: We are unable to locate the function name symbol for the error just occurred. Please refer to release documentation for possible reason and solutions. Current Java thread: Dynamic libraries: 08048000-0804c000 r-xp 08:03 882710 /usr/local/java/jdk1.3.1_01/bin/i386/native_threads/java 0804c000-0804d000 rw-p 3000 08:03 882710 /usr/local/java/jdk1.3.1_01/bin/i386/native_threads/java 4000-40013000 r-xp 08:03 63508 /lib/ld-2.1.1.so 40013000-40014000 rw-p 00012000 08:03 63508 /lib/ld-2.1.1.so 40015000-40016000 r--p 08:03 2017282 /usr/share/locale/en_US/LC_MESSAGES/SYS_LC_MESSAGES 40016000-40017000 r--p 08:03 2015236 /usr/share/locale/en_US/LC_MONETARY 40017000-40018000 r--p 08:03 2015238 /usr/share/locale/en_US/LC_TIME 40018000-40019000 r--p 08:03 2015237 /usr/share/locale/en_US/LC_NUMERIC 40019000-4001c000 r--p 08:03 2015235 /usr/share/locale/en_US/LC_CTYPE 4001e000-40028000 r-xp 08:03 63527 /lib/libpthread.so.0 40028000-4003 rw-p 9000 08:03 63527 /lib/libpthread.so.0 4003-40039000 r-xp 08:03 1402893 /usr/local/java/jdk1.3.1_01/jre/lib/i386/native_threads/libhpi.so 40039000-4003a000 rw-p 8000 08:03 1402893 /usr/local/java/jdk1.3.1_01/jre/lib/i386/native_threads/libhpi.so 4003a000-40227000 r-xp 08:03 1576975 /usr/local/java/jdk1.3.1_01/jre/lib/i386/client/libjvm.so 40227000-4031d000 rw-p 001ec000 08:03 1576975 /usr/local/java/jdk1.3.1_01/jre/lib/i386/client/libjvm.so 40335000-40337000 r-xp 08:03 63517 /lib/libdl.so.2 40337000-40338000 rw-p 1000 08:03 63517 /lib/libdl.so.2 40338000-4042a000 r-xp 08:03 63513 /lib/libc.so.6 4042a000-4042e000 rw-p 000f1000 08:03 63513 /lib/libc.so.6 40432000-40444000 r-xp 08:03 63519 /lib/libnsl.so.1 40444000-40446000 rw-p 00011000 08:03 63519 /lib/libnsl.so.1 40448000-40464000 r-xp 08:03 63518 /lib/libm.so.6 40464000-40465000 rw-p 0001b000 08:03 63518 /lib/libm.so.6 40465000-4049e000 r-xp 08:03 235544 /usr/lib/libstdc++-2-libc6.1-1-2.9.0.so 4049e000-404aa000 rw-p 00038000 08:03 235544 /usr/lib/libstdc++-2-libc6.1-1-2.9.0.so 404ae000-404bf000 r-xp 08:03 1368077 /usr/local/java/jdk1.3.1_01/jre/lib/i386/libverify.so 404bf000-404c1000 rw-p 0001 08:03 1368077 /usr/local/java/jdk1.3.1_01/jre/lib/i386/libverify.so 404c1000-404e2000 r-xp 08:03 1368078 /usr/local/java/jdk1.3.1_01/jre/lib/i386/libjava.so 404e2000-404e4000 rw-p 0002 08:03 1368078 /usr/local/java/jdk1.3.1_01/jre/lib/i386/libjava.so 404e5000-404f9000 r-xp 08:03 1368079 /usr/local/java/jdk1.3.1_01/jre/lib/i386/libzip.so 404f9000-404fc000 rw-p 00013000 08:03 1368079 /usr/local/java/jdk1.3.1_01/jre/lib/i386/libzip.so 404fc000-4122a000 r--s 08:03 1363996 /usr/local/java/jdk1.3.1_01/jre/lib/rt.jar 41257000-414fc000 r--s 08:03 1363997 /usr/local/java/jdk1.3.1_01/jre/lib/i18n.jar 414fc000-41512000 r--s 08:03 1363984 /usr/local/java/jdk1.3.1_01/jre/lib/sunrsasign.jar 435ba000-435bf000 r--s 08:03 1175604 /usr/local/tomcat/jakarta-tomcat-4.0.1/common/lib/jta.jar 4961f000-49627000 r--p 08:03 2015234 /usr/share/locale/en_US/LC_COLLATE 49627000-4962e000 r--s 08:03 1548315 /usr/local/tomcat/jakarta-tomcat-4.0.1/bin/bootstrap.jar 4969a000-496a6000 r--s 08:03 1175597 /usr/local/tomcat/jakarta-tomcat-4.0.1/common/lib/activation.jar 496a6000-496f r--s 08:03 1175599 /usr/local/tomcat/jakarta-tomcat-4.0.1/common/lib/tyrex-0.9.7.0.jar 496f-496f9000 r--s 08:03 1175605 /usr/local/tomcat/jakarta-tomcat-4.0.1/common/lib/naming-resources.jar 496f9000-4970 r--s 08:03 1175607 /usr/local/tomcat/jakarta-tomcat-4.0.1/common/lib/naming-common.jar 4980-49c7f000 r--s 08:03 507925 /usr/local/java/jdk1.3.1_01/lib/tools.jar 49c7f000-49e39000 r--s 08:03 1175598 /usr/local/tomcat/jakarta-tomcat-4.0.1/common/lib/xerces.jar 49e39000-49e4e000 r--s 08:03 1175601 /usr/local/tomcat/jakarta-tomcat-4.0.1/common/lib/jdbc2_0-stdext.jar 49e4e000-49e61000 r--s 08:03 1175602 /usr/local/tomcat/jakarta-tomcat-4.0.1/common/lib/servlet.jar 49e61000-49ea6000 r--s 08:03 1175603 /usr/local/tomcat/jakarta-tomcat-4.0.1/common/lib/mail.jar 49ea6000-49ead000 r--s 08:03 1384458 /usr/local/tomcat/jakarta-tomcat-4.0.1/server/lib/warp.jar 49ead000-49eb3000 r--s 08:03 1384459 /usr/local/tomcat/jakarta-tomcat-4.0.1/server/lib/servlets-webdav.jar 49eb3000-49f43000 r--s 08:03 1384460 /usr/local/tomcat/jakarta-tomcat-4.0.1/server/lib/catalina.jar Local Time = Thu Nov 29 23:17:30 2001 Elapsed Time = 2 # # The exception above was detected in native code outside the VM #
Re: errors starting tomcat 4 on linux
Daliso Zuze wrote: Hi All, Would anyone have any idea what the following error may be caused by when trying to start up tomcat 4 on suse linux 6.2 Yes. A buggy JVM. 1.3.x from Sun has issues on Linux. Check out their bug database. My recommendation: use IBM's 1.3.0. It's faster and more stable. Bojan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: TC 3.3: For Servlets only
[EMAIL PROTECTED] wrote: On Thu, 29 Nov 2001, Bojan Smojver wrote: Bill Barker wrote: I've checked in a change to move setting the default mapping to JspInterceptor. Now, all Bojan needs to do is to comment out JspInterceptor in server.xml and all of his *.jsp files will be served as regular text files. Again, thanks for this. It makes JSP and Servlet spec totally different beasts in Tomcat 3.3.x. Cool! Just keep in mind that the beast can't be called Tomcat after that ! Pick a different name for it. Maybe just 'Tom' (since 'cat' was eaten with JSP's ;-) Bojan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: TC 3.3: For Servlets only
Maybe just 'Tom' (since 'cat' was eaten with JSP's ;-) +1 !=))) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[PATCH] webapp-module-1.0-tc40: pr_warp_defs.h not build correctly
Hi, I think there is a small bug in webapp-module-1.0-tc40/lib/Makefile.in. This bug causes pr_warp_defs.h to be generated as an empty file. Maybe, someone already fixed this. I can't get the file directly from the cvs, cause I'm living behind a firewall and proxy :-( So I got the file from http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0/src/webapp- module-1.0-tc40-src.tar.gz Regards, Hendrik --- Hendrik Harms TOJAQ Datentechnik GmbH, Germany Tel.: 05361 / 9 - 49828 Handy: 0151 / 12 70 23 37 E-Mail: [EMAIL PROTECTED] *** Makefile.in Mon Sep 17 02:42:59 2001 --- Makefile.in.fix Fri Nov 30 11:23:30 2001 *** *** 56,62 # = # # @author Pier Fumagalli mailto:[EMAIL PROTECTED] ! # @version $Id: Makefile.in,v 1.16 2001/09/17 00:42:59 pier Exp $ include @TGTDIR@/Makedefs --- 56,62 # = # # @author Pier Fumagalli mailto:[EMAIL PROTECTED] ! # @version $Id: Makefile.in,v 1.16 2001/09/17 00:42:59 pier Exp + fix $ include @TGTDIR@/Makedefs *** *** 96,102 pr_warp_defs.h: $(TGTDIR)/java/Constants.java @$(MECHO) Generating \$@\ ! @$(CAT) $ | \ $(GREP) TYPE_ | \ $(SED) s/public static final int/#define/g | \ $(SED) y/=;/ / $@ --- 96,102 pr_warp_defs.h: $(TGTDIR)/java/Constants.java @$(MECHO) Generating \$@\ ! @$(CAT) $? | \ $(GREP) TYPE_ | \ $(SED) s/public static final int/#define/g | \ $(SED) y/=;/ / $@ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: server.xml DTD/Schema
Craig, yes, that's exactly the problem. Valve is another prominent case where the attribute-checking is not possible. One solution, but I confess that I would not recommend it, is to distinguish between the different types, i.e. change Valve to AccessLogValve,RequestDumperValve,RemoteHostFilter etc. That would certainly make the server.xml validatable, but create the burden of changing the xsd/dtd every times a user creates her own Valve/Logger/Realm etc. Could xslt be a solution to check the required attributes if the dtd/schema uses union? Maybe that is to much effort because anyway if a required attribute is not present, the digester would moan. Mika - Original Message - From: Craig R. McClanahan [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Friday, November 30, 2001 4:09 AM Subject: Re: server.xml DTD/Schema One thing to remember is that it is not technically possible to write a DTD for server.xml that covers all possible cases (and I suspect that's true for Schema as well). Consider the following cases: * Elements like Logger and Realm let you define which implementation class you want, from the set of choices included with Tomcat. The set of attributes that are valid depends on which implementation class you choose -- and there is no way to make that distinction in a DTD. The best you could do is list the union of all possible attributes -- but that is not semantically valid for any single implementation. * Even more generally, Tomcat users are free to install their own implementations of Tomcat classes, and there's no way your general purpose DTD would know which attributes are valid. Craig McClanahan On Fri, 30 Nov 2001, Mika Goeckel wrote: Date: Fri, 30 Nov 2001 01:01:46 +0100 From: Mika Goeckel [EMAIL PROTECTED] Reply-To: Tomcat Developers List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: server.xml DTD/Schema Hi, I've built a first version of a DTD/Schema for server.xml and would ask if someone would like to review it? I would prefer the Schema, because it allows more checking, but I haven't seen a parser which checks against schemes, so I created a DTD from it as well. As this is quite a bunch of lines, please hands up who wants to receive it. Cheers, Mika P.S.: The initial cut is from the docu, I plan to go through the source tomorrow to recheck. -- 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] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5197] New: - Error Page 401 redirection avoids web resource authorization
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=5197. 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=5197 Error Page 401 redirection avoids web resource authorization Summary: Error Page 401 redirection avoids web resource authorization Product: Tomcat 4 Version: 4.0.1 Final Platform: All OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The presence of a 401 error redirection create some problem in user authorization; an access to a protected resource generate an Internal Error. Here is a part of my web.xml file: error-page error-code401/error-code location/error_Unauthorized.jsp/location /error-page security-constraint web-resource-collection web-resource-nameProtected Area/web-resource-name url-pattern/login.jsp/url-pattern /web-resource-collection auth-constraint role-nameLogin/role-name /auth-constraint /security-constraint The presence of other kind of redirection (i.e. 404 error) doesn't generate the error. I recreated the error with both Memory and Jdbc Realms. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5198] New: - one Apache with two Tomcats via warp failed
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=5198. 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=5198 one Apache with two Tomcats via warp failed Summary: one Apache with two Tomcats via warp failed Product: Tomcat 4 Version: 4.0.1 Final Platform: Sun OS/Version: Solaris Status: NEW Severity: Normal Priority: Other Component: Webapps AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] There seemed to be a bug connecting two different Tomcats via the mod_webapp from one Apache-Server. The Configuration-Example below is only working, when I comment out one of the WebAppDeloy lines. Otherwise I got many error reports in the apache_error_log: Cannot deploy application oneweb using: IBM_HTTP_Server/1.3.12.3 Apache/1.3.12 (Unix) # cause of Websphere webapp-module-1.0-tc40 Jakarta-Tomcat 4.0.1 #--- apache httpd.conf - WebAppConnection oneWarp warp localhost:8013 WebAppConnection twoWarp warp localhost:8015 VirtualHost _default_:443 WebAppInfo /webapp-info WebAppDeploy oneweb oneWarp /one WebAppDeploy twoweb twoWarp /two /VirtualHost -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5199] New: - jsp:param in jsp:include section not correct
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=5199.
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=5199
jsp:param in jsp:include section not correct
Summary: jsp:param in jsp:include section not correct
Product: Tomcat 4
Version: 4.0.1 Final
Platform: PC
OS/Version: Windows 9x
Status: NEW
Severity: Normal
Priority: Other
Component: Unknown
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
When jsp:param in jsp:include section used international string (russian in
example), parameter tranfered not correctly
file test_include_1.jsp:
%@page
contentType=text/html; charset=utf-8
language=java
%
html
head
meta http-equiv=Content-Type content=text/html; charset=utf-8
/head
body
%
String russian_string = \u0418\u043d\u0444\u043e\u0440\u043c\u0430
\u0446\u0438\u044f \u043e \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442
\u0435\u043b\u0435;
session.setAttribute(TEST_VALUE, russian_string);
%
jsp:include page=test_include_2.jsp
jsp:param name=test_value value=%= russian_string %/
/jsp:include
String from session 1: %= (String)session.getAttribute(TEST_VALUE) %br
/body
/html
file test_include_2.jsp:
%@page
contentType=text/html; charset=utf-8
language=java
import=java.util.Enumeration
%
String from session 2: %= (String)session.getAttribute(TEST_VALUE) %br
String from URL: %= request.getParameter(test_value) %br
%
Enumeration e = request.getParameterNames();
for (; e.hasMoreElements() ;)
{
String n = (String)e.nextElement();
String[] s = request.getParameterValues( n );
for (int i=0; is.length; i++)
out.print(n+ = +s[i]+br);
}
%
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5201] New: - Persistent sessions EJB Statefull
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=5201. 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=5201 Persistent sessions EJB Statefull Summary: Persistent sessions EJB Statefull Product: Tomcat 4 Version: 4.0.1 Final Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Webapps AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When using EJB Statefull session bean (I'm using JBoss, if this info can help), when re-deploying WAR, stoping tomcat and re-starting (I need to do, because just deploying new WAR does not overwrite old expanded files) I get following error (the class is in the WEB- INF/classes/br/com/econet/project/session/MyOwnService.class): 2001-11-30 13:24:20 StandardManager[/portalHIV] ClassNotFoundException while loading persisted sessions: java.lang.ClassNotFoundException: br.com.econet.project.session.MyOwnService java.lang.ClassNotFoundException: br.com.econet.project.session.MyOwnService at org.apache.catalina.loader.StandardClassLoader.loadClassStandardClassLoader.jav a:1124) at org.apache.catalina.loader.StandardClassLoader.loadClassStandardClassLoader.jav a:989) at java.lang.ClassLoader.loadClassInternal(Unknown Source) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) at java.io.ObjectInputStream.resolveProxyClass(Unknown Source) at java.io.ObjectInputStream.inputProxyClassDescriptor(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at java.io.ObjectInputStream.inputObject(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at org.apache.catalina.session.StandardSession.readObjectStandardSession.java:1268 ) at org.apache.catalina.session.StandardSession.readObjectDataStandardSession.java: 810) at org.apache.catalina.session.StandardManager.loadStandardManager.java:411) at org.apache.catalina.session.StandardManager.startStandardManager.java:617) at org.apache.catalina.core.ContainerBase.startContainerBase.java:1104) at org.apache.catalina.core.StandardContext.startStandardContext.java:3352) at org.apache.catalina.core.ContainerBase.addChildContainerBase.java:785) at org.apache.catalina.core.StandardHost.addChildStandardHost.java:415) at org.apache.catalina.core.StandardHost.install(StandardHost.java:643) at org.apache.catalina.startup.HostConfig.deployAppsHostConfig.java:647) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:777) at org.apache.catalina.startup.HostConfig.lifecycleEventHostConfig.java:463) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEventLifecycleSupport.ja va:155) at org.apache.catalina.core.ContainerBase.startContainerBase.java:1131) at org.apache.catalina.core.ContainerBase.startContainerBase.java:1123) at org.apache.catalina.core.StandardEngine.startStandardEngine.java:307) at org.apache.catalina.core.StandardService.startStandardService.java:388) at org.apache.catalina.core.StandardServer.startStandardServer.java:505) at org.apache.catalina.startup.CatalinaService.startCatalinaService.java:261) at org.apache.catalina.startup.CatalinaService.executeCatalinaService.java:172) and so on. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: server.xml DTD/Schema
A first cut of dtd and schema are reviewable under: http://www.mikagoeckel.de/tomcat/server.html, http://www.mikagoeckel.de/tomcat/server.xsd http://www.mikagoeckel.de/tomcat/server.dtd I've thrown all possible attributes for the different classes into the tag, so this is nothing more than to validate structure of tags. Remember this is a first cut, so validate your server.xml against it and report flaws to me, I'm happy to continue refining it. Comments welcome. P.S.: Who is maintaining the documentation on jakarta.apache.org/tomcat I think the graphics from this work could add some clarity to it. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
SSL
Hi, I have some doubts about SSL. Eventhough I posted this mail in user forum, I couldn't get any reply. Hence I am posting this in developer forum. I am now using apache web server with SSL already setup. that means I can connect to HTTP server using SSL: https://10.0.0.105:443/ or I can connect to HTTP server w/o SSL http://10.0.0.105:80 I can make a request to servlet using SSL: https://10.0.0.105:443/admin/servlet/com.app.Admin or I can make request to servelt w/o SSL http://10.0.0.105/admin/servlet/com.app.Admin Will I get a secure connection between servlet web browser if I - block all port that can access servlet engine(e.g. TOMCAT) from internet (e.g. 80, 8080) except SSL port 443. - now web browser to apache web server connection is secure. - apache server to TOMCAT is not secure but only apache can access TOMCAT , then it means TOMCAT(servlet) is secure too?? If the above way is secure. how can I block access to servlet through port 80? or block access to a sepecific web application through port 80? which means access is only granted through SSL port 443. (in TOMCAT for example) Since i need to send private info up from web browser to servlet and make sure no one spy it. ( user/password for example ) thanks. RajeshKannan _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5203] New: - A frameset with 2 JSP's causes duplicate class definition - sometimes
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=5203. 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=5203 A frameset with 2 JSP's causes duplicate class definition - sometimes Summary: A frameset with 2 JSP's causes duplicate class definition - sometimes Product: Tomcat 4 Version: 4.0.1 Final Platform: PC OS/Version: Windows 9x Status: NEW Severity: Major Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Having a frameset with 2 JSP's causes class duplicate definition. Sometimes I get this error with the JSP in the first frame, sometimes, the second frame. In either case, the problem occurs randomly. Here is an example dump (copy and paste from the log file). 2001-11-29 10:58:45 StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception javax.servlet.ServletException: duplicate class definition: org/apache/jasper/runtime/JspRuntimeLibrary at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.ja va:457) at org.apache.jsp.search$jsp._jspService(search$jsp.java:191) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:1 99) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt erChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain. java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:2 43) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:2 01) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2344) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java :170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:462) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:163 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1011 ) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1106) at java.lang.Thread.run(Unknown Source) - Root Cause - java.lang.LinkageError: duplicate class definition: org/apache/jasper/runtime/JspRuntimeLibrary at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at java.security.SecureClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.access$100(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at
WG: No Documentation On Connecting Tomcat4 to Apache
AXA eSolutions GmbH AXA Konzern AG Germany Oliver Lauer Web Architect Wörthstraße 34 D-50668 Köln Germany Tel.: +49 221 148 31277 Fax: +49 221 148 43963 Mobil: +49 179 59 064 59 e-Mail: [EMAIL PROTECTED] _ -Ursprüngliche Nachricht- Von: Marcin Kieæ [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 30. November 2001 17:00 An: Tomcat Users List Betreff: Re: No Documentation On Connecting Tomcat4 to Apache Since any documentation comes from Tomcat Developer I should refer to Tomcat-Dev List. I guess there is some documentation on connecting Tomcat and Apache on CVS (but I'm not sure). Marcin Kiec Kemp Randy-W18971 wrote: Look at http://www.webmasterbase.com/article/305 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 4:05 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: No Documentation On Connecting Tomcat4 to Apache Hello, I've searched high and low for a document that explains how to use Tomcat from Apache httpd. Could some kind sole point me to them? Cheers, Douglass Turner email: [EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] Aus Rechts- und Sicherheitsgruenden ist die in dieser E-Mail gegebene Information nicht rechtsverbindlich. Eine rechtsverbindliche Bestaetigung reichen wir Ihnen gerne auf Anforderung in schriftlicher Form nach. Beachten Sie bitte, dass jede Form der unautorisierten Nutzung, Veroeffentlichung, Vervielfaeltigung oder Weitergabe des Inhalts dieser E-Mail nicht gestattet ist.Diese Nachricht ist ausschliesslich fuer den bezeichneten Adressaten oder dessen Vertreter bestimmt. Sollten Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein, so bitten wir Sie, sich mit dem Absender der E-Mail in Verbindung zu setzen. For legal and security reasons the information provided in this e-mail is not legally binding. Upon request we would be pleased to provide you with a legally binding confirmation in written form. Any form of unauthorised use, publication, reproduction, copying or disclosure of the content of this e-mail is not permitted. This message is exclusively for the person addressed or their representative. If you are not the intended recipient of this message and its contents, please notify the sender immediately. --- -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
java.lang.SecurityException: Cannot set up certs for trusted CAs
Hi,
I work with Jakarta-tomcat and I have JCE(java cryptography package) 1.2.1 into
context\webinfo\lib extension
I am using JDK 1.3 andI have followed all installation issues required and granted all
permissions needed but it just won't work with Tomcat.
The same piece of code works well executed from java command line, Forte, netbeans or
weblogic but not using tomcat.
This is the error message:
PoolTcpConnector: Starting Ajp12ConnectionHandler on 8007
java.lang.ExceptionInInitializerError: java.lang.SecurityException: Cannot set up
certs for trusted CAs at javax.crypto.b.clinit([DashoPro-V1.2-120198]) at
javax.crypto.Cipher.getInstance([DashoPro-V1.2-120198])
Decrypter class:
import java.io.*;
import java.util.*;
import javax.crypto.*;
import java.security.*;
import javax.crypto.spec.*;
import java.security.spec.*;
import com.portland.adx.Header;
import com.sun.crypto.provider.SunJCE;
public class Decryption {
private Cryptography c;
public Decryption() {
c = new Cryptography();
}
public Header decryptHeader(Object tmp){
Cipher desCipher = null;
Header header = null;
try {
desCipher = Cipher.getInstance(DES/ECB/PKCS5Padding);
desCipher.init(Cipher.DECRYPT_MODE, c.desKey);
SealedObject toDecrypt = (SealedObject)tmp;
header = (Header) toDecrypt.getObject(desCipher);
}catch(Exception e) {
System.err.println(e.toString());
return null;
}
return header;
}
}//end class
and Cryptography class:
import java.io.*;
import java.util.*;
import sun.security.*;
import javax.crypto.*;
import java.security.*;
import javax.crypto.spec.*;
import java.security.spec.*;
import sun.security.provider.*;
import com.sun.crypto.provider.SunJCE;
public class Cryptography {
SecretKeySpec desKey;
byte[] keyBuffer;
public Cryptography() {
try {
// Add SunJCE to the list of providers
SunJCE jce = new SunJCE();
Security.addProvider(jce);
//generating secret key
keyBuffer = 02010387.getBytes();
desKey = new SecretKeySpec(keyBuffer,DES);
}catch(Exception e){
e.printStackTrace();
}
}
}
Any help would be very much apreciated
Regards
Frustated
DO NOT REPLY [Bug 5197] - Error Page 401 redirection avoids web resource authorization
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=5197. 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=5197 Error Page 401 redirection avoids web resource authorization [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2001-11-30 08:35 --- This is the same issue as bug 5110. *** This bug has been marked as a duplicate of 5110 *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5110] - ErrorDispatcherValve throws NullPointerException on 403 forbidden!
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=5110. 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=5110 ErrorDispatcherValve throws NullPointerException on 403 forbidden! [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2001-11-30 08:35 --- *** Bug 5197 has been marked as a duplicate of this bug. *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5203] - A frameset with 2 JSP's causes duplicate class definition - sometimes
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=5203. 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=5203 A frameset with 2 JSP's causes duplicate class definition - sometimes [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2001-11-30 09:08 --- There was a race condition in the StandardClassLoader which is very likely to be the root cause of the problem. It has been fixed some time ago in the CVS. The nightly builds have the fix, which will also be in the upcoming Tomcat 4.0.2 beta release. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat classloader problem?
Glenn Nielsen wrote: Chris Malley wrote: [...] I'm experiencing a problem with SOAP message-style services when using Tomcat 4.01. When trying to access any message-style SOAP service, my client receives a no signature match fault. [...] Moving soap.jar to $CATALINA_HOME/webapps/soap/WEB-INF/lib/soap.jar should solve the problem, and could be used as a workaround. Alternately, you can remove from $CATALINA_HOME/webapps/soap/WEB-INF/classes/ the classes which are also present in the JAR. Note: I don't consider this a Catalina problem, but more a questionable packaging choice of the SOAP binary. Remy I agree with Remy, we use soap2.2 in Tomcat 4.01 just by installing the soap.war file. Glenn -- Chris Malley PixelZoom, Inc. Voice: +1.303.494.8849 835 Orman Drive EMail: [EMAIL PROTECTED] Boulder CO 80303-2616 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat classloader problem?
Chris Malley wrote: [...] I'm experiencing a problem with SOAP message-style services when using Tomcat 4.01. When trying to access any message-style SOAP service, my client receives a no signature match fault. [...] Remy Maucherat wrote: [...] Moving soap.jar to $CATALINA_HOME/webapps/soap/WEB-INF/lib/soap.jar should solve the problem, and could be used as a workaround. Alternately, you can remove from $CATALINA_HOME/webapps/soap/WEB-INF/classes/ the classes which are also present in the JAR. Glenn Nielsen wrote: I agree with Remy, we use soap2.2 in Tomcat 4.01 just by installing the soap.war file. Glenn Glenn: Are you using message-style SOAP services, or RPC-style? Using only soap.war does indeed work just fine for RPC-style, but I get the SOAP fault shown below for message-style services; org.apache.soap.Envelope isn't found. Suggestions? -Chris ?xml version='1.0' encoding='UTF-8'? SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance; xmlns:xsd=http://www.w3.org/1999/XMLSchema; SOAP-ENV:Body SOAP-ENV:Fault faultcodeSOAP-ENV:Server/faultcode faultstringException while handling service request: org/apache/soap/Envelope /faultstring faultactor/soap/servlet/messagerouter/faultactor detail stackTracejava.lang.NoClassDefFoundError: org/apache/soap/Envelope at java.lang.Class.getMethod0(Native Method) at java.lang.Class.getMethod(Class.java:888) at org.apache.soap.util.MethodUtils.getEntryPoint(MethodUtils.java:114) at org.apache.soap.util.MethodUtils.getMethod(MethodUtils.java:548) at org.apache.soap.util.MethodUtils.getMethod(MethodUtils.java:528) [...] at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1011) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1106) at java.lang.Thread.run(Thread.java:484) /stackTrace /detail /SOAP-ENV:Fault /SOAP-ENV:Body /SOAP-ENV:Envelope -- Chris Malley PixelZoom, Inc. Voice: +1.303.494.8849 835 Orman Drive EMail: [EMAIL PROTECTED] Boulder CO 80303-2616 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5181] - HttpConnector [8080] No processor available, rejecting this connection
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=5181. 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=5181 HttpConnector [8080] No processor available, rejecting this connection --- Additional Comments From [EMAIL PROTECTED] 2001-11-30 11:23 --- You can change the max and min processors till the cow come home it ignore these. Why don't you guys get a loadrunner and try it yourselves. You should see the problem right aways -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5181] - HttpConnector [8080] No processor available, rejecting this connection
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=5181. 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=5181 HttpConnector [8080] No processor available, rejecting this connection --- Additional Comments From [EMAIL PROTECTED] 2001-11-30 11:40 --- FYI this is on Linux Redhat 7.0 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[PATCH] Watchdog-4.0 -- New Tests tests.javax_servlet.Error
New tests for verification of error page handling by the container.
The tests validate the use of dynamic and static resources as error
pages and validate that the appropriate request parameters are set
depending on the circumstances when the error resource is dynamic.
The attached .gz file can be untarred in the root directory of the
watchdog distribution and all new files will be put into the proper
directories. Also attached are patches to the servlet-tests web
application's web.xml, and the servlet-gtest.xml file.
Comments are welcome.
-rl
javax_servlet_Error.tar.gz
Description: GNU Zip compressed data
Index: servlet-gtest.xml
===
RCS file: /home/cvspublic/jakarta-watchdog-4.0/src/conf/servlet-gtest.xml,v
retrieving revision 1.19
diff -u -r1.19 servlet-gtest.xml
--- servlet-gtest.xml 2001/07/20 23:07:56 1.19
+++ servlet-gtest.xml 2001/11/30 20:23:12
@@ -586,6 +586,49 @@
debug=0 host=${host} port=${port}
goldenFile=${wgdir}/javax_servlet/UnavailableException/UnavailableException_Constructor2Test.html
/
+ !-- javax_servlet_Error tests --
+
+gtest request=GET /servlet-tests/ServletToServletErrorPageTest HTTP/1.0
+debug=0 host=${host} port=${port}
+goldenfile=${wgdir}/javax_servlet/Error/ServletToServletErrorPageTest.html
+testName=ServletToServletErrorPageTest
+assertion=Servlet error handlers can be installed for specific Exception
+types.
+testStrategy=The target servlet will generage a
+java.lang.ArithmeticException. The Servlet error page should display non-null values
+for status_code, exception_type, message, exception, request_uri, and servlet_name
+/
+
+gtest request=GET /servlet-tests/ServletToServletError501PageTest HTTP/1.0
+debug=0 host=${host} port=${port}
+
+goldenfile=${wgdir}/javax_servlet/Error/ServletToServletError501PageTest.html
+testName=ServletToServletError501PageTest
+assertion=Servlet error handlers can be installed for specific HTTP status
+codes.
+testStrategy=The target servlet will class HttpServletResponse.sendError(
+int status, String message ). The Servlet error page should display non-null values
+for status_code, message, request_uri, and servlet_name
+/
+
+gtest request=GET /servlet-tests/ServletToJSPErrorPageTest HTTP/1.0
+debug=0 host=${host} port=${port}
+goldenfile=${wgdir}/javax_servlet/Error/ServletToJSPErrorPageTest.html
+testName=ServletToJSPErrorPageTest
+assertion=JSP error handlers can be installed for specific Exception types.
+testStrategy=The target servlet will generage a
+java.lang.ArrayIndexOutOfBoundsException. The JSP error page should display non-null
+values for status_code, exception_type, message, exception, request_uri, and
+servlet_name
+/
+
+
+gtest request=GET /servlet-tests/ServletToJSPError502PageTest HTTP/1.0
+debug=0 host=${host} port=${port}
+goldenfile=${wgdir}/javax_servlet/Error/ServletToJSPError502PageTest.html
+testName=ServletToJSPError502PageTest
+assertion=JSP error handlers can be installed for specific HTTP status
+codes.
+testStrategy=The target servlet will generage a
+java.lang.ArrayIndexOutOfBoundsException. The JSP error page should display non-null
+values for status_code, message, request_uri, and servlet_name
+/
+
+
+gtest request=GET /servlet-tests/ServletToHTMLErrorPageTest HTTP/1.0
+debug=0 host=${host} port=${port}
+goldenfile=${wgdir}/javax_servlet/Error/ServletToHTMLErrorPageTest.html
+testName=ServletToHTMLErrorPageTest
+assertion=Static HTML page error handlers can be installed for specific
+Exception types.
+testStrategy=The target servlet will generage a
+java.lang.NumberFormatException. The static HTML error page should be returned to
+the client.
+/
!-- javax_servlet_http_Cookie tests --
Index: web.xml
===
RCS file:
/home/cvspublic/jakarta-watchdog-4.0/src/server/servlet-tests/WEB-INF/web.xml,v
retrieving revision 1.3
diff -u -r1.3 web.xml
--- web.xml 2000/12/22 18:59:14 1.3
+++ web.xml 2001/11/30 20:23:35
@@ -242,6 +242,71 @@
/servlet-class
/servlet
+ !-- Error --
+
+ servlet
+servlet-name
+ServletToServletErrorPageTest
+/servlet-name
+servlet-class
+tests.javax_servlet.Error.ServletToServletErrorPageTestServlet
+/servlet-class
+ /servlet
+
+ servlet
+servlet-name
+ServletToServletError501PageTest
+/servlet-name
+servlet-class
+tests.javax_servlet.Error.ServletToServletError501PageTestServlet
+/servlet-class
+ /servlet
+
+ servlet
+servlet-name
+JSPErrorPage
+/servlet-name
+jsp-file
+/tests/javax_servlet/Error/JSPErrorPage.jsp
+/jsp-file
cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/resources messages.properties messages_es.properties messages_ja.properties
larryi 01/11/30 14:17:40
Modified:jasper/src/share/org/apache/jasper Tag: tomcat_40_branch
EmbededServletOptions.java JspC.java Options.java
jasper/src/share/org/apache/jasper/compiler Tag:
tomcat_40_branch Compiler.java JavaCompiler.java
JikesJavaCompiler.java SunJavaCompiler.java
jasper/src/share/org/apache/jasper/resources Tag:
tomcat_40_branch messages.properties
messages_es.properties messages_ja.properties
Log:
For the few who need it, add a classdebuginfo init parameter to enable
compiling the class file with debugging information.
Revision ChangesPath
No revision
No revision
1.6.2.1 +24 -3
jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/EmbededServletOptions.java
Index: EmbededServletOptions.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/EmbededServletOptions.java,v
retrieving revision 1.6
retrieving revision 1.6.2.1
diff -u -r1.6 -r1.6.2.1
--- EmbededServletOptions.java2001/02/04 01:03:28 1.6
+++ EmbededServletOptions.java2001/11/30 22:17:39 1.6.2.1
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/EmbededServletOptions.java,v
1.6 2001/02/04 01:03:28 glenn Exp $
- * $Revision: 1.6 $
- * $Date: 2001/02/04 01:03:28 $
+ * $Header:
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/EmbededServletOptions.java,v
1.6.2.1 2001/11/30 22:17:39 larryi Exp $
+ * $Revision: 1.6.2.1 $
+ * $Date: 2001/11/30 22:17:39 $
*
*
*
@@ -106,6 +106,11 @@
public boolean sendErrorToClient = false;
/**
+ * Do we want to include debugging information in the class file?
+ */
+public boolean classDebugInfo = false;
+
+/**
* I want to see my generated servlets. Which directory are they
* in?
*/
@@ -173,6 +178,13 @@
}
/**
+ * Should class files be compiled with debug information?
+ */
+public boolean getClassDebugInfo() {
+return classDebugInfo;
+}
+
+/**
* Class ID for use in the plugin tag when the browser is IE.
*/
public String getIeClassId() {
@@ -257,6 +269,15 @@
else if (senderr.equalsIgnoreCase(false))
this.sendErrorToClient = false;
else Constants.message (jsp.warning.sendErrToClient, Logger.WARNING);
+}
+
+String debugInfo = config.getInitParameter(classdebuginfo);
+if (debugInfo != null) {
+if (debugInfo.equalsIgnoreCase(true))
+this.classDebugInfo = true;
+else if (debugInfo.equalsIgnoreCase(false))
+this.classDebugInfo = false;
+else Constants.message (jsp.warning.classDebugInfo, Logger.WARNING);
}
String ieClassId = config.getInitParameter(ieClassId);
1.12.2.1 +8 -3 jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/JspC.java
Index: JspC.java
===
RCS file: /home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/JspC.java,v
retrieving revision 1.12
retrieving revision 1.12.2.1
diff -u -r1.12 -r1.12.2.1
--- JspC.java 2001/09/18 00:16:34 1.12
+++ JspC.java 2001/11/30 22:17:39 1.12.2.1
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/JspC.java,v 1.12
2001/09/18 00:16:34 craigmcc Exp $
- * $Revision: 1.12 $
- * $Date: 2001/09/18 00:16:34 $
+ * $Header:
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/JspC.java,v 1.12.2.1
2001/11/30 22:17:39 larryi Exp $
+ * $Revision: 1.12.2.1 $
+ * $Date: 2001/11/30 22:17:39 $
*
*
*
@@ -181,6 +181,11 @@
return true;
}
+public boolean getClassDebugInfo() {
+// compile with debug info
+return false;
+}
+
public String getIeClassId() {
return ieClassId;
}
1.6.2.1 +8 -3
jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/Options.java
Index: Options.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/Options.java,v
retrieving revision 1.6
retrieving revision 1.6.2.1
diff -u -r1.6 -r1.6.2.1
--- Options.java 2001/02/04 01:04:11 1.6
+++ Options.java 2001/11/30 22:17:39 1.6.2.1
@@ -1,7 +1,7 @@
/*
cvs commit: jakarta-tomcat-4.0/catalina/src/conf web.xml
larryi 01/11/30 14:18:44 Modified:catalina/src/conf Tag: tomcat_40_branch web.xml Log: Document the classdebuginfo init parameter added to Jasper. Revision ChangesPath No revision No revision 1.22.2.8 +3 -0 jakarta-tomcat-4.0/catalina/src/conf/web.xml Index: web.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/conf/web.xml,v retrieving revision 1.22.2.7 retrieving revision 1.22.2.8 diff -u -r1.22.2.7 -r1.22.2.8 --- web.xml 2001/11/21 17:37:36 1.22.2.7 +++ web.xml 2001/11/30 22:18:44 1.22.2.8 @@ -91,6 +91,9 @@ !-- generated servlets? [Created dynamically -- !-- based on the current web application] -- !-- -- + !-- classdebuginfo Should the class file be compiled with -- + !-- debugging information? [false]-- + !-- -- !-- ieClassId The class-id value to be sent to Internet -- !-- Explorer when using jsp:plugin tags. -- !-- [clsid:8AD9C840-044E-11D1-B3E9-00805F499D93] -- -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat/src/share/org/apache/jasper/resources messages.properties messages_es.properties messages_fr.properties
larryi 01/11/30 14:20:07
Modified:src/share/org/apache/jasper/resources messages.properties
messages_es.properties messages_fr.properties
Log:
Fix the case of the classdebuginfo init parameter in warning message.
Revision ChangesPath
1.26 +2 -2
jakarta-tomcat/src/share/org/apache/jasper/resources/messages.properties
Index: messages.properties
===
RCS file:
/home/cvs/jakarta-tomcat/src/share/org/apache/jasper/resources/messages.properties,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- messages.properties 2001/06/11 03:42:29 1.25
+++ messages.properties 2001/11/30 22:20:07 1.26
@@ -1,4 +1,4 @@
-# $Id: messages.properties,v 1.25 2001/06/11 03:42:29 larryi Exp $
+# $Id: messages.properties,v 1.26 2001/11/30 22:20:07 larryi Exp $
#
# Default localized string information
# Localized this the Default Locale as is en_US
@@ -113,7 +113,7 @@
largeFile. Will use the default value of \true\
jsp.warning.mappedFile=Warning: Invalid value for the initParam mappedFile. Will
use the default value of \false\
jsp.warning.sendErrToClient=Warning: Invalid value for the initParam
sendErrToClient. Will use the default value of \false\
-jsp.warning.classDebugInfo=Warning: Invalid value for the initParam classDebugInfo.
Will use the default value of \false\
+jsp.warning.classDebugInfo=Warning: Invalid value for the initParam classdebuginfo.
Will use the default value of \false\
jsp.error.badtaglib=Unable to open taglibrary {0} : {1}
jsp.error.badGetReader=Cannot create a reader when the stream is not buffered
jsp.warning.unknown.element.in.TLD=Warning: Unknown element {0} in TLD
1.11 +2 -2
jakarta-tomcat/src/share/org/apache/jasper/resources/messages_es.properties
Index: messages_es.properties
===
RCS file:
/home/cvs/jakarta-tomcat/src/share/org/apache/jasper/resources/messages_es.properties,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- messages_es.properties2001/02/04 22:06:01 1.10
+++ messages_es.properties2001/11/30 22:20:07 1.11
@@ -1,4 +1,4 @@
-# $Id: messages_es.properties,v 1.10 2001/02/04 22:06:01 nacho Exp $
+# $Id: messages_es.properties,v 1.11 2001/11/30 22:20:07 larryi Exp $
#
# Default localized string information
# Localized para Locale es_ES
@@ -107,7 +107,7 @@
jsp.warning.largeFile=Aviso: valor incorrecto para el initParam largeFile. se usara
el valor por defecto de \true\
jsp.warning.mappedFile=Aviso: valor incorrecto para the initParam mappedFile. se
usara el valor por defecto de \false\
jsp.warning.sendErrToClient=Aviso: valor incorrecto para the initParam
sendErrToClient. se usara el valor por defecto de \false\
-jsp.warning.classDebugInfo=Aviso: valor incorrecto para the initParam
classDebugInfo. se usara el valor por defecto de \false\
+jsp.warning.classDebugInfo=Aviso: valor incorrecto para the initParam
classdebuginfo. se usara el valor por defecto de \false\
jsp.error.badtaglib=No se puede abrir la libreria de tags {0} : {1}
jsp.error.badGetReader=No se puede crear un reader cuando el stream no tiene buffer
jsp.warning.unknown.element.in.TLD=Aviso: Elemento {0} desconocido en el TLD
1.5 +2 -2
jakarta-tomcat/src/share/org/apache/jasper/resources/messages_fr.properties
Index: messages_fr.properties
===
RCS file:
/home/cvs/jakarta-tomcat/src/share/org/apache/jasper/resources/messages_fr.properties,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- messages_fr.properties2001/02/16 09:50:42 1.4
+++ messages_fr.properties2001/11/30 22:20:07 1.5
@@ -1,4 +1,4 @@
-# $Id: messages_fr.properties,v 1.4 2001/02/16 09:50:42 hgomez Exp $
+# $Id: messages_fr.properties,v 1.5 2001/11/30 22:20:07 larryi Exp $
#
# Default localized string information
# Localized this the Default Locale as is fr_FR
@@ -109,7 +109,7 @@
jsp.warning.largeFile=Attention: Valeur invalide pour l''initParam de largeFile. La
valeur par défaut \true\ sera retenue
jsp.warning.mappedFile=Attention: Valeur invalide pour l''initParam mappedFile. La
valeur par défaut \false\ sera retenue
jsp.warning.sendErrToClient=Attention: Valeur invalide pour l''initParam
sendErrToClient. La valeur par défaut \false\ sera retenue
-jsp.warning.classDebugInfo=Attention: Valeur invalide pour l''initParam
classDebugInfo. La valeur par défaut \false\ sera retenue
+jsp.warning.classDebugInfo=Attention: Valeur invalide pour l''initParam
classdebuginfo. La valeur par défaut \false\ sera retenue
jsp.error.badtaglib=Impossible d''ouvrir la taglibrary {0} : {1}
Tomcat 4.0.1 and HTTP/1.1
All, I'm interested on the HTTP/1.1 implementation, however, I'm not sure if this has been implemented on both Tomcat 3.3 and Tomcat 4.0 or just 4.0. If it is implemented, does it support full HTTP/1.1 spec or not? If anyone knows the answer of this, please share it with me. Kindest Regards, Huy Tran -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/resources messages.properties messages_es.properties messages_ja.properties
Remy,
Since for now SAS will be using Tomcat 3.3.x and 4.0.x in our IDE,
I added the classdebuginfo init parameter so it will be supported
by both. I have the same changes for 4.0 HEAD, but haven't tested
them yet. Since its time to go home, I'll commit them on Monday.
Thankfully the messages_ja.properties already had the new warning
string, so I didn't have worry about that one. :)
Cheers,
Larry
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 30, 2001 5:18 PM
To: [EMAIL PROTECTED]
Subject: cvs commit:
jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/resources
messages.properties messages_es.properties messages_ja.properties
larryi 01/11/30 14:17:40
Modified:jasper/src/share/org/apache/jasper Tag:
tomcat_40_branch
EmbededServletOptions.java JspC.java
Options.java
jasper/src/share/org/apache/jasper/compiler Tag:
tomcat_40_branch Compiler.java
JavaCompiler.java
JikesJavaCompiler.java SunJavaCompiler.java
jasper/src/share/org/apache/jasper/resources Tag:
tomcat_40_branch messages.properties
messages_es.properties messages_ja.properties
Log:
For the few who need it, add a classdebuginfo init
parameter to enable
compiling the class file with debugging information.
Revision ChangesPath
No revision
No revision
1.6.2.1 +24 -3
jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/EmbededS
ervletOptions.java
Index: EmbededServletOptions.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jaspe
r/EmbededServletOptions.java,v
retrieving revision 1.6
retrieving revision 1.6.2.1
diff -u -r1.6 -r1.6.2.1
--- EmbededServletOptions.java 2001/02/04 01:03:28 1.6
+++ EmbededServletOptions.java 2001/11/30 22:17:39 1.6.2.1
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jaspe
r/EmbededServletOptions.java,v 1.6 2001/02/04 01:03:28 glenn Exp $
- * $Revision: 1.6 $
- * $Date: 2001/02/04 01:03:28 $
+ * $Header:
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jaspe
r/EmbededServletOptions.java,v 1.6.2.1 2001/11/30 22:17:39
larryi Exp $
+ * $Revision: 1.6.2.1 $
+ * $Date: 2001/11/30 22:17:39 $
*
*
*
@@ -106,6 +106,11 @@
public boolean sendErrorToClient = false;
/**
+ * Do we want to include debugging information in the
class file?
+ */
+public boolean classDebugInfo = false;
+
+/**
* I want to see my generated servlets. Which
directory are they
* in?
*/
@@ -173,6 +178,13 @@
}
/**
+ * Should class files be compiled with debug information?
+ */
+public boolean getClassDebugInfo() {
+return classDebugInfo;
+}
+
+/**
* Class ID for use in the plugin tag when the browser is IE.
*/
public String getIeClassId() {
@@ -257,6 +269,15 @@
else if (senderr.equalsIgnoreCase(false))
this.sendErrorToClient = false;
else Constants.message
(jsp.warning.sendErrToClient, Logger.WARNING);
+}
+
+String debugInfo =
config.getInitParameter(classdebuginfo);
+if (debugInfo != null) {
+if (debugInfo.equalsIgnoreCase(true))
+this.classDebugInfo = true;
+else if (debugInfo.equalsIgnoreCase(false))
+this.classDebugInfo = false;
+else Constants.message
(jsp.warning.classDebugInfo, Logger.WARNING);
}
String ieClassId = config.getInitParameter(ieClassId);
1.12.2.1 +8 -3
jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/JspC.java
Index: JspC.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jaspe
r/JspC.java,v
retrieving revision 1.12
retrieving revision 1.12.2.1
diff -u -r1.12 -r1.12.2.1
--- JspC.java 2001/09/18 00:16:34 1.12
+++ JspC.java 2001/11/30 22:17:39 1.12.2.1
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jaspe
r/JspC.java,v 1.12 2001/09/18 00:16:34 craigmcc Exp $
- * $Revision: 1.12 $
- * $Date: 2001/09/18 00:16:34 $
+ * $Header:
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jaspe
r/JspC.java,v 1.12.2.1 2001/11/30 22:17:39 larryi Exp $
+ * $Revision: 1.12.2.1 $
+ * $Date:
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/net DefaultServerSocketFactory.java SSLServerSocketFactory.java
remm01/11/30 15:00:46
Modified:catalina/src/share/org/apache/catalina/net
DefaultServerSocketFactory.java
SSLServerSocketFactory.java
Log:
- Fix problem where connectors for TC 4 wouldn't run with TC 4.1.
Revision ChangesPath
1.6 +4 -4
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/net/DefaultServerSocketFactory.java
Index: DefaultServerSocketFactory.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/net/DefaultServerSocketFactory.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- DefaultServerSocketFactory.java 2001/10/17 02:33:46 1.5
+++ DefaultServerSocketFactory.java 2001/11/30 23:00:45 1.6
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/net/DefaultServerSocketFactory.java,v
1.5 2001/10/17 02:33:46 craigmcc Exp $
- * $Revision: 1.5 $
- * $Date: 2001/10/17 02:33:46 $
+ * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/net/DefaultServerSocketFactory.java,v
1.6 2001/11/30 23:00:45 remm Exp $
+ * $Revision: 1.6 $
+ * $Date: 2001/11/30 23:00:45 $
*
*
*
@@ -73,7 +73,7 @@
import java.security.UnrecoverableKeyException;
import java.security.KeyManagementException;
import java.security.cert.CertificateException;
-import org.apache.catalina.ServerSocketFactory;
+import org.apache.catalina.net.ServerSocketFactory;
/**
1.10 +1 -1
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/net/SSLServerSocketFactory.java
Index: SSLServerSocketFactory.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/net/SSLServerSocketFactory.java,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- SSLServerSocketFactory.java 2001/10/17 02:33:46 1.9
+++ SSLServerSocketFactory.java 2001/11/30 23:00:45 1.10
@@ -110,7 +110,7 @@
*/
public class SSLServerSocketFactory
-implements org.apache.catalina.ServerSocketFactory {
+implements org.apache.catalina.net.ServerSocketFactory {
// - Instance Variables
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Submission: Portable SSL Support
I've finished patching Tomcat to support both PureTLS and JSSE (and it would be trivial to add pretty much any other SSL implementation if there was a need). Essentially, what I did was take the current support for JSSE and generalize it so that it could support any implementation. This required adding a fair amount of abstraction. (1) Each implementation is encapsulated by a subclass of SSLImplementation. As before, PoolTCPConnector is responsible for detecting that SSL has been called for and loading up the right implementation but it does it by using SSLImplementation. (2) SSLImplementation.getInstance() automatically chooses whatever implementation is active. (There's a parameter to tell it to use a specific one). (3) In order to get a socket you first get the appropriate socketFactory from the SSLImplementation. You then use socketFactory.getSocket() as before. (4) All the special things you can do with an SSL socket are encapsulated in SSLSupport. SSLImplementation.getSSLSuport(Socket sock) lets you get the SSLSupport for a given socket. (5) Currently you can get the attributes: javax.servlet.request.cipher_suite javax.servlet.request.X509Certificate What's supposed to be at: javax.servlet.request.key_size is extremely vague. I'll implement it once I hear back from Sun about the value. (6) Changes to the doc to explain this stuff. The changes are of three types: (1) A patch file. (2) A mess of new source files which live in org/apache/tomcat/util/net. (3) The following file needs to be deleted from the repository: org/apache/tomcat/util/net/SSLSocketFactory.java Due to the size of the changes I've put the patch and new source files up at http://www.rtfm.com/tomcat-changes-20011130.tar.gz. If someone wants them mailed to the list I'm happy to do so. Note: These changes only work properly with the latest PureTLS snapshot: 20011130 (though they should work fine if you're compiling without PureTLS at all as well). -Ekr -- [Eric Rescorla [EMAIL PROTECTED]] Author of SSL and TLS: Designing and Building Secure Systems http://www.rtfm.com/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[PATCH] mod_jk for Apache 2.0 minor fixes
This patch contains minor fixes for mod_jk for Apache 2.0;
Most important is the change in prototype of jk_post_config
which used to be void but now needs to return success code,
also changes to types of some variables to better confirm to
Apache 2.0 types.
Let me know if you have any comments.
Julius
Index: mod_jk.c
===
RCS file:
/home/cvspublic/jakarta-tomcat-connectors/jk/native/apache-2.0/mod_jk.c,v
retrieving revision 1.37
diff -u -r1.37 mod_jk.c
--- mod_jk.c2001/11/21 00:09:21 1.37
+++ mod_jk.c2001/11/30 23:58:13
@@ -110,9 +110,8 @@
#define ADD_SSL_INFO
/* module MODULE_VAR_EXPORT jk_module; */
-AP_DECLARE_DATA module jk_module;
+AP_MODULE_DECLARE_DATA module jk_module;
-
typedef struct {
/*
@@ -326,7 +325,7 @@
/* Debug - try to get around rwrite */
while( ll 0 ) {
-long toSend=(llCHUNK_SIZE) ? CHUNK_SIZE : ll;
+size_t toSend=(llCHUNK_SIZE) ? CHUNK_SIZE : ll;
r = ap_rwrite((const char *)bb, toSend, p-r );
jk_log(main_log, JK_LOG_DEBUG,
writing %ld (%ld) out of %ld \n,toSend, r, ll );
@@ -535,7 +534,7 @@
}
if(conf-envvars_in_use) {
-apr_array_header_t *t = apr_table_elts(conf-envvars);
+const apr_array_header_t *t = apr_table_elts(conf-envvars);
if(t t-nelts) {
int i;
apr_table_entry_t *elts = (apr_table_entry_t *)t-elts;
@@ -563,7 +562,7 @@
s-num_headers = 0;
if(r-headers_in apr_table_elts(r-headers_in)) {
int need_content_length_header = (!s-is_chunked
s-content_length == 0) ? JK_TRUE : JK_FALSE;
-apr_array_header_t *t = apr_table_elts(r-headers_in);
+const apr_array_header_t *t = apr_table_elts(r-headers_in);
if(t t-nelts) {
int i;
apr_table_entry_t *elts = (apr_table_entry_t *)t-elts;
@@ -1514,7 +1513,7 @@
return;
}
-static void jk_post_config(apr_pool_t *pconf,
+static int jk_post_config(apr_pool_t *pconf,
apr_pool_t *plog,
apr_pool_t *ptemp,
server_rec *s)
@@ -1528,6 +1527,7 @@
init_jk( pconf, conf, s );
}
}
+ return OK;
}
/** Use the internal mod_jk mappings to find if this is a request for
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5218] New: - org.apache.jasper.JasperException: Unable to compile class for JSP
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=5218. 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=5218 org.apache.jasper.JasperException: Unable to compile class for JSP Summary: org.apache.jasper.JasperException: Unable to compile class for JSP Product: Tomcat 4 Version: 4.0.1 Final Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Blocker Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] This error appears when I was testing Cocoon2 (cocoon-2.0rc2.tar) and add a match in a pipeline section of the file sitemap.xmap with something like this: map:match pattern= map:generate type=jsp src=eventos/buscarEventos.jsp/ map:transform src=test/Semana.xslt/ map:serialize/ /map:match Basically a JSP that responds with some XML data and use a XSLT to process that XML data. When I try to used it I got an error like this: org.apache.cocoon.ProcessingException: SAXException JspGenerator.generate(): org.xml.sax.SAXParseException: The root element is required in a well-formed document. then I start searching for the cause and execute de JSP normally and Tomcat response was: Incompatible type for method. Explicit cast needed to convert java.lang.Throwable to java.lang.Exception. if (pageContext != null) pageContext.handlePageException(t); ^ 1 error at org.apache.jasper.compiler.Compiler.compile(Compiler.java:284) at org.apache.jasper.servlet.JspServlet.loadJSP(JspServlet.java:546) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary (JspServlet.java:177) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service (JspServlet.java:189) at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:382) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke (StandardWrapperValve.java:243) at org.apache.catalina.core.StandardPipeline.invokeNext (StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke (StandardContextValve.java:201) at org.apache.catalina.core.StandardPipeline.invokeNext (StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke (StandardContext.java:2344) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:164) at org.apache.catalina.core.StandardPipeline.invokeNext (StandardPipeline.java:566) at org.apache.catalina.valves.ErrorDispatcherValve.invoke (ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext (StandardPipeline.java:564) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext (StandardPipeline.java:564) at org.apache.catalina.valves.AccessLogValve.invoke (AccessLogValve.java:462) at org.apache.catalina.core.StandardPipeline.invokeNext (StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:163) at org.apache.catalina.core.StandardPipeline.invokeNext (StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.connector.http.HttpProcessor.process (HttpProcessor.java:1011) at org.apache.catalina.connector.http.HttpProcessor.run (HttpProcessor.java:1106) at java.lang.Thread.run(Thread.java:484) I downloaded the source of Tomcat jakarta-tomcat-4.0.1-src.tar and search for that line and I found it so I patch it ( File:
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/config ajp.xml
remm01/11/30 17:12:31 Modified:webapps/tomcat-docs/config ajp.xml Log: - Merge some of the relevant documentation. Please review and expand. Revision ChangesPath 1.3 +229 -2jakarta-tomcat-4.0/webapps/tomcat-docs/config/ajp.xml Index: ajp.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/ajp.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- ajp.xml 2001/11/30 06:23:13 1.2 +++ ajp.xml 2001/12/01 01:12:31 1.3 @@ -144,12 +144,239 @@ section name=Configuration HOWTOs + subsection name=Apache + + subsection name=Introduction + +pThis section explains how to connect Tomcat 4 to the popular +open source web server, Apache. It was originally part of +iTomcat: A Minimalistic User's Guide/i by Gal Shachor, but +has been split off for organizational reasons. It should be +considered a bwork in progress/b. Since the Tomcat source +tree is constantly changing, the information herein may be out +of date. The only definitive reference at this point is the a +href=http://jakarta.apache.org/site/sourceindex.html;source +code/a./p + + /subsection + + subsection name=Installation + +subsection name=Needed Components + + pIn a nutshell a web server is waiting for client HTTP requests. + When these requests arrive the server does whatever is needed to + serve the requests by providing the necessary content. Adding a + servlet container may somewhat change this behavior. Now the web + server needs also to perform the following:/p + + ul +liLoad the servlet container adapter library +and initialize it (prior to serving requests). /li +liWhen a request arrives, it needs to check and see if a certain +request belongs to a servlet, if so it needs to let the adapter +take the request and handle it./li + /ul + + pThe adapter on the other hand needs to know what requests it is + going to serve, usually based on some pattern in the request URL, + and to where to direct these requests./p + + pThings are even more complex when the user wants to set + a configuration that uses virtual hosts, or when they want multiple + developers to work on the same web server but on different servlet + container JVMs. We will cover these two cases + in the advanced sections./p + +/subsection + +subsection name=mod_jk Terminology + + pThe following terms are used in this section:/p + + ul + listrongWorker process/strong - A worker is a Tomcat + instance that is running to serve servlet requests coming + from the web server. In most cases there is only a single worker + (the one and only Tomcat process) but sometimes you will run + multiple workers to achieve load balancing or site partitioning. + Each worker is identified to the web server by the host were + it is located, the port where it listens and the communication + protocol used to exchange messages./li + listrongIn-Process Worker/strong - This is a special + worker. Instead of working with a Tomcat process residing on + another process, the web server opens a JVM and executes + Tomcat inside the web server process address space. + Our discussion in this document is not going to get into this + special worker. Note: Tomcat 4 can't be run as this type of + worker at the moment./li + listrongWeb Server Plug-in/Tomcat Redirector/strong - + For Tomcat to cooperate with any web server it needs an agent + to reside in the web server and send him servlet requests. + This is the web server plug-in, and in our case the web server + plug-in is mod_jk. The redirector usually comes in the shape of + a DLL or shared object module that you plug into + the web server./li + listrongPlug-in Configuration/strong - We need to + configure the web server plug-in so that it knows where + the different Tomcat workers are and to which of them + it should forward requests. This information, accompanied with + some internal parameter, such as the log level, comprises + the plug-in configuration./li + listrongWeb Server Configuration/strong -
[FAQ] jGuru FAQ Update
jGuru maintains FAQs and Forums on Servlets, JSP, and Tomcat (as well as many other Java topics). Here is an automated update on recent postings to Tomcat-related FAQs. Please direct flames and feedback to [EMAIL PROTECTED] . - Alex ++ JavaServer Pages (JSP) FAQ: http://www.jguru.com/faq/JSP My JSP application runs fine sometimes, but on other instances, when i try to refresh the page, the server outputs only a part of the page. In the Tomcat Console, I see IOException, Connection reset by peer. If I keep refreshing the page, it loads the complete page at some point. Otherwise I have to restart the server and try again. Any suggestions on how I can overcome this? http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=568124 I'm working on the chinese version of our project. I already set the charset to GB2312 for all jsp pages to display simplified chinese correctly. Now I need to pass data within forms between jsp pages. In the english version, we used request.getParameter to receive these data, but after changing the charset setting, it causes the get data to be unreadable. Any solutions on how I can overcome this problem? http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=568118 I am getting an Out of Memory error running my JSP applications under Tomcat. How do I increase the default JVM heap size settings that Tomcat uses upon startup? http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=568115 I have developed a site in JSP. Whenever I type www.name.com in address bar the url changes to www.name.com/index.jsp. How do I prevent the index.jsp from showing up in the address bar? http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=568108 I have got this error when I tried to access the Tomcat welcome page at http://localhost:8080 using Tomcat 4.0. p font size=3pre Starting service Tomcat-Standalone Apache Tomcat/4.0.1 Starting service Tomcat-Apache Apache Tomcat/4.0.1 java.lang.NoSuchMethodError at org.apache.catalina.connector.ResponseStream.flush(ResponseStream.java:244) at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:245) at java.io.PrintWriter.flush(PrintWriter.java:120) at org.apache.catalina.connector.ResponseWriter.flush(ResponseWriter.java:125) at org.apache.catalina.connector.ResponseBase.finishResponse(ResponseBase.java:481) at org.apache.catalina.connector.HttpResponseBase.finishResponse(HttpResponseBase.java:229) at org.apache.catalina.connector.http.HttpResponseImpl.finishResponse(HttpResponseImpl.java:288) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1038) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1106) at java.lang.Thread.run(Thread.java:484) /pre/font/p pThe server starts up fine. The error comes up when I access the welcome page. All my other JSP codes residing in Tomcat cannot be access as a result of this problem./pbr pI have tried to reinstall the entire Tomcat Server and JDK 1.3 to ensure that everything is the default setting but the problem still persists. This problem came all of a sudden. There was no problem at all in the first place./p http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=568095 How can I read a text file from JSP page? http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=566162 How do i specify Application-level variables in JSP? p I want to do something similar to the global.asa in ASP, where I can specify application and session variables. http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=566160 How can I read a text file from a JSP page? http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=566159 Are global variables in the included file (using lt;jsp:include/gt;) available in the file that includes it? http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=566158 I have a problem and I'm hoping you can help me. I have a jsp that's displaying data, which length depends on the user. It takes up to 10 minutes sometimes to display a page. I don't want to break my page into multiple pages, but what I want to do is to display line by line on the screen as the data is being read. What happens now, is the browser waits until all the data is processed and then displays a page. Any ideas how to do this? http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=565046 I want to download files within a client browser from a web server using JSP. How can I do this? http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=563827 ++ Servlets FAQ: http://www.jguru.com/faq/Servlets I have got this error when I tried to access the Tomcat welcome page at http://localhost:8080 using Tomcat 4.0. p font size=3pre Starting service Tomcat-Standalone Apache Tomcat/4.0.1 Starting service Tomcat-Apache Apache Tomcat/4.0.1
WG: TC3.3 updating a webapp without killing sessions
Hi, since Costin is currently refactoring mod_jk in jakarta-tomcat-connectors I want to throw in our usage scenario. We are abusing the loadbalancing feature of mod_jk to switch tomcats on the fly in order to be able to make application updates without killing our curreent user sessions. See discussion below from tomcat-user This feature (graceful restart) was present in jserv and is still missing in mod_jk/Tomcat3.3 as far as I know. Below are references to the archive where Michael Kuz has sent a patch to decouple this feature from the lbfactor (introducing an active flag). So please keep in mind the requirement to be able to update Webapps in a farm of Tomcats without killing active sessions. Thanks, Hans -Ursprüngliche Nachricht- Von: Hans Schmid [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 28. November 2001 18:21 An: Tomcat Users List Betreff: AW: TC3.3 updating a webapp without killing sessions Thanks Larry, perhaps a lbfactor of 0.1 or so would do the job for us. We could probably live with 1 out of 10 sessions beeing sent to the wrong Tomcat and beeing killed if this instance shuts down. Should this be discussed in tomcat-dev ? I remember a patch from early this year which tried to fix this (check the archives) but did never make it into the release It tried to add a flag called 'active' in the worker.properties file for each worker instead of misusing the lbfactor for this. ajp13-01... lbfactor=1 active=0 and ajb13-02... lbfactor=1 active=1 see http://w6.metronet.com/~wjm/tomcat/2001/Jan/msg00102.html and http://w6.metronet.com/~wjm/tomcat/2001/Jan/msg00114.html for the patch which might be a little bit outdated -Ursprüngliche Nachricht- Von: Larry Isaacs [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 28. November 2001 15:00 An: 'Tomcat Users List' Betreff: RE: TC3.3 updating a webapp without killing sessions I assume the value or lbfactor is requested to be 0 because 1/lbfactor is calculated during initialization. Since this is done with doubles, it may generate an internal representation for infinity rather than a division by zero error. I don't have a complete understanding of what mod_jk does internally for loadbalancing, but your approach seems like it should work. A brief scan of the codes shows that some updates to mod_jk would be needed to insure that lbfactor=0 means only use this worker when mandated by session routing. There isn't much logging around the choice of worker. Perhaps adding some logging would help determine why requests are being routed to the lbfactor=0 Tomcat when session routing shouldn't be a factor. Hope this helps. Cheers, Larry -Original Message- From: Hans Schmid [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 28, 2001 4:25 AM To: Tomcat-User Subject: TC3.3 updating a webapp without killing sessions Hi, We try to make a workaround for the following problems: 1.) memory management 2.) application update 3.) do not kill active sessions Perhaps someone can comment on the startegy and answer some questions. Our environment: Tomcat 3.3 final with mod_jk Apache 1.3.19 on Solaris 2.7 Sparc Our problem: ever growing cache until memory runs out (clearly an application problem) plus soft updates to our application without killing actiove sessions The idea: when a certain ammount of memory is reached by the tomcat java process, start up a second Tomcat and route all new requests to the second instance while existing sessions should phase out on the first instance. If no more sessions are active on the original Tomcat, shut it down (currently we just shut it down 30 minutes after the second Tomcat started up) How to do it with mod_jk: We have two versions of a worker.properties. Before we start up our second tomcat, we switch a link to point to the other version. Both versions of the worker.property file have a loadbalancer worker defined: First version: worker.list=loadbalancer worker.ajp13-01.port=11009 worker.ajp13-01.host=tomcathost worker.ajp13-01.type=ajp13 worker.ajp13-01.lbfactor=1 - important worker.ajp13-02.port=11019 worker.ajp13-02.host=tomcathost worker.ajp13-02.type=ajp13 worker.ajp13-02.lbfactor=0 - important worker.loadbalancer.type=lb worker.loadbalancer.balanced_workers=ajp13-01, ajp13-02 Second version: worker.list=loadbalancer worker.ajp13-01.port=11009 worker.ajp13-01.host=tomcathost worker.ajp13-01.type=ajp13 worker.ajp13-01.lbfactor=0 - important worker.ajp13-02.port=11019 worker.ajp13-02.host=tomcathost worker.ajp13-02.type=ajp13 worker.ajp13-02.lbfactor=1 - important worker.loadbalancer.type=lb worker.loadbalancer.balanced_workers=ajp13-02, ajp13-01 We just try to switch the lbfactor from 1 to 0 for the first Tomcat and from 0 to 1 for the second Tomcat. after the switch we do a graceful
SSL and URL rewriting with Tomcat 3.2.3
The problem is that you need to have the class com.sun.net.ssl.internal.www.protocol.Handler available so that the Tomcat implementation class of HttpServletResponse works out that it should encode urls. To do this: 1. put jsse.jar in %JAVA_HOME%\jre\lib\ext 2. add this jar to your classpath for Tomcat 3. add the environment variable TOMCAT_OPTS with value: -Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5181] -
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=5181. 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=5181 [EMAIL PROTECTED] changed: What|Removed |Added Summary|HttpConnector [8080] No | |processor available,| |rejecting this connection | --- Additional Comments From [EMAIL PROTECTED] 2001-11-30 17:47 --- Thanks for the details, it really helps a lot. AFAIK, it works very well for me; unless somebody can confirm the problem, I'll close it. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5220] New: - Problem with mod_webapp.so getting confused with tomcat restart
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=5220. 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=5220 Problem with mod_webapp.so getting confused with tomcat restart Summary: Problem with mod_webapp.so getting confused with tomcat restart Product: Tomcat 4 Version: 4.0.1 Final Platform: Other OS/Version: Linux Status: NEW Severity: Enhancement Priority: Other Component: WARP Connector AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hello, There seems to be a problem with the mod_webapp.so getting an Web- Application not yet deployed error when tomcat hasn't fully started yet. This happens during system reboots when tomcat hasn't finished fully deploying it's applications while at the same time, apache has already started. It seems to me that mod_webapp should be retrying the status check when a request is made to see if the webapps are up instead of just outright failing. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/webapps/admin login.jsp
patrickl01/11/30 19:09:19
Modified:webapps/admin login.jsp
Log:
Make redirect to login.jsp smoother if a timeout occurs. Now, we redirect to . so
that, once you relogin after a timeout, the user will be forward to the welcome page.
Revision ChangesPath
1.4 +1 -1 jakarta-tomcat-4.0/webapps/admin/login.jsp
Index: login.jsp
===
RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/admin/login.jsp,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- login.jsp 2001/11/13 01:00:03 1.3
+++ login.jsp 2001/12/01 03:09:19 1.4
@@ -13,7 +13,7 @@
!--
if (window.self != window.top) {
- window.open(window.location, _top);
+ window.open(., _top);
}
// --
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit:jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/coreLocalStrings.properties
From: [EMAIL PROTECTED]
Subject: cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core
LocalStrings.properties
Date: 29 Nov 2001 03:11:04 -
+naming.invalidEnvEntryType=Environment entry {0} has an invalid type
+naming.invalidEnvEntryValue=Environment entry (0) has an invalid value
Would you replace the (0) with {0}? This mistype isn't fixed in
the current CVS.
Kazuhiro Kazama ([EMAIL PROTECTED]) NTT Network Innovation Laboratories
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core LocalStrings.properties
remm01/11/30 20:14:04
Modified:catalina/src/share/org/apache/catalina/core
LocalStrings.properties
Log:
- Fix typo.
Submitted by Kazuhiro Kazama
Revision ChangesPath
1.43 +1 -1
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/LocalStrings.properties
Index: LocalStrings.properties
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/LocalStrings.properties,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- LocalStrings.properties 2001/11/29 03:11:04 1.42
+++ LocalStrings.properties 2001/12/01 04:14:04 1.43
@@ -28,7 +28,7 @@
naming.bindFailed=Failed to bind object: {0}
naming.unbindFailed=Failed to unbind object: {0}
naming.invalidEnvEntryType=Environment entry {0} has an invalid type
-naming.invalidEnvEntryValue=Environment entry (0) has an invalid value
+naming.invalidEnvEntryValue=Environment entry {0} has an invalid value
naming.namingContextCreationFailed=Creation of the naming context failed: {0}
standardContext.alreadyStarted=Context has already been started
standardContext.applicationListener=Error configuring application listener of class
{0}
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
PATCH:jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/coreLocalStrings_ja.properties
Thank you, Remmy.
And this is a patch file for japanese translations.
Kazuhiro Kazama ([EMAIL PROTECTED]) NTT Network Innovation Laboratories
Index: catalina/src/share/org/apache/catalina/core/LocalStrings_ja.properties
===
RCS file:
/home/cvspublic/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/LocalStrings_ja.properties,v
retrieving revision 1.3
diff -c -u -r1.3 LocalStrings_ja.properties
--- catalina/src/share/org/apache/catalina/core/LocalStrings_ja.properties
2001/09/26 17:51:52 1.3
+++ catalina/src/share/org/apache/catalina/core/LocalStrings_ja.properties
+2001/12/01 04:18:20
@@ -25,6 +25,11 @@
httpHostMapper.container=\u3053\u306e\u30b3\u30f3\u30c6\u30ca\u306fStandardHost\u3067\u306f\u3042\u308a\u307e\u305b\u3093
interceptorValve.alreadyStarted=InterceptorValve\u306f\u3001\u3059\u3067\u306b\u8d77\u52d5\u3055\u308c\u3066\u3044\u307e\u3059
interceptorValve.notStarted=InterceptorValve\u306f\u3001\u307e\u3060\u8d77\u52d5\u3055\u308c\u3066\u3044\u307e\u305b\u3093
+naming.bindFailed=\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u306e\u30d0\u30a4\u30f3\u30c9\u306b\u5931\u6557\u3057\u307e\u3057\u305f:
+ {0}
+naming.unbindFailed=\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u306e\u30a2\u30f3\u30d0\u30a4\u30f3\u30c9\u306b\u5931\u6557\u3057\u307e\u3057\u305f:
+ {0}
+naming.invalidEnvEntryType=\u74b0\u5883\u30a8\u30f3\u30c8\u30ea {0}
+\u306f\u3001\u7121\u52b9\u306a\u578b\u3092\u6301\u3063\u3066\u3044\u307e\u3059
+naming.invalidEnvEntryValue=\u74b0\u5883\u30a8\u30f3\u30c8\u30ea {0}
+\u306f\u7121\u52b9\u306a\u5024\u3092\u6301\u3063\u3066\u3044\u307e\u3059
+naming.namingContextCreationFailed=\u540d\u524d\u304c\u4ed8\u3051\u3089\u308c\u305f\u30b3\u30f3\u30c6\u30ad\u30b9\u30c8\u306e\u751f\u6210\u306b\u5931\u6557\u3057\u307e\u3057\u305f:
+ {0}
standardContext.alreadyStarted=\u30b3\u30f3\u30c6\u30ad\u30b9\u30c8\u306f\u3001\u3059\u3067\u306b\u8d77\u52d5\u3055\u308c\u3066\u3044\u307e\u3059
standardContext.applicationListener=\u30af\u30e9\u30b9 {0}
\u306e\u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3\u30ea\u30b9\u30ca\u306e\u8a2d\u5b9a\u4e2d\u306b\u30a8\u30e9\u30fc\u304c\u767a\u751f\u3057\u307e\u3057\u305f
standardContext.applicationSkipped=\u524d\u306e\u30a8\u30e9\u30fc\u306e\u305f\u3081\u306b\u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3\u30ea\u30b9\u30ca\u306e\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3092\u30b9\u30ad\u30c3\u30d7\u3057\u307e\u3059
@@ -72,10 +77,6 @@
standardContext.urlValidate=URL\u30c7\u30b3\u30fc\u30c9\u3055\u308c\u305f\u30ea\u30af\u30a8\u30b9\u30c8\u30d1\u30b9
{0} \u3092\u691c\u8a3c\u3067\u304d\u307e\u305b\u3093
standardContext.wrapper.error=JSP\u30d5\u30a1\u30a4\u30eb {0}
\u306f\u3001'/'\u3067\u958b\u59cb\u3057\u306a\u3051\u308c\u3070\u3044\u3051\u307e\u305b\u3093
standardContext.wrapper.warning=\u8b66\u544a: Servlet
2.3\u3067\u306f\u3001JSP\u30d5\u30a1\u30a4\u30eb {0}
\u306f\u3001'/'\u3067\u958b\u59cb\u3057\u306a\u3051\u308c\u3070\u3044\u3051\u307e\u305b\u3093
-standardContext.invalidEnvEntryValue={0}
\u74b0\u5883\u30a8\u30f3\u30c8\u30ea\u306f\u6307\u5b9a\u3055\u308c\u305f\u578b\u306b\u5bfe\u3057\u3066\u7121\u52b9\u306a\u5024\u3092\u6301\u3063\u3066\u3044\u307e\u3059
-standardContext.invalidEnvEntryType={0}
\u74b0\u5883\u30a8\u30f3\u30c8\u30ea\u306f\u3001\u7121\u52b9\u306a\u578b\u3092\u6301\u3063\u3066\u3044\u307e\u3059
-standardContext.bindFailed=\u540d\u524d\u306e\u30d0\u30a4\u30f3\u30c9\u64cd\u4f5c\u304c\u5931\u6557\u3057\u307e\u3057\u305f
: {0}
-standardContext.namingInitFailed=\u30b3\u30f3\u30c6\u30ad\u30b9\u30c8 {0}
\u306e\u540d\u524d\u304c\u4ed8\u3051\u3089\u308c\u305f\u30b3\u30f3\u30c6\u30ad\u30b9\u30c8\u306e\u521d\u671f\u5316\u4e2d\u306b\u30a8\u30e9\u30fc\u304c\u767a\u751f\u3057\u307e\u3057\u305f
standardEngine.alreadyStarted=\u30a8\u30f3\u30b8\u30f3\u306f\u3001\u3059\u3067\u306b\u8d77\u52d5\u3055\u308c\u3066\u3044\u307e\u3059
standardEngine.mappingError=\u30b5\u30fc\u30d0\u540d {0}
\u306e\u30de\u30c3\u30d4\u30f3\u30b0\u8a2d\u5b9a\u30a8\u30e9\u30fc\u3067\u3059
standardEngine.noHost=\u30b5\u30fc\u30d0\u540d {0}
\u306b\u4e00\u81f4\u3059\u308b\u30db\u30b9\u30c8\u304c\u5b58\u5728\u3057\u307e\u305b\u3093
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: tomcat 4.0.1 and persistent connection problem
Dear Sir I already did some research about this problem. But still be confused. I want to take advantage of the persistent connection of Http/1.1. In my experiement, if HTTP/1.1 client connects to the tomcat 4.0.1 Http/1.1 directly, the persistent connection can be established. However, it is usless because actually all companies employ http proxies. Furthermore, a lot of them such as the squid is a http/1.0 proxy. in my application, the client (http/1.1) - squid proxy(http/1.0) tomcat 4.0.1.(Http/1.1) I found that tomcat 4.0.1 always sends a FIN package after it sends the response even i send the Connection: Keep-Alive in the request header. Also, I know the tomcat does also received Connection: Keep-Alive header via proxy. I did a comparison between tomcat4.0.1 and apache 1.3.9, the results show that if If I add Connection: Keep-Alive header in the request, apache server will keep the connection alive even the proxy/client sends a HTTP/1.0 package. However, It seems that tomcat 4.0.1 doesn't support this feature. I think this feature isn't defined in specification, however, it is so important that it provide the only way(am i right?) to establish persistent connection in real world which is consisted of unexpected HTTP/1.0 proxies. I don't know whether my understanding is correct or not. Any comments are welcome. That's correct. Tomcat 4 doesn't support legacy HTTP/1.0 keepalive. As usual, if you want to have it fixed you can contribute patches. Keepalives over HTTP/1.0 are not that useful in a JSP / servlets environment, as in many many cases, the content-length of the response is not set. Overall, I think it's time for HTTP/1.0 to go away (1.1 has been around for some time now). Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Solved : ClassNotFound Exception when loading Tomcat 4.0.1 via URLClassLoader
Hi all,
I've used the following workaround to address this problem.
I've created an executable jar for my UI class, and have added the bootstrap.jar file
to the Class-Path manifest attribute. This works.
--- begin manifest fiel contents ---
Manifest-Version: 1.0
Main-Class: test.TCStart
Created-By: OESI
Class-Path: bin/bootstrap.jar bin/tools.jar
--- end manifest file contents ---
This lets me run the text.TCStart class, and load tomcat 4.0.1 and load tools.jar too.
What I'm planning to tackle next is asking the SystemClassLoader to load additional
jars, the URLs/path of which I shall read form a properties file.
Regards,
Sriram
--- Start of forwarded message ---
From: Sriram Narayanan [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Reply-To: Tomcat Developers List [EMAIL PROTECTED]
Subject: ClassNotFound Exception when loading Tomcat 4.0.1 via URLClassLoader
Date: 30/11/2001 9:24:34 AM
Hello all,
I'm trying to write a Swing based UI that'll help manage Tomcat.
Towards that end, I'm first trying to load Tomcat via a URLCLassLoader. This is so
that one can load and test different Tomcat releases, and builds, and jar combinations.
My idea is to load Tomcat via a URLCLassloader.
This thing works for Tomcat 3.3, but I'm facing the following problem with Tomcat 4.0.1
Any ideas ?
Thanks,
Sriram
--- Start of forwarded message ---
From: Sriram N [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Reply-To: Tomcat Developers List [EMAIL PROTECTED]
Subject: ClassNotFound Exception when loading Tomcat 4.0.1 via URLClassLoader
Date: 29/11/2001 6:43:02 PM
Hi all,
I'm trying to write a java class that will load Tomcat 4.0.1 for me.
My goal is:
- Do not use the classpath. The CLASSPATH env variable's contents are clear
be me first.
- Use the URLClassLoader to get started.
This technique works with Tomcat 3.3
With Tomcat 4.0.1 however, I get a ClassNotFoundException for
org.apache.catalina.loader.Reloader which is in the same bootstrap.jar that is
used to load
org.apache.catalina.startup.Bootstrap
However, when I stick to the batch file which adds bootstrap.jar to the system
CLASSPATH, tomcat runs OK, as usual.
Could some one point me to what I'm missing or doing wrong ? Thanks.
Here's the code that I use to load Tomcat 4.0.1
-- begin code
public class TCStart{
public static void main(String args[]){
try{
System.setProperty(catalina.home,f:/tc4.0.1/);
System.setProperty(catalina.base,f:/tc4.0.1/);
System.setProperty(java.class.path,);
java.io.File file = new
java.io.File(f:/tc4.0.1/bin/bootstrap.jar);
java.net.URL[] urls = new java.net.URL[]{file.toURL()};
java.net.URLClassLoader loader = new
java.net.URLClassLoader(urls);
Class aClass =
loader.loadClass(org.apache.catalina.startup.Bootstrap);
String classLoaderName =
aClass.getClassLoader().getClass().getName();
String className = aClass.getName();
System.out.println(ClassName + className);
System.out.println(ClassLoader + classLoaderName);
//Class aClass =
Class.forName(org.apache.catalina.startup.Bootstrap);
java.lang.reflect.Method method = null;
Class[] argsClass = new Class[] { String[].class };
// get the main method for the org.apache.tomcat.shell.Startup
class
method = aClass.getMethod(main, argsClass);
Object object = null;
String filePath= -f conf/server.xml;
Object[] arguments = new Object[] { new String[] {start}};
// now invoke the main method for the
org.apache.tomcat.shell.Startup class
method.invoke(object, arguments);
}catch(Exception ex){
System.err.println(Ugh ! is all that I can say);
ex.printStackTrace(System.err);
}
}
}
-- end code ---
And here's the stack Trace that I get.
begin stack trace dump ---
ClassName org.apache.catalina.startup.Bootstrap
ClassLoader java.net.URLClassLoader
Starting service Tomcat-Standalone
Apache Tomcat/4.0.1
Exception during startup processing
java.lang.reflect.InvocationTargetException: java.lang.NoClassDefFoundError:
org
/apache/catalina/loader/Reloader
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$100(Unknown Source)
at
DO NOT REPLY [Bug 4966] - request.getParameter(String) SOMETIMES fail to parse the querystring
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=4966.
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=4966
request.getParameter(String) SOMETIMES fail to parse the querystring
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution||WORKSFORME
--- Additional Comments From [EMAIL PROTECTED] 2001-11-30 23:31 ---
I created a simple servlet accessing the request parameters, with debug code
like:
String foo = req.getParameter(foo);
if (foo == null) {
System.out.println(No foo in URL: + req.getRequestURL());
}
I then used ab to hammer the servlet (called S3, and added to the examples
webapp) on:
http://127.0.0.1:8080/examples/servlet/S3?dfsds=dasdfasfoo=barfsdiuwe=qfebwejh
With concurrency set to 50 and 5000 requests, I didn't get a single failure.
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5068] - can't compile
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=5068. 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=5068 can't compile [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2001-11-30 23:34 --- Hmmm, the attachement looks weird. There was a problem compiling connectors for Tomcat 4.0 with the current CVS HEAD. It has been fixed (I assume that was the problem). -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/webapp/java WarpConnector.java
remm01/11/30 23:20:29
Modified:webapp/java WarpConnector.java
Log:
- Add the findLifecycleListeners method, so that webapp builds against the
HEAD of the CVS.
Revision ChangesPath
1.26 +8 -0 jakarta-tomcat-connectors/webapp/java/WarpConnector.java
Index: WarpConnector.java
===
RCS file: /home/cvs/jakarta-tomcat-connectors/webapp/java/WarpConnector.java,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- WarpConnector.java2001/10/31 08:10:29 1.25
+++ WarpConnector.java2001/12/01 07:20:29 1.26
@@ -449,6 +449,14 @@
}
/**
+ * Get the lifecycle listeners associated with this lifecycle. If this
+ * Lifecycle has no listeners registered, a zero-length array is returned.
+ */
+public LifecycleListener[] findLifecycleListeners() {
+return lifecycle.findLifecycleListeners();
+}
+
+/**
* Remove a codeLifecycleEvent/code listener from this
* codeConnector/code.
*
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5067] - can't compile java webapp project
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=5067. 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=5067 can't compile java webapp project [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2001-11-30 23:38 --- Fixed (ported the change from the Tomcat 4 CVS). Webapp should now build fine against the CVS HEAD and the 4.0 branch. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5134] - problems using the manager app from within a java app
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=5134. 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=5134 problems using the manager app from within a java app [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2001-11-30 23:48 --- Downloaded the code, built it. D:\tempjava SecureSourceViewer http://localhost:8080/manager/list The dialog pops up. I enter tomcat/tomcat I get: OK - Listed applications for virtual host localhost /examples:running:0 /webdav:running:0 /tomcat-docs:running:0 /manager:running:0 /admin:running:0 /:running:0 Don't forget the user you're using must have the manager role. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 BUILDING.txt
remm01/11/30 23:32:59 Modified:.BUILDING.txt Log: - Fix URL typo. Submitted by Martijn Koster. Revision ChangesPath 1.15 +2 -2 jakarta-tomcat-4.0/BUILDING.txt Index: BUILDING.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/BUILDING.txt,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- BUILDING.txt 2001/11/06 21:52:14 1.14 +++ BUILDING.txt 2001/12/01 07:32:59 1.15 @@ -1,4 +1,4 @@ -$Id: BUILDING.txt,v 1.14 2001/11/06 21:52:14 patrickl Exp $ +$Id: BUILDING.txt,v 1.15 2001/12/01 07:32:59 remm Exp $ Building The Tomcat 4.0 Servlet/JSP Container @@ -269,7 +269,7 @@ * Download a binary distribution of Struts 1.0 from: -http://jakarta.apache.org/builds/jakarta-struts/release/1.0/ +http://jakarta.apache.org/builds/jakarta-struts/release/v1.0/ On a Windows platform, you will need: jakarta-struts-1.0.zip -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5135] - URL typo in BUILDING.txt
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=5135. 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=5135 URL typo in BUILDING.txt [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2001-11-30 23:51 --- Fixed. Thanks. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 RUNNING.txt
remm01/11/30 23:35:46 Modified:.RUNNING.txt Log: - Fix typos. Submitted by Martijn Koster. Revision ChangesPath 1.3 +4 -4 jakarta-tomcat-4.0/RUNNING.txt Index: RUNNING.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/RUNNING.txt,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- RUNNING.txt 2001/08/27 20:22:37 1.2 +++ RUNNING.txt 2001/12/01 07:35:46 1.3 @@ -1,4 +1,4 @@ -$Id: RUNNING.txt,v 1.2 2001/08/27 20:22:37 craigmcc Exp $ +$Id: RUNNING.txt,v 1.3 2001/12/01 07:35:46 remm Exp $ Running The Tomcat 4.0 Servlet/JSP Container @@ -103,7 +103,7 @@ (4) Advanced Configuration - Multiple Tomcat 4 Instances -In many circumstances, it is desireable to have a single copy of a Tomcat 4 +In many circumstances, it is desirable to have a single copy of a Tomcat 4 binary distribution shared among multiple users on the same server. To make this possible, you must configure a CATALINA_BASE environment variable (in addition to CATALINA_HOME as described above) that points to a directory @@ -123,7 +123,7 @@ If you do not set CATALINA_BASE to an explicit value, it will be initialized to the same value as is set for CATALINA_HOME (which means that the same -directory is used for all relative path resoluations). +directory is used for all relative path resolutions). (5) Troubleshooting: @@ -155,7 +155,7 @@ After you click apply, Windows will create shortcuts in the directory with which you can use to start and stop the container. -3) The 'localhost' machine isn't found. This could happen if you're behing a +3) The 'localhost' machine isn't found. This could happen if you're behind a proxy. If that's the case, make sure the proxy configuration for your browser knows that you shouldn't be going through the proxy to access the localhost machine. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 RUNNING.txt
remm01/11/30 23:36:47 Modified:.Tag: tomcat_40_branch RUNNING.txt Log: - Fix typos. Submitted by Martijn Koster. Revision ChangesPath No revision No revision 1.2.2.1 +4 -4 jakarta-tomcat-4.0/RUNNING.txt Index: RUNNING.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/RUNNING.txt,v retrieving revision 1.2 retrieving revision 1.2.2.1 diff -u -r1.2 -r1.2.2.1 --- RUNNING.txt 2001/08/27 20:22:37 1.2 +++ RUNNING.txt 2001/12/01 07:36:47 1.2.2.1 @@ -1,4 +1,4 @@ -$Id: RUNNING.txt,v 1.2 2001/08/27 20:22:37 craigmcc Exp $ +$Id: RUNNING.txt,v 1.2.2.1 2001/12/01 07:36:47 remm Exp $ Running The Tomcat 4.0 Servlet/JSP Container @@ -103,7 +103,7 @@ (4) Advanced Configuration - Multiple Tomcat 4 Instances -In many circumstances, it is desireable to have a single copy of a Tomcat 4 +In many circumstances, it is desirable to have a single copy of a Tomcat 4 binary distribution shared among multiple users on the same server. To make this possible, you must configure a CATALINA_BASE environment variable (in addition to CATALINA_HOME as described above) that points to a directory @@ -123,7 +123,7 @@ If you do not set CATALINA_BASE to an explicit value, it will be initialized to the same value as is set for CATALINA_HOME (which means that the same -directory is used for all relative path resoluations). +directory is used for all relative path resolutions). (5) Troubleshooting: @@ -155,7 +155,7 @@ After you click apply, Windows will create shortcuts in the directory with which you can use to start and stop the container. -3) The 'localhost' machine isn't found. This could happen if you're behing a +3) The 'localhost' machine isn't found. This could happen if you're behind a proxy. If that's the case, make sure the proxy configuration for your browser knows that you shouldn't be going through the proxy to access the localhost machine. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5163] - typos in RUNNING.txt
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=5163. 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=5163 typos in RUNNING.txt [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2001-11-30 23:54 --- Fixed. Thanks. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/authenticator AuthenticatorBase.java
remm01/11/30 23:39:50
Modified:catalina/src/share/org/apache/catalina/authenticator
AuthenticatorBase.java
Log:
- Set the value of the seed which has just been calclated.
Please review this patch, as I don't know all the implications !
Patch submitted by Ian West ian at perth.wni.com
Revision ChangesPath
1.27 +5 -4
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/authenticator/AuthenticatorBase.java
Index: AuthenticatorBase.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/authenticator/AuthenticatorBase.java,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- AuthenticatorBase.java2001/11/09 19:38:25 1.26
+++ AuthenticatorBase.java2001/12/01 07:39:50 1.27
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/authenticator/AuthenticatorBase.java,v
1.26 2001/11/09 19:38:25 remm Exp $
- * $Revision: 1.26 $
- * $Date: 2001/11/09 19:38:25 $
+ * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/authenticator/AuthenticatorBase.java,v
1.27 2001/12/01 07:39:50 remm Exp $
+ * $Revision: 1.27 $
+ * $Date: 2001/12/01 07:39:50 $
*
*
*
@@ -121,7 +121,7 @@
* requests. Requests of any other type will simply be passed through.
*
* @author Craig R. McClanahan
- * @version $Revision: 1.26 $ $Date: 2001/11/09 19:38:25 $
+ * @version $Revision: 1.27 $ $Date: 2001/12/01 07:39:50 $
*/
@@ -856,6 +856,7 @@
long update = ((byte) entropy[i]) ((i % 8) * 8);
seed ^= update;
}
+this.random.setSeed(seed);
} catch (Exception e) {
this.random = new java.util.Random();
}
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5174] - entropy value computed but not used in org.apache.catalina.authenticator.AuthenticatorBase
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=5174. 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=5174 entropy value computed but not used in org.apache.catalina.authenticator.AuthenticatorBase [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2001-11-30 23:58 --- I applied the patch. It will be ported to the 4.0 branch after reviewing. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
JK versions
There is an important issue to discuss - labeling mod_jk. As you know, we are trying to make some improvements in jk, start using APR, etc. That will involve few significant changes - and some people may want to have a more 'stable' jk. There are 4 versions of jk: Let's call 1.0 what is present in tomcat3.2.x repository. Let's call 1.1 what is present in 3.3 repository. It is backward compatible with Jk1.0, has many fixes, etc. 1.2 - what is in jakarta-tomcat-connectors/jk, the same as 1.1 plus support for Apache2.0 ( Jk1.1 doesn't support apache2.0 since it wasn't available at that time ). This version also have support for tomcat4.0 and initial code for ajp14. I would call '1.2' the version that was in CVS around Oct 15 ( i.e. after both 3.3 and 4.0.1 were released, before any refactoring was started ). So far all the changes in the main tree were small. However some biger changes are needed and are already in progress. We'll have a simpler build system, support for APR, lot more flexibility, simpler configuration. I would like to call the next version of jk 2.0, as a number of internal APIs will change. ( all those numbers are made up - we can call them 1, 2, 3, 4 instead of 1.0, 1.1, ... ). What I would like to do is make a branch for mod_jk 1.2, and eventually build a snapshot. Eventually we should start a release plan and have a vote on the names and such. Since names/labels/versions are allways fun thing to discuss, I'm open to any other naming scheme - but we need to have one, it's extremely confusing otherwise. I will not check anything else into mod_jk until this is decided ( since my next commit is pretty big and likely to brake things, I did a lot of changes in uri_map, etc. - I need a stable branch labeled before doing the commit ). Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Submission: Portable SSL Support
Hi Eric, I looked at the patch - it seems ok. I think we should wait few more days for more people to have a chance to look at the code. It's great having an SSL expert around :-) What remains to be done is getting jk to reuse the same abstractions for ssl support - that would make the code cleaner. But it can wait a while, there are bigger changes going on there. Costin On Fri, 30 Nov 2001, Eric Rescorla wrote: I've finished patching Tomcat to support both PureTLS and JSSE (and it would be trivial to add pretty much any other SSL implementation if there was a need). Essentially, what I did was take the current support for JSSE and generalize it so that it could support any implementation. This required adding a fair amount of abstraction. (1) Each implementation is encapsulated by a subclass of SSLImplementation. As before, PoolTCPConnector is responsible for detecting that SSL has been called for and loading up the right implementation but it does it by using SSLImplementation. (2) SSLImplementation.getInstance() automatically chooses whatever implementation is active. (There's a parameter to tell it to use a specific one). (3) In order to get a socket you first get the appropriate socketFactory from the SSLImplementation. You then use socketFactory.getSocket() as before. (4) All the special things you can do with an SSL socket are encapsulated in SSLSupport. SSLImplementation.getSSLSuport(Socket sock) lets you get the SSLSupport for a given socket. (5) Currently you can get the attributes: javax.servlet.request.cipher_suite javax.servlet.request.X509Certificate What's supposed to be at: javax.servlet.request.key_size is extremely vague. I'll implement it once I hear back from Sun about the value. (6) Changes to the doc to explain this stuff. The changes are of three types: (1) A patch file. (2) A mess of new source files which live in org/apache/tomcat/util/net. (3) The following file needs to be deleted from the repository: org/apache/tomcat/util/net/SSLSocketFactory.java Due to the size of the changes I've put the patch and new source files up at http://www.rtfm.com/tomcat-changes-20011130.tar.gz. If someone wants them mailed to the list I'm happy to do so. Note: These changes only work properly with the latest PureTLS snapshot: 20011130 (though they should work fine if you're compiling without PureTLS at all as well). -Ekr -- [Eric Rescorla [EMAIL PROTECTED]] Author of SSL and TLS: Designing and Building Secure Systems http://www.rtfm.com/ -- 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: WG: TC3.3 updating a webapp without killing sessions
Hi Hans, Thanks for your feedback, lb is high on my list as well. I hope to finish the first part of the refactoring next week, and then we can start with new features and good stuff like you mention. I'm also trying to find a way to add/remove webapps without having to restart apache. Costin On Fri, 30 Nov 2001, Hans Schmid wrote: Hi, since Costin is currently refactoring mod_jk in jakarta-tomcat-connectors I want to throw in our usage scenario. We are abusing the loadbalancing feature of mod_jk to switch tomcats on the fly in order to be able to make application updates without killing our curreent user sessions. See discussion below from tomcat-user This feature (graceful restart) was present in jserv and is still missing in mod_jk/Tomcat3.3 as far as I know. Below are references to the archive where Michael Kuz has sent a patch to decouple this feature from the lbfactor (introducing an active flag). So please keep in mind the requirement to be able to update Webapps in a farm of Tomcats without killing active sessions. Thanks, Hans -Ursprüngliche Nachricht- Von: Hans Schmid [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 28. November 2001 18:21 An: Tomcat Users List Betreff: AW: TC3.3 updating a webapp without killing sessions Thanks Larry, perhaps a lbfactor of 0.1 or so would do the job for us. We could probably live with 1 out of 10 sessions beeing sent to the wrong Tomcat and beeing killed if this instance shuts down. Should this be discussed in tomcat-dev ? I remember a patch from early this year which tried to fix this (check the archives) but did never make it into the release It tried to add a flag called 'active' in the worker.properties file for each worker instead of misusing the lbfactor for this. ajp13-01... lbfactor=1 active=0 and ajb13-02... lbfactor=1 active=1 see http://w6.metronet.com/~wjm/tomcat/2001/Jan/msg00102.html and http://w6.metronet.com/~wjm/tomcat/2001/Jan/msg00114.html for the patch which might be a little bit outdated -Ursprüngliche Nachricht- Von: Larry Isaacs [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 28. November 2001 15:00 An: 'Tomcat Users List' Betreff: RE: TC3.3 updating a webapp without killing sessions I assume the value or lbfactor is requested to be 0 because 1/lbfactor is calculated during initialization. Since this is done with doubles, it may generate an internal representation for infinity rather than a division by zero error. I don't have a complete understanding of what mod_jk does internally for loadbalancing, but your approach seems like it should work. A brief scan of the codes shows that some updates to mod_jk would be needed to insure that lbfactor=0 means only use this worker when mandated by session routing. There isn't much logging around the choice of worker. Perhaps adding some logging would help determine why requests are being routed to the lbfactor=0 Tomcat when session routing shouldn't be a factor. Hope this helps. Cheers, Larry -Original Message- From: Hans Schmid [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 28, 2001 4:25 AM To: Tomcat-User Subject: TC3.3 updating a webapp without killing sessions Hi, We try to make a workaround for the following problems: 1.) memory management 2.) application update 3.) do not kill active sessions Perhaps someone can comment on the startegy and answer some questions. Our environment: Tomcat 3.3 final with mod_jk Apache 1.3.19 on Solaris 2.7 Sparc Our problem: ever growing cache until memory runs out (clearly an application problem) plus soft updates to our application without killing actiove sessions The idea: when a certain ammount of memory is reached by the tomcat java process, start up a second Tomcat and route all new requests to the second instance while existing sessions should phase out on the first instance. If no more sessions are active on the original Tomcat, shut it down (currently we just shut it down 30 minutes after the second Tomcat started up) How to do it with mod_jk: We have two versions of a worker.properties. Before we start up our second tomcat, we switch a link to point to the other version. Both versions of the worker.property file have a loadbalancer worker defined: First version: worker.list=loadbalancer worker.ajp13-01.port=11009 worker.ajp13-01.host=tomcathost worker.ajp13-01.type=ajp13 worker.ajp13-01.lbfactor=1 - important worker.ajp13-02.port=11019 worker.ajp13-02.host=tomcathost worker.ajp13-02.type=ajp13 worker.ajp13-02.lbfactor=0 - important worker.loadbalancer.type=lb worker.loadbalancer.balanced_workers=ajp13-01, ajp13-02 Second version: worker.list=loadbalancer worker.ajp13-01.port=11009
Re: Emulating JServ's session.topleveldomain with Catalina
Craig R. McClanahan [EMAIL PROTECTED] writes: I'd certainly be interested in a patch to allow pattern matching in the host mapper, as long as the code was smart about using direct string compares when no patterns are specified (to avoid slowing down all requests by regexp processing). Since . is a regex character, there is no way to automatically infer whether an alias string is a pattern or a literal, meaning that a way to communicate to the Mapper implementations which aliases are patterns is required. Because of this, I don't believe that it is possible to avoid minor API/server.xml additions/changes. The cleanest implementation route I see for addition of pattern matching is to solidfy an existing data type (Alias) as an interface accompanied by standard implementation. The suggested syntax would be as follows: Host ... Alias isPattern=true.*domain.com/Alias !-- An Alias element is not a pattern by default -- Aliaswww.otherdomain.com/Alias /Host I haven't previously used Digester, Modeler, or BeanUtils, so am unsure of what changes to make to mbeans-descriptors.xml and HostRuleSet.java (I definitely screwed up the declaration for Alias). Note that Tomcat already loads jakarta-regexp for use in the RemoteAddrValve and RemoteHostValve filters. If you need regexp patterns, that would be a convenient choice because no additional dependencies would be created. Gotcha -- I used RE.match() in the style of RequestFilterValve. Here's an incomplete version of the modifications to solicit feedback, and make sure I'm following the desired path: Index: src/share/org/apache/catalina/Alias.java === RCS file: Alias.java diff -N Alias.java --- /dev/null Fri Nov 30 17:57:31 2001 +++ Alias.java Fri Nov 30 17:59:22 2001 @@ -0,0 +1,128 @@ +/* + * $Header: +/home/cvspublic/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/Host.java,v +1.7 2001/10/22 04:48:56 remm Exp $ + * $Revision: 1.7 $ + * $Date: 2001/10/22 04:48:56 $ + * + * + * + * The Apache Software License, Version 1.1 + * + * Copyright (c) 1999 The Apache Software Foundation. All rights + * reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * + * 1. Redistributions of source code must retain the above copyright + *notice, this list of conditions and the following disclaimer. + * + * 2. Redistributions in binary form must reproduce the above copyright + *notice, this list of conditions and the following disclaimer in + *the documentation and/or other materials provided with the + *distribution. + * + * 3. The end-user documentation included with the redistribution, if + *any, must include the following acknowlegement: + * This product includes software developed by the + *Apache Software Foundation (http://www.apache.org/). + *Alternately, this acknowlegement may appear in the software itself, + *if and wherever such third-party acknowlegements normally appear. + * + * 4. The names The Jakarta Project, Tomcat, and Apache Software + *Foundation must not be used to endorse or promote products derived + *from this software without prior written permission. For written + *permission, please contact [EMAIL PROTECTED] + * + * 5. Products derived from this software may not be called Apache + *nor may Apache appear in their names without prior written + *permission of the Apache Group. + * + * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED + * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES + * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE + * DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR + * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, + * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT + * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF + * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND + * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, + * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT + * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + * + * + * This software consists of voluntary contributions made by many + * individuals on behalf of the Apache Software Foundation. For more + * information on the Apache Software Foundation, please see + * http://www.apache.org/. + * + */ + + +package org.apache.catalina; + + +import javax.servlet.ServletContext; + +/** + * An codeAlias/code defines a mapping from a host name used in a + * request to a bHost/b object from server.xml. + * + * @author a href=mailto:[EMAIL PROTECTED];Daniel Rall/a +
