Re: Thread priority
Michael Smith wrote: Remy Maucherat wrote: I was wondering about how expensive the Thread.setPriority method is, and to which extent it does what it advetises. The extent to which it has an effect is very much platform (and probably JVM) dependent. It's also dependent on the permissions a user has - on many (all?) unix systems, only root may set a process or thread to higher than normal priority [...] I suspect that this will mean that your suggested use of these calls will [...] have no effect [...] on most common JVM implementations. [...] it's pretty unlikely to make any noticable difference in performance. That may be true for Linux--which only has setpriority(2) available to the common user--but Solaris and Windows JVMs can conceivably support raising the Java Thread priority. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Apache 2.0 mod_jk.so bug ?
Hi, Whether it's a bug or not, it's definitely a strange thing going on, and at this point in time I suspect the mod_jk.so is the problem. I hope I can get a little verification. I have a Location Apache directive inside a SSL-enabled virtualhost, and if I go to a *directory* under that location that happens to be served by Tomcat, the URL rewrite gets munged. For example: Begin sample Apache conf VirtualHost _default_:443 # General setup for the virtual host DocumentRoot /test/html/mysite-ssl ServerName foo.bar.com:443 ServerAdmin [EMAIL PROTECTED] ErrorLog logs/ssl_error_log TransferLog logs/ssl_access_log # SSL Engine Switch: # Enable/Disable SSL for this virtual host. SSLEngine on [... (extra config removed)] Location /my-open-web-context Order Allow,Deny Allow from all Satisfy any /Location # Require authn for rest of virt host... /VirtualHost [...] JkMount /my-open-web-context ajp13 JkMount /my-open-web-context/* ajp13 End sample Apache conf IF I go to https://foo.bar.com/my-open-web-context/index.jsp it works FINE. BUT if I go to https://foo.bar.com/my-open-web-context/ (i.e. no index.jsp) I get a URL like this in my browser: http://foo.bar.com:443/my-open-web-context/index.jsp This URL of course fails because the http on the https port. Is this really a bug? This all worked fine with Apache 1.3. Also note that any dir handled by mod_jk NOT under the Location works fine. Smells like a bug. Could it be Apache itself? Should I just use jk2? There is pain between my ears. Info: Red Hat 8.0 / Apache 2.0.40, Tomcat 4.0.6LE, mod_jk.so compiled from jakarta-tomcat-connectors-jk-1.2.1-src package. Thanks for any pointers, -Dan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native/apache-2.0 bldjk.qclsrc
hgomez 2002/12/17 01:44:35
Modified:jk/native/apache-2.0 bldjk.qclsrc
Log:
Updated iSeries build file, include the missing _REENTRANT define
Revision ChangesPath
1.6 +266 -285 jakarta-tomcat-connectors/jk/native/apache-2.0/bldjk.qclsrc
Index: bldjk.qclsrc
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native/apache-2.0/bldjk.qclsrc,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- bldjk.qclsrc 11 Dec 2002 10:38:39 - 1.5
+++ bldjk.qclsrc 17 Dec 2002 09:44:35 - 1.6
@@ -1,288 +1,269 @@
PGM
-CRTCMOD MODULE(MOD_JK/MOD_JK) +
-SRCSTMF('/home/apache/jk/native/apache-2.0/mod_jk.c') +
-DEFINE('AS400' 'HAVE_JNI' 'USE_APACHE_MD5') +
-TEXT('mod_jk.c')+
-OPTIMIZE(40)+
-SYSIFCOPT(*IFSIO) +
-TGTCCSID(*JOB) +
-OPTION(*LOGMSG) +
-TERASPACE(*YES *TSIFC) +
-STGMDL(*INHERIT) +
-INCDIR('/home/apache/jk/native/common' +
- '/QIBM/ProdData/HTTPA/Include')
-
-CRTCMOD MODULE(MOD_JK/JK_AJP_COM)+
-SRCSTMF('/home/apache/jk/native/common/jk_ajp_common.c') +
-DEFINE('AS400' 'HAVE_JNI' 'USE_APACHE_MD5') +
-TEXT('jk_ajp_common.c') +
-OPTIMIZE(40) +
-SYSIFCOPT(*IFSIO)+
-LANGLVL(*ANSI) +
-TGTCCSID(*JOB) +
-OPTION(*LOGMSG) +
-TERASPACE(*YES *TSIFC) +
-STGMDL(*INHERIT) +
-INCDIR('/home/apache/jk/native/common' +
- '/QIBM/ProdData/HTTPA/Include')
-
-CRTCMOD MODULE(MOD_JK/JK_AJP12_W) +
-SRCSTMF('/home/apache/jk/native/common/jk_ajp12_worker.c') +
-DEFINE('AS400' 'HAVE_JNI' 'USE_APACHE_MD5')+
-TEXT('jk_ajp12_worker.c') +
-OPTIMIZE(40) +
-SYSIFCOPT(*IFSIO) +
-LANGLVL(*ANSI) +
-TGTCCSID(*JOB) +
-OPTION(*LOGMSG)+
-TERASPACE(*YES *TSIFC)+
-STGMDL(*INHERIT) +
-INCDIR('/home/apache/jk/native/common' +
- '/QIBM/ProdData/HTTPA/Include')
-
-CRTCMOD MODULE(MOD_JK/JK_AJP13) +
-SRCSTMF('/home/apache/jk/native/common/jk_ajp13.c') +
-DEFINE('AS400' 'HAVE_JNI' 'USE_APACHE_MD5') +
-TEXT('jk_ajp13.c') +
-OPTIMIZE(40)+
-SYSIFCOPT(*IFSIO) +
-LANGLVL(*ANSI) +
-TGTCCSID(*JOB) +
-OPTION(*LOGMSG) +
-TERASPACE(*YES *TSIFC) +
-STGMDL(*INHERIT) +
-INCDIR('/home/apache/jk/native/common' +
- '/QIBM/ProdData/HTTPA/Include')
-
-CRTCMOD MODULE(MOD_JK/JK_AJP13_W) +
-SRCSTMF('/home/apache/jk/native/common/jk_ajp13_worker.c') +
-DEFINE('AS400' 'HAVE_JNI' 'USE_APACHE_MD5')+
-TEXT('jk_ajp13_worker.c') +
-OPTIMIZE(40) +
-SYSIFCOPT(*IFSIO) +
-LANGLVL(*ANSI) +
-TGTCCSID(*JOB) +
-OPTION(*LOGMSG)+
-TERASPACE(*YES *TSIFC)+
-STGMDL(*INHERIT) +
-INCDIR('/home/apache/jk/native/common' +
- '/QIBM/ProdData/HTTPA/Include')
-
-CRTCMOD MODULE(MOD_JK/JK_AJP14) +
-SRCSTMF('/home/apache/jk/native/common/jk_ajp14.c') +
-DEFINE('AS400' 'HAVE_JNI' 'USE_APACHE_MD5') +
-TEXT('jk_ajp14.c') +
-OPTIMIZE(40)+
-SYSIFCOPT(*IFSIO) +
-LANGLVL(*ANSI)
cvs commit: jakarta-tomcat-connectors/jk/native/common jk_version.h
hgomez 2002/12/17 02:15:54 Modified:jk/native/common jk_version.h Log: Set JK to release 1.2.2 Revision ChangesPath 1.8 +2 -2 jakarta-tomcat-connectors/jk/native/common/jk_version.h Index: jk_version.h === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native/common/jk_version.h,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- jk_version.h 28 Nov 2002 09:50:26 - 1.7 +++ jk_version.h 17 Dec 2002 10:15:54 - 1.8 @@ -74,7 +74,7 @@ #define JK_VERBETA 0 #define JK_BETASTRING 1 /* set JK_VERISRELEASE to 1 when release (do not forget to commit!) */ -#define JK_VERISRELEASE 0 +#define JK_VERISRELEASE 1 /** END OF AREA TO MODIFY BEFORE RELEASING */ #define PACKAGE mod_jk/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
JK 1.2.2
jtc cvs tagged JK_1_2_2 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native/common jk_version.h
hgomez 2002/12/17 02:36:16 Modified:jk/native/common jk_version.h Log: Set JK to 1.2.3-dev Revision ChangesPath 1.9 +3 -3 jakarta-tomcat-connectors/jk/native/common/jk_version.h Index: jk_version.h === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native/common/jk_version.h,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- jk_version.h 17 Dec 2002 10:15:54 - 1.8 +++ jk_version.h 17 Dec 2002 10:36:16 - 1.9 @@ -68,13 +68,13 @@ #define JK_VERMAJOR 1 #define JK_VERMINOR 2 #define JK_VERFIX 2 -#define JK_VERSTRING1.2.2 +#define JK_VERSTRING1.2.3 /* Beta number */ #define JK_VERBETA 0 #define JK_BETASTRING 1 /* set JK_VERISRELEASE to 1 when release (do not forget to commit!) */ -#define JK_VERISRELEASE 1 +#define JK_VERISRELEASE 0 /** END OF AREA TO MODIFY BEFORE RELEASING */ #define PACKAGE mod_jk/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [4.1.17] [VOTE] Stability rating
As a Tomcat user I have been looking forward to getting Tomcat 4.1.x into my production environment. Up until now I have had issues that have prevented me upgrading. I'm a regular reader of this list but my only previous participation has been when voting a previous milestone of 4.1.x not stable. I'm very pleased to say though that all the issues that I have come across have now been resolved and 4.1.17 is working very well for me. Thanks very much for all your hard work on the product. Richard Atkinson ballot [ ] Alpha [ ] Beta [X] Stable (General Availability) /ballot This email with all information contained herein or attached hereto may contain confidential and/or privileged information intended for the addressee(s) only. If you have received this email in error, please contact the sender and immediately delete this email in its entirety and any attachments thereto. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15436] New: - Cannot start Tomcat 4.1.12 with JDK1.2.2
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=15436. 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=15436 Cannot start Tomcat 4.1.12 with JDK1.2.2 Summary: Cannot start Tomcat 4.1.12 with JDK1.2.2 Product: Tomcat 4 Version: 4.1.12 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] On Windows 2000 platform. The moment I upgrade to JDK1.4, it works fine. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15437] New: - Authentication for admin and manager applications
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=15437. 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=15437 Authentication for admin and manager applications Summary: Authentication for admin and manager applications Product: Tomcat 4 Version: 4.1.16 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] 1. I included the proper roles lines in tomcat-users.xml (admin and manager roles); 2. I am using an JDBC realm in server.xml to perform authentication in a personal webapp. When I use the username and password defined in tomcat-users.xml to acess manager, the authetication is performed but I get 403 denied access. If I include the username and roles in the SQL database I cann access admin and manager. Is this how it shoud work? Can I have two diferent authentication reals at the same time? Is thgis a conflict? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[ANNOUNCE] JK 1.2.2 released
JK 1.2.2 maintenance release is available at : http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.2/ Changes with JK 1.2.2: * tomcat_trend.pl updated script to support changed logging of aborted requests * jk set correctly the content-type in Apache 2.0, making it ready to works with mod_deflate and AddOutputFilterByType * jk will check result of get_endpoint and handle a failure. This call can fail if the allocation for the endpoint fails because of low memory conditions causing a dereference of NULL when we try and access the endpoint Sources, Linux (flat/rpms) and iSeries binaries are already available, Windows, Solaris, MacOS X binaries will be released soon. Regards. iSeries Note: Previous JK binaries for iSeries (AS/400) were built without TERASPACE support nor multi-threading support code and should be considered incorrect. Production sites should upgrade to this version. Binaries Providers: We're looking for binaries contributors for AIX and FreeBSD (Apache 1.3 (w/wo SSL) and Apache 2.0.42 or higher). -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15437] - Authentication for admin and manager applications
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=15437. 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=15437 Authentication for admin and manager applications [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-12-17 13:23 --- Is this how it shoud work? Yes Can I have two diferent authentication reals at the same time? Not on the same context. Is thgis a conflict? No :-) Please send your questions to [EMAIL PROTECTED] This is not a place to ask question :-). -- Jeanfrancois -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15436] - Cannot start Tomcat 4.1.12 with JDK1.2.2
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=15436. 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=15436 Cannot start Tomcat 4.1.12 with JDK1.2.2 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID Summary|Cannot start Tomcat 4.1.12 |Cannot start Tomcat 4.1.12 |with JDK1.2.2 |with JDK1.2.2 --- Additional Comments From [EMAIL PROTECTED] 2002-12-17 13:26 --- Please change role for 10 seconds and read you bug. It's like going to the doctor and say I'm sick. What the doctor can do for you with only that information? Same thing for us. Please put more information when you file bug. Also, please send the question to [EMAIL PROTECTED] *first*. There are a lot of users that will answer your questions. :-) -- Jeanfrancois -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-site/xdocs building.xml index.xml resources.xml
remm2002/12/17 05:26:04 Modified:docs bugreport.html building.html index.html irc.html news.html resources.html xdocsbuilding.xml index.xml resources.xml Log: - Website update for Tomcat 4.1.17. Revision ChangesPath 1.8 +2 -0 jakarta-tomcat-site/docs/bugreport.html Index: bugreport.html === RCS file: /home/cvs/jakarta-tomcat-site/docs/bugreport.html,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- bugreport.html15 Nov 2002 17:37:11 - 1.7 +++ bugreport.html17 Dec 2002 13:26:03 - 1.8 @@ -5,6 +5,7 @@ !-- start the processing -- !-- == -- +!-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! -- !-- Main Page Section -- !-- == -- html @@ -16,6 +17,7 @@ + titleThe Jakarta Site - Report a Tomcat Bug/title /head 1.4 +5 -3 jakarta-tomcat-site/docs/building.html Index: building.html === RCS file: /home/cvs/jakarta-tomcat-site/docs/building.html,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- building.html 15 Nov 2002 17:37:11 - 1.3 +++ building.html 17 Dec 2002 13:26:03 - 1.4 @@ -5,6 +5,7 @@ !-- start the processing -- !-- == -- +!-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! -- !-- Main Page Section -- !-- == -- html @@ -16,6 +17,7 @@ + titleThe Jakarta Site - Building Tomcat/title /head @@ -226,14 +228,14 @@ file, and adding the following content to it: codebr / # - Proxy setup -br / -# Uncomment if using a proxy serverbr / +# Uncomment if using a proxy server.br / #proxy.host=proxy.domainbr / #proxy.port=8080br / #proxy.use=onbr / br / # - Default Base Path for Dependent Packages -br / -# Replace this path with the directory path where dependencies binariesbr / -# should be downloadedbr / +# Replace this path with the directory path wherebr / +# dependencies binaries should be downloaded.br / base.path=/usr/localbr / /code /p 1.32 +11 -8 jakarta-tomcat-site/docs/index.html Index: index.html === RCS file: /home/cvs/jakarta-tomcat-site/docs/index.html,v retrieving revision 1.31 retrieving revision 1.32 diff -u -r1.31 -r1.32 --- index.html15 Nov 2002 17:37:11 - 1.31 +++ index.html17 Dec 2002 13:26:03 - 1.32 @@ -5,6 +5,7 @@ !-- start the processing -- !-- == -- +!-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! -- !-- Main Page Section -- !-- == -- html @@ -16,6 +17,7 @@ + titleThe Jakarta Site - Apache Tomcat/title /head @@ -146,16 +148,16 @@ Servlet/JSP specifications:/p table tr -td bgcolor=#039acc colspan= rowspan= valign=top align=left +th bgcolor=#039acc colspan= rowspan= valign=top align=left font color=#00 size=-1 face=arial,helvetica,sanserif Servlet/JSP Spec /font -/td -td bgcolor=#039acc colspan= rowspan= valign=top align=left +/th +th bgcolor=#039acc colspan= rowspan= valign=top align=left font color=#00 size=-1 face=arial,helvetica,sanserif Tomcat version /font -/td +/th /tr tr td bgcolor=#a0ddf0 colspan= rowspan= valign=top align=left @@ -165,7 +167,7 @@ /td td bgcolor=#a0ddf0 colspan= rowspan= valign=top align=left font color=#00 size=-1 face=arial,helvetica,sanserif -
Re: [4.1.17] [VOTE] Stability rating
Remy Maucherat wrote: ballot [ ] Alpha [ ] Beta [X] Stable (General Availability) Reason (optional): /ballot Thanks for voting and for testing 4.1.17 Alpha! It is time for a stable release. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] New committer: Filip Hanik
+1 Welcome aboard Filip Remy Maucherat wrote: I'd like to nominate Filip Hanik filip at filip.net as a committer on the Tomcat project. Filip has written the clustering code that was committed recently in the Tomcat 5 CVS, and is willing to maintain it, as well as continuing to improve it (including supporting large clusters). Filip is one of the authors of JavaGroups, the Java based clustering framework used in the new Tomcat clustering code. He has my +1. Remy -- 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: [VOTE] New committer: Filip Hanik
Glenn Nielsen wrote: +1 Welcome aboard Filip A little bit late, as Filip already got his account ;-) Welcome on board Filip :) Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Thread priority
Is there a reported bug you are trying to address?
I have not noticed any problems related to thread scheduling with the medium
volume site I administer.
It is possible that this change could cause threads other than the socket
accept thread to be starved. I would be -1 for making this change unless
there is a significant reported bug that these changes would address.
If it ain't broke, don't fix it. ;-)
Regards,
Glenn
Remy Maucherat wrote:
Hi,
I was wondering about how expensive the Thread.setPriority method is,
and to which extent it does what it advetises.
The point would be to assign the minimum priority to background
reloading threads, as well as set the priority of the thread accepting
on the server socket to the maximum while is it accepting, and then
switch back to normal priority once the accept is done.
That would prevent the only thread accepting on the server socket from
being starved by the OS scheduler.
Here's a patch for the PoolTcpEndpoint:
diff -r1.8 PoolTcpEndpoint.java
496a497
Thread.currentThread().setPriority(Thread.MAX_PRIORITY);
500c501,503
}
---
} finally {
Thread.currentThread().setPriority(Thread.NORM_PRIORITY);
}
I have no idea if this produces useful results. This adds no additional
overhead on Windows according to OptimizeIt (which might hint that it
doesn't do anything on that platform). Maybe it would be a good ideato
test this on different platforms (and hammer the server to see how it
compares to an unpatched server).
According to Doug Lea's book, this may heuristically do something
intelligent depending on the VM implementation. (great :) )
Comments ?
Remy
--
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: Thread priority
Glenn Nielsen wrote: Is there a reported bug you are trying to address? Not really. The test here reported a lot of connection failures: http://webperformanceinc.com/library/ServletReport/ Tomcat 4.1.17 should improve the results over 4.1.12 (it's faster and would probably lower slightly GC), but I think the number of errors was higher than it should have been. This could be caused by GC, or possibly because the accepting thread couldn't get the job done, or some other unknown factor. I have not noticed any problems related to thread scheduling with the medium volume site I administer. It is possible that this change could cause threads other than the socket accept thread to be starved. I would be -1 for making this change unless there is a significant reported bug that these changes would address. If it ain't broke, don't fix it. ;-) Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] New committer: Filip Hanik
Remy Maucherat wrote: Glenn Nielsen wrote: +1 Welcome aboard Filip A little bit late, as Filip already got his account ;-) Welcome on board Filip :) Did there is any chance to have one day javagroups as an jakarta project covered by an ASF license ? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
gzip-encoding in TC 4.1.x/5.x
I spent some times playing with http compression,
using Apache 2.0 mod_deflate together with mod_jk,
and it works great (at least with jk 1.2.2).
I wonder now if someone, may be Remy, has plan to
add it in Catalina 1.x/2.x (or Coyote) to make it
available for both HTTP 1.1 and JK2 ?
For those who want to experiment JK+DEFLATE
here is was to add in httpd.conf :
---
...
LoadModule jk_module /modules/mod_jk.so
LoadModule deflate_module /modules/mod_deflate.so
...
#
# MOD_DEFLATE
#
# Netscape 4.x has some problems...
BrowserMatch ^Mozilla/4 gzip-only-text/html
# Netscape 4.06-4.08 have some more problems
BrowserMatch ^Mozilla/4\.0[678] no-gzip
# MSIE masquerades as Netscape, but it is fine
BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
# Don't compress images
SetEnvIfNoCase Request_URI \.(gif|jpe?g|png)$ no-gzip dont-vary
# Make sure proxies don't deliver the wrong content
Header append Vary User-Agent env=!dont-vary
#
# Logging
#
LogFormat %h %l %u %t \%r\ %s %b \%{Referer}i\ \%{User-Agent}i\
combined
LogFormat %h %l %u %t \%r\ %s %b common
LogFormat %{Referer}i - %U referer
LogFormat %{User-agent}i agent
DeflateFilterNote ratio
LogFormat '%r %b (%{ratio}n) %{User-agent}i' deflate
VirtualHost *
ServerName myhost.org
ServerAdmin [EMAIL PROTECTED]
#
# DEFLATE
#
AddOutputFilterByType DEFLATE text/html text/plain text/xml
DeflateFilterNote ratio
LogFormat '%r %b (%{ratio}n) %{User-agent}i' deflate
JkMount /* ajp13
...
/VirtualHost
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15442] New: - missing java package in compiled jsp according to jsp directory
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=15442. 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=15442 missing java package in compiled jsp according to jsp directory Summary: missing java package in compiled jsp according to jsp directory Product: Tomcat 4 Version: 4.1.12 Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Jasper 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] We are using tomcat 4.0.6 with Jasper. When a JSP gets compiled in java source the package ist set to some prefix and the relative path of the jsp file to web- root is used as java package. e.g. package jsp_servlet._buecher._login; public class __login extends Tomcat 4.1.12 with jasper2 creates package org.apache.jsp; public class Login_jsp extends ... Now we have serveral hundred JSP in different directories. Mapping them all to the same java package results in name clashes. duplicate class: org.apache.jsp.Login_jsp Why was ths behaviour changed and how can i come around this problem? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: gzip-encoding in TC 4.1.x/5.x
Henri Gomez wrote: I spent some times playing with http compression, using Apache 2.0 mod_deflate together with mod_jk, and it works great (at least with jk 1.2.2). I wonder now if someone, may be Remy, has plan to add it in Catalina 1.x/2.x (or Coyote) to make it available for both HTTP 1.1 and JK2 ? I was planning to add the feature as filters in Coyote HTTP/1.1, but never did, because I wasn't able to find efficient compression code. I suppose something could be put together using the JDK compression IS and OS in the meantime. For JK 2, I think it's fair to say that you should rely on the native webserver capabilities (that's the whole point, I think). Great that you added the support (I thought it had been there from the start, actually). Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[BUG?] ajp connector with address
hi, i'm using tomcat 4.1.12 i created a connector on port 8009 and IP 127.0.0.1. the server.xml file is correct - which means that the address-attribute is set to 127.0.0.1. the administrator shows the correct address 127.0.0.1 and i would expect tomcat to bind to 127.0.0.1:8009, but it binds to :::8009. Is this a bug? (i think so!) Did anyone notice my post on the user-mailinglist? Will it be fixed? Is it already fixed (in an upcoming 4.1.x release)? Thx Sven -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Thread priority
My 2 cents. I rather a server deny connections and keep on running than accept connections until it dies :) peter lin Remy Maucherat [EMAIL PROTECTED] wrote:Glenn Nielsen wrote: Is there a reported bug you are trying to address? Not really. The test here reported a lot of connection failures: http://webperformanceinc.com/library/ServletReport/ Tomcat 4.1.17 should improve the results over 4.1.12 (it's faster and would probably lower slightly GC), but I think the number of errors was higher than it should have been. This could be caused by GC, or possibly because the accepting thread couldn't get the job done, or some other unknown factor. I have not noticed any problems related to thread scheduling with the medium volume site I administer. It is possible that this change could cause threads other than the socket accept thread to be starved. I would be -1 for making this change unless there is a significant reported bug that these changes would address. If it ain't broke, don't fix it. ;-) Remy -- To unsubscribe, e-mail: For additional commands, e-mail: - Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
Re: Thread priority
Yes, that sums up my thoughts exactly. Peter Lin wrote: My 2 cents. I rather a server deny connections and keep on running than accept connections until it dies :) peter lin Remy Maucherat [EMAIL PROTECTED] wrote:Glenn Nielsen wrote: Is there a reported bug you are trying to address? Not really. The test here reported a lot of connection failures: http://webperformanceinc.com/library/ServletReport/ Tomcat 4.1.17 should improve the results over 4.1.12 (it's faster and would probably lower slightly GC), but I think the number of errors was higher than it should have been. This could be caused by GC, or possibly because the accepting thread couldn't get the job done, or some other unknown factor. I have not noticed any problems related to thread scheduling with the medium volume site I administer. It is possible that this change could cause threads other than the socket accept thread to be starved. I would be -1 for making this change unless there is a significant reported bug that these changes would address. If it ain't broke, don't fix it. ;-) Remy -- To unsubscribe, e-mail: For additional commands, e-mail: - Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] New committer: Filip Hanik
I knew that, just wanted to show my support. I am interested in the results of the new clustering, at some point I want to setup clustering for one of my customers. Regards, Glenn Remy Maucherat wrote: Glenn Nielsen wrote: +1 Welcome aboard Filip A little bit late, as Filip already got his account ;-) Welcome on board Filip :) Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [BUG?] ajp connector with address
Is this a bug? (i think so!) sorry - i will use bugzilla next time. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: gzip-encoding in TC 4.1.x/5.x
Remy Maucherat wrote: Henri Gomez wrote: I spent some times playing with http compression, using Apache 2.0 mod_deflate together with mod_jk, and it works great (at least with jk 1.2.2). I wonder now if someone, may be Remy, has plan to add it in Catalina 1.x/2.x (or Coyote) to make it available for both HTTP 1.1 and JK2 ? I was planning to add the feature as filters in Coyote HTTP/1.1, but never did, because I wasn't able to find efficient compression code. I suppose something could be put together using the JDK compression IS and OS in the meantime. GZIPOutputstream is quit fast today. For JK 2, I think it's fair to say that you should rely on the native webserver capabilities (that's the whole point, I think). Great that you added the support (I thought it had been there from the start, actually). Hum, the idea to put compression on the Java side (HTTP 1.1/JK2) is to reduce the response time and network bandwidth when webserver and tomcat are linked TCP/IP (ie ajp13 + network). I make some bench on large output streams and even if mod_deflate help by sending to browser smaller responses, it still has to handle the big response caming from tomcat. That's why it could be a real gain to have gzip compression also on the tomcat side, I think you'll see real gain with recent browser as soon as response is more than 10k. I hope someone could works on it at the coyote level to make it available for both HTTP 1.1 and JK2 upper layers. There is some things to care off, ie activation of compression on certains mimes contents (ie: text/html, text/plain) and when size is greater than xxx bytes. If someone has ideas and may be a skeleton for coyote, I may help him on this area. Regards -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: gzip-encoding in TC 4.1.x/5.x
For JK 2, I think it's fair to say that you should rely on the native webserver capabilities (that's the whole point, I think). Great that you added the support (I thought it had been there from the start, actually). I didn't added support really, just corrected the way we set the content-type in Apache 2.0 using the correct API ;) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: gzip-encoding in TC 4.1.x/5.x
Henri Gomez wrote: Remy Maucherat wrote: Henri Gomez wrote: I spent some times playing with http compression, using Apache 2.0 mod_deflate together with mod_jk, and it works great (at least with jk 1.2.2). I wonder now if someone, may be Remy, has plan to add it in Catalina 1.x/2.x (or Coyote) to make it available for both HTTP 1.1 and JK2 ? I was planning to add the feature as filters in Coyote HTTP/1.1, but never did, because I wasn't able to find efficient compression code. I suppose something could be put together using the JDK compression IS and OS in the meantime. GZIPOutputstream is quit fast today. I think I'll disagree whenever I'll try it. Ideally, I'd like a ByteChunk compress(ByteChunk) with nice recycle methods so that no object even gets allocated. For JK 2, I think it's fair to say that you should rely on the native webserver capabilities (that's the whole point, I think). Great that you added the support (I thought it had been there from the start, actually). Hum, the idea to put compression on the Java side (HTTP 1.1/JK2) is to reduce the response time and network bandwidth when webserver and tomcat are linked TCP/IP (ie ajp13 + network). I make some bench on large output streams and even if mod_deflate help by sending to browser smaller responses, it still has to handle the big response caming from tomcat. That's why it could be a real gain to have gzip compression also on the tomcat side, I think you'll see real gain with recent browser as soon as response is more than 10k. I hope someone could works on it at the coyote level to make it available for both HTTP 1.1 and JK2 upper layers. You can't do it, unless the code is in the adapter, and that's bad design (it's a protocol feature, so it should be in the protocol hanlder). The compression code should go in a filter for HTTP/1.1. For the native webserver connector, like JK2, I insist that this is to be done in the native code. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-site/xdocs/stylesheets project.xml
remm2002/12/17 08:40:24 Modified:docs bugreport.html building.html index.html irc.html news.html resources.html xdocs/stylesheets project.xml Log: - Update source and binaries links. Revision ChangesPath 1.9 +2 -2 jakarta-tomcat-site/docs/bugreport.html Index: bugreport.html === RCS file: /home/cvs/jakarta-tomcat-site/docs/bugreport.html,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- bugreport.html17 Dec 2002 13:26:03 - 1.8 +++ bugreport.html17 Dec 2002 16:40:23 - 1.9 @@ -69,9 +69,9 @@ /ul pstrongDownload/strong/p ul -lia href=http://jakarta.apache.org/site/binindex.html;Binaries/a +lia href=http://jakarta.apache.org/site/binindex.cgi;Binaries/a /li -lia href=http://jakarta.apache.org/site/sourceindex.html;Source Code/a +lia href=http://jakarta.apache.org/site/sourceindex.cgi;Source Code/a /li /ul pstrongJakarta/strong/p 1.5 +2 -2 jakarta-tomcat-site/docs/building.html Index: building.html === RCS file: /home/cvs/jakarta-tomcat-site/docs/building.html,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- building.html 17 Dec 2002 13:26:03 - 1.4 +++ building.html 17 Dec 2002 16:40:23 - 1.5 @@ -69,9 +69,9 @@ /ul pstrongDownload/strong/p ul -lia href=http://jakarta.apache.org/site/binindex.html;Binaries/a +lia href=http://jakarta.apache.org/site/binindex.cgi;Binaries/a /li -lia href=http://jakarta.apache.org/site/sourceindex.html;Source Code/a +lia href=http://jakarta.apache.org/site/sourceindex.cgi;Source Code/a /li /ul pstrongJakarta/strong/p 1.33 +2 -2 jakarta-tomcat-site/docs/index.html Index: index.html === RCS file: /home/cvs/jakarta-tomcat-site/docs/index.html,v retrieving revision 1.32 retrieving revision 1.33 diff -u -r1.32 -r1.33 --- index.html17 Dec 2002 13:26:03 - 1.32 +++ index.html17 Dec 2002 16:40:23 - 1.33 @@ -69,9 +69,9 @@ /ul pstrongDownload/strong/p ul -lia href=http://jakarta.apache.org/site/binindex.html;Binaries/a +lia href=http://jakarta.apache.org/site/binindex.cgi;Binaries/a /li -lia href=http://jakarta.apache.org/site/sourceindex.html;Source Code/a +lia href=http://jakarta.apache.org/site/sourceindex.cgi;Source Code/a /li /ul pstrongJakarta/strong/p 1.10 +2 -2 jakarta-tomcat-site/docs/irc.html Index: irc.html === RCS file: /home/cvs/jakarta-tomcat-site/docs/irc.html,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- irc.html 17 Dec 2002 13:26:03 - 1.9 +++ irc.html 17 Dec 2002 16:40:23 - 1.10 @@ -69,9 +69,9 @@ /ul pstrongDownload/strong/p ul -lia href=http://jakarta.apache.org/site/binindex.html;Binaries/a +lia href=http://jakarta.apache.org/site/binindex.cgi;Binaries/a /li -lia href=http://jakarta.apache.org/site/sourceindex.html;Source Code/a +lia href=http://jakarta.apache.org/site/sourceindex.cgi;Source Code/a /li /ul pstrongJakarta/strong/p 1.33 +2 -2 jakarta-tomcat-site/docs/news.html Index: news.html === RCS file: /home/cvs/jakarta-tomcat-site/docs/news.html,v retrieving revision 1.32 retrieving revision 1.33 diff -u -r1.32 -r1.33 --- news.html 17 Dec 2002 13:26:03 - 1.32 +++ news.html 17 Dec 2002 16:40:23 - 1.33 @@ -69,9 +69,9 @@ /ul pstrongDownload/strong/p ul -lia href=http://jakarta.apache.org/site/binindex.html;Binaries/a +lia href=http://jakarta.apache.org/site/binindex.cgi;Binaries/a /li -lia href=http://jakarta.apache.org/site/sourceindex.html;Source Code/a +lia
DO NOT REPLY [Bug 15417] - Add port for forced compilation of pages
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=15417. 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=15417 Add port for forced compilation of pages --- Additional Comments From [EMAIL PROTECTED] 2002-12-17 16:55 --- I have also discovered that because version systems retain the mod date of the file, one can update from an older branch to a newer branch and still have this problem because the files in the newer branch are older than the day you were working on the older branch, and therefore older than the classfiles. Can you honestly tell me this isn't confusing :) Sure be nice if I could spend my brain cycles writing code rather than keeping track of what tomcat is doing to my branches. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: gzip-encoding in TC 4.1.x/5.x
I was planning to add the feature as filters in Coyote HTTP/1.1, but never did, because I wasn't able to find efficient compression code. I suppose something could be put together using the JDK compression IS and OS in the meantime. GZIPOutputstream is quit fast today. I think I'll disagree whenever I'll try it. C'est le jeu ;) Ideally, I'd like a ByteChunk compress(ByteChunk) with nice recycle methods so that no object even gets allocated. Right, but I'm currently playing with stuff which read/write large files, and reading/writing with GZIPstream make the program 4* faster ! I hope someone could works on it at the coyote level to make it available for both HTTP 1.1 and JK2 upper layers. You can't do it, unless the code is in the adapter, and that's bad design (it's a protocol feature, so it should be in the protocol hanlder). Couldn't the compression goes in filter, like Amy does sometimes ago ? The compression code should go in a filter for HTTP/1.1. For the native webserver connector, like JK2, I insist that this is to be done in the native code. Just take an example : If a servlet has to respond a 100K content, and you're using webserver+jk via net/ajp13, tomcat will send 100K by the network which will be compressed 'à la volée' by mod_deflate. You've got a 100K network use (tc-webserver) + about 30k network use (webserver-browser). If you've got the compression done in java side, you'll have only 30+30 network use and you know that bandwidth today is more important for IT and ADMINs that CPU/RAM. May be a solution could be to bench and optimize the Amy works on gzip compression filter ? Of course compression may also be present in browser-server, ie while uploading large file. When you're using tomcat/jk in SOAP situation, having gzip activated make operation appears really quickers since the volume of datas in both side could be important. Just my 0.01 EUR. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: gzip-encoding in TC 4.1.x/5.x
Henri Gomez wrote: I was planning to add the feature as filters in Coyote HTTP/1.1, but never did, because I wasn't able to find efficient compression code. I suppose something could be put together using the JDK compression IS and OS in the meantime. GZIPOutputstream is quit fast today. I think I'll disagree whenever I'll try it. C'est le jeu ;) Ideally, I'd like a ByteChunk compress(ByteChunk) with nice recycle methods so that no object even gets allocated. Right, but I'm currently playing with stuff which read/write large files, and reading/writing with GZIPstream make the program 4* faster ! One of the problems is that the compressed streams from the JDK are not recyclable, cause a lot of possibly synced method calls, and so on. Plus, it's kinda ugly to fit the OS and IS models into the Coyote HTTP/1.1 filter model. Does anyone know about compression code which would use byte arrays on input/output ? I hope someone could works on it at the coyote level to make it available for both HTTP 1.1 and JK2 upper layers. You can't do it, unless the code is in the adapter, and that's bad design (it's a protocol feature, so it should be in the protocol hanlder). Couldn't the compression goes in filter, like Amy does sometimes ago ? You can use it there if you want. However, transfer encoding is a protocol feature. So it seems logical to handle this at the protocol layer (for example, chunked is a transfer encoding, and also hanlded at the protocol handler level). Plus you get a nice server wide configuration on the native webserver, rather than individual settings depending on where the resource is served from. It just seems much cleaner. I don't quite see the Apache - Tomcat link being bandwidth constrained except in very specific situations. In loopback, it uses special optimized processing, and if there are separate boxes for Apache and Tomcat, then they should IMO use a dedicated network link. I don't see what you can do to improve Amy's filter performance, as it has to: - be thread safe - use inefficient methods from the servlet API (which create garbage, etc) Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15446] New: - request parameters get lost when using the ajp connector
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15446. 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=15446 request parameters get lost when using the ajp connector Summary: request parameters get lost when using the ajp connector Product: Tomcat 4 Version: 4.1.12 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: Connector:JK/AJP (deprecated) AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The below jsp includes a servet, the servlet is unable to access the parameters on the request url e.g. http://host.net/testInclude.jsp?test=test Removing a line from the comment or changing the flush=true to flush=false can both make it work, but I don't understand why. It does seem to be very buffer related and very dependant on size of text before the include. This problem only occurs when using tomcat through apache and is not reproducible with tomcat alone. I'm using apache 1.3.26 with the mod_jk connector to tomcat 4.1.12 (load balanced) %@ page language=java session=true % html head titleAccess Reports/title !-- test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test -- /head body jsp:include page=/servlet/testIncludeServlet flush=true jsp:param name=depth value=summary / /jsp:include /body /html -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [VOTE] New committer: Filip Hanik
-Original Message- From: Henri Gomez [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 17, 2002 6:27 AM To: Tomcat Developers List Subject: Re: [VOTE] New committer: Filip Hanik Remy Maucherat wrote: Glenn Nielsen wrote: +1 Welcome aboard Filip A little bit late, as Filip already got his account ;-) Welcome on board Filip :) Did there is any chance to have one day javagroups as an jakarta project covered by an ASF license ? I doubt that will happen anytime soon, it is quite a process to do that. And it is really up to Bela since he is the founder and this is his baby :)) Filip -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Thread priority
here is a good link about the different VM settings for the GC. should be worth trying out the different ones to see which one is best for Tomcat http://wireless.java.sun.com/midp/articles/garbagecollection2/ Filip ~ Namaste - I bow to the divine in you ~ Filip Hanik Software Architect www.filip.net -Original Message- From: Peter Lin [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 17, 2002 6:55 AM To: Tomcat Developers List Subject: Re: Thread priority My 2 cents. I rather a server deny connections and keep on running than accept connections until it dies :) peter lin Remy Maucherat [EMAIL PROTECTED] wrote:Glenn Nielsen wrote: Is there a reported bug you are trying to address? Not really. The test here reported a lot of connection failures: http://webperformanceinc.com/library/ServletReport/ Tomcat 4.1.17 should improve the results over 4.1.12 (it's faster and would probably lower slightly GC), but I think the number of errors was higher than it should have been. This could be caused by GC, or possibly because the accepting thread couldn't get the job done, or some other unknown factor. I have not noticed any problems related to thread scheduling with the medium volume site I administer. It is possible that this change could cause threads other than the socket accept thread to be starved. I would be -1 for making this change unless there is a significant reported bug that these changes would address. If it ain't broke, don't fix it. ;-) Remy -- To unsubscribe, e-mail: For additional commands, e-mail: - Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [VOTE] New committer: Filip Hanik
I knew that, just wanted to show my support. I am interested in the results of the new clustering, at some point I want to setup clustering for one of my customers. Regards, Glenn thanks Glenn, the version for Tomcat 4.1.12 is fully working http://sourceforge.net/projects/tomcat-jg and I am actually putting this to work with one of my clients for TC 5.x I am planning to build a highly improved version of this. Filip ~ Namaste - I bow to the divine in you ~ Filip Hanik Software Architect www.filip.net -Original Message- From: Glenn Nielsen [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 17, 2002 7:02 AM To: Tomcat Developers List Subject: Re: [VOTE] New committer: Filip Hanik I knew that, just wanted to show my support. I am interested in the results of the new clustering, at some point I want to setup clustering for one of my customers. Regards, Glenn Remy Maucherat wrote: Glenn Nielsen wrote: +1 Welcome aboard Filip A little bit late, as Filip already got his account ;-) Welcome on board Filip :) Remy -- 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]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet JspServlet.java
jfarcand2002/12/17 11:21:07
Modified:jasper2/src/share/org/apache/jasper/servlet JspServlet.java
Log:
Remove the first condition since it is not required. The getPathInfo() returns
always null except when the jsp-property-file element is used and the servlet-name
is not defined in the web.xml. I'm not happy with the solution but I don't think we
need to change the url-mapping algorithm (StandardCpntextMapper) to include this
corner case.
Revision ChangesPath
1.16 +4 -4
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet/JspServlet.java
Index: JspServlet.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet/JspServlet.java,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- JspServlet.java 13 Dec 2002 21:38:06 - 1.15
+++ JspServlet.java 17 Dec 2002 19:21:07 - 1.16
@@ -217,7 +217,7 @@
// jsp is not defined with servlet-name, the url
// as to be passed as it is to the JSP container (since Catalina
// doesn't know anything about the requested JSP
-if(request.getServletPath().indexOf(.) == -1
request.getPathInfo() != null){
+if(request.getPathInfo() != null){
jspUri = request.getServletPath() + request.getPathInfo();
}
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina Globals.java
jfarcand2002/12/17 12:05:07 Modified:catalina/src/share/org/apache/catalina Globals.java Log: Servlet 2.4 Specification addition -- SRV.8.4.2 Forwarded Request Parameters Except for servlets obtained by using the getNamedDispatcher method, a servlet being used from a servlet that has been invoked by another servlet using the forward method of RequestDispatcher. The following request attributes must be set: - javax.servlet.forward.request_uri - javax.servlet.forward.context_path - javax.servlet.forward.servlet_path - javax.servlet.forward.path_info - javax.servlet.forward.query_string Revision ChangesPath 1.3 +50 -10 jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/Globals.java Index: Globals.java === RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/Globals.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- Globals.java 21 Sep 2002 06:47:22 - 1.2 +++ Globals.java 17 Dec 2002 20:05:07 - 1.3 @@ -126,9 +126,17 @@ * The request attribute under which the original context path is stored * on an included dispatcher request. */ -public static final String CONTEXT_PATH_ATTR = +public static final String INCLUDE_CONTEXT_PATH_ATTR = javax.servlet.include.context_path; + +/** + * The request attribute under which the original context path is stored + * on an forwarded dispatcher request. + */ +public static final String FORWARD_CONTEXT_PATH_ATTR = +javax.servlet.forward.context_path; + /** * The request attribute under which we forward a Java exception @@ -216,27 +224,51 @@ * The request attribute under which the original path info is stored * on an included dispatcher request. */ -public static final String PATH_INFO_ATTR = +public static final String INCLUDE_PATH_INFO_ATTR = javax.servlet.include.path_info; + + +/** + * The request attribute under which the original path info is stored + * on an forwarded dispatcher request. + */ +public static final String FORWARD_PATH_INFO_ATTR = +javax.servlet.forward.path_info; /** * The request attribute under which the original query string is stored * on an included dispatcher request. */ -public static final String QUERY_STRING_ATTR = +public static final String INCLUDE_QUERY_STRING_ATTR = javax.servlet.include.query_string; - + +/** + * The request attribute under which the original query string is stored + * on an forwarded dispatcher request. + */ +public static final String FORWARD_QUERY_STRING_ATTR = +javax.servlet.forward.query_string; + + /** * The request attribute under which the original request URI is stored * on an included dispatcher request. */ -public static final String REQUEST_URI_ATTR = +public static final String INCLUDE_REQUEST_URI_ATTR = javax.servlet.include.request_uri; /** + * The request attribute under which the original request URI is stored + * on an forwarded dispatcher request. + */ +public static final String FORWARD_REQUEST_URI_ATTR = +javax.servlet.forward.request_uri; + + +/** * The request attribute under which we forward a servlet name to * an error page. */ @@ -248,10 +280,18 @@ * The request attribute under which the original servlet path is stored * on an included dispatcher request. */ -public static final String SERVLET_PATH_ATTR = +public static final String INCLUDE_SERVLET_PATH_ATTR = javax.servlet.include.servlet_path; +/** + * The request attribute under which the original servlet path is stored + * on an forwarded dispatcher request. + */ +public static final String FORWARD_SERVLET_PATH_ATTR = +javax.servlet.forward.servlet_path; + + /** * The name of the cookie used to pass the session identifier back * and forth with the client. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core ApplicationRequest.java ApplicationDispatcher.java ApplicationHttpRequest.java
jfarcand2002/12/17 12:06:20
Modified:catalina/src/share/org/apache/catalina/core
ApplicationRequest.java ApplicationDispatcher.java
ApplicationHttpRequest.java
Log:
Servlet 2.4 Specification addition
--
SRV.8.4.2 Forwarded Request Parameters
Except for servlets obtained by using the getNamedDispatcher method, a
servlet being used from a servlet that has been invoked by another
servlet using the forward method of RequestDispatcher.
The following request attributes must be set:
- javax.servlet.forward.request_uri
- javax.servlet.forward.context_path
- javax.servlet.forward.servlet_path
- javax.servlet.forward.path_info
- javax.servlet.forward.query_string
Revision ChangesPath
1.2 +9 -7
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/ApplicationRequest.java
Index: ApplicationRequest.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/ApplicationRequest.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ApplicationRequest.java 18 Jul 2002 16:48:06 - 1.1
+++ ApplicationRequest.java 17 Dec 2002 20:06:20 - 1.2
@@ -103,9 +103,11 @@
* The set of attribute names that are special for request dispatchers.
*/
protected static final String specials[] =
-{ Globals.REQUEST_URI_ATTR, Globals.CONTEXT_PATH_ATTR,
- Globals.SERVLET_PATH_ATTR, Globals.PATH_INFO_ATTR,
- Globals.QUERY_STRING_ATTR };
+{ Globals.INCLUDE_REQUEST_URI_ATTR, Globals.INCLUDE_CONTEXT_PATH_ATTR,
+ Globals.INCLUDE_SERVLET_PATH_ATTR, Globals.INCLUDE_PATH_INFO_ATTR,
+ Globals.INCLUDE_QUERY_STRING_ATTR, Globals.FORWARD_REQUEST_URI_ATTR,
+ Globals.FORWARD_CONTEXT_PATH_ATTR, Globals.FORWARD_SERVLET_PATH_ATTR,
+ Globals.FORWARD_PATH_INFO_ATTR, Globals.FORWARD_QUERY_STRING_ATTR };
// --- Constructors
1.7 +28 -9
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/ApplicationDispatcher.java
Index: ApplicationDispatcher.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/ApplicationDispatcher.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- ApplicationDispatcher.java6 Dec 2002 02:49:39 - 1.6
+++ ApplicationDispatcher.java17 Dec 2002 20:06:20 - 1.7
@@ -450,6 +450,25 @@
wrequest.setRequestURI(sb.toString());
wrequest.setServletPath(servletPath);
wrequest.setPathInfo(pathInfo);
+
+if (sb.length() 0)
+wrequest.setAttribute(Globals.FORWARD_REQUEST_URI_ATTR,
+ sb.toString());
+if (contextPath != null)
+wrequest.setAttribute(Globals.FORWARD_CONTEXT_PATH_ATTR,
+ contextPath);
+if (servletPath != null)
+wrequest.setAttribute(Globals.FORWARD_SERVLET_PATH_ATTR,
+ servletPath);
+if (pathInfo != null)
+wrequest.setAttribute(Globals.FORWARD_PATH_INFO_ATTR,
+ pathInfo);
+if (queryString != null) {
+wrequest.setAttribute(Globals.FORWARD_QUERY_STRING_ATTR,
+ queryString);
+wrequest.mergeParameters(queryString);
+}
+
if (queryString != null) {
wrequest.setQueryString(queryString);
wrequest.mergeParameters(queryString);
@@ -599,19 +618,19 @@
if (pathInfo != null)
sb.append(pathInfo);
if (sb.length() 0)
-wrequest.setAttribute(Globals.REQUEST_URI_ATTR,
+wrequest.setAttribute(Globals.INCLUDE_REQUEST_URI_ATTR,
sb.toString());
if (contextPath != null)
-wrequest.setAttribute(Globals.CONTEXT_PATH_ATTR,
+wrequest.setAttribute(Globals.INCLUDE_CONTEXT_PATH_ATTR,
contextPath);
if (servletPath != null)
-wrequest.setAttribute(Globals.SERVLET_PATH_ATTR,
+wrequest.setAttribute(Globals.INCLUDE_SERVLET_PATH_ATTR,
servletPath);
if (pathInfo != null)
-wrequest.setAttribute(Globals.PATH_INFO_ATTR,
+
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/servlets DefaultServlet.java InvokerServlet.java
jfarcand2002/12/17 12:06:51
Modified:catalina/src/share/org/apache/catalina/servlets
DefaultServlet.java InvokerServlet.java
Log:
Servlet 2.4 Specification addition
--
SRV.8.4.2 Forwarded Request Parameters
Except for servlets obtained by using the getNamedDispatcher method, a
servlet being used from a servlet that has been invoked by another
servlet using the forward method of RequestDispatcher.
The following request attributes must be set:
- javax.servlet.forward.request_uri
- javax.servlet.forward.context_path
- javax.servlet.forward.servlet_path
- javax.servlet.forward.path_info
- javax.servlet.forward.query_string
Revision ChangesPath
1.3 +5 -5
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/servlets/DefaultServlet.java
Index: DefaultServlet.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/servlets/DefaultServlet.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- DefaultServlet.java 18 Sep 2002 13:17:31 - 1.2
+++ DefaultServlet.java 17 Dec 2002 20:06:49 - 1.3
@@ -969,7 +969,7 @@
// Checking If headers
boolean included =
-(request.getAttribute(Globals.CONTEXT_PATH_ATTR) != null);
+(request.getAttribute(Globals.INCLUDE_CONTEXT_PATH_ATTR) != null);
if (!included
!checkIfHeaders(request, response, resourceInfo)) {
return;
1.4 +8 -8
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/servlets/InvokerServlet.java
Index: InvokerServlet.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/servlets/InvokerServlet.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- InvokerServlet.java 7 Oct 2002 20:35:19 - 1.3
+++ InvokerServlet.java 17 Dec 2002 20:06:50 - 1.4
@@ -272,15 +272,15 @@
String inServletPath = null;
String inPathInfo = null;
boolean included =
-(request.getAttribute(Globals.REQUEST_URI_ATTR) != null);
+(request.getAttribute(Globals.INCLUDE_REQUEST_URI_ATTR) != null);
if (included) {
inRequestURI =
-(String) request.getAttribute(Globals.REQUEST_URI_ATTR);
+(String) request.getAttribute(Globals.INCLUDE_REQUEST_URI_ATTR);
inServletPath =
-(String) request.getAttribute(Globals.SERVLET_PATH_ATTR);
+(String) request.getAttribute(Globals.INCLUDE_SERVLET_PATH_ATTR);
inPathInfo =
-(String) request.getAttribute(Globals.PATH_INFO_ATTR);
+(String) request.getAttribute(Globals.INCLUDE_PATH_INFO_ATTR);
} else {
inRequestURI = request.getRequestURI();
inServletPath = request.getServletPath();
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5 CoyoteRequest.java
jfarcand2002/12/17 12:07:38 Modified:coyote/src/java/org/apache/coyote/tomcat5 CoyoteRequest.java Log: Servlet 2.4 Specification addition -- SRV.8.4.2 Forwarded Request Parameters Except for servlets obtained by using the getNamedDispatcher method, a servlet being used from a servlet that has been invoked by another servlet using the forward method of RequestDispatcher. The following request attributes must be set: - javax.servlet.forward.request_uri - javax.servlet.forward.context_path - javax.servlet.forward.servlet_path - javax.servlet.forward.path_info - javax.servlet.forward.query_stringCVS: -- Revision ChangesPath 1.12 +5 -5 jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteRequest.java Index: CoyoteRequest.java === RCS file: /home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteRequest.java,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- CoyoteRequest.java26 Nov 2002 11:09:40 - 1.11 +++ CoyoteRequest.java17 Dec 2002 20:07:38 - 1.12 @@ -1118,7 +1118,7 @@ return (context.getServletContext().getRequestDispatcher(path)); // Convert a request-relative path to a context-relative one -String servletPath = (String) getAttribute(Globals.SERVLET_PATH_ATTR); +String servletPath = (String) getAttribute(Globals.INCLUDE_SERVLET_PATH_ATTR); if (servletPath == null) servletPath = getServletPath(); -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Coyote Connector Question for Dev
I am toying around with the connector for some personal reasons, nothing I intend to commit. I have a question, I added an attribute to the Connector element in server.xml. My problem is that the setAttributeXXX(String x) is only invoked once but three instances of the CoyoteConnector are created. So two instances are not having the attributeXXX set. please enlighten me :) Filip ~ Namaste - I bow to the divine in you ~ Filip Hanik Software Architect www.filip.net -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Coyote Connector Question for Dev
oops idiot question, sorry about that! I need to set the attribute in every Connector element Filip ~ Namaste - I bow to the divine in you ~ Filip Hanik Software Architect www.filip.net -Original Message- From: Filip Hanik [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 17, 2002 12:32 PM To: Tomcat Developers List Subject: Coyote Connector Question for Dev I am toying around with the connector for some personal reasons, nothing I intend to commit. I have a question, I added an attribute to the Connector element in server.xml. My problem is that the setAttributeXXX(String x) is only invoked once but three instances of the CoyoteConnector are created. So two instances are not having the attributeXXX set. please enlighten me :) Filip ~ Namaste - I bow to the divine in you ~ Filip Hanik Software Architect www.filip.net -- 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]
JSP compiler could not find the import class
Hi, One .jsp file has @page import statements, that class is under WEB-INF/classes and compiler could not find it. It works in develop machine but not on production machine which tomcat version is 3.2.3 and develop is 3.2.4. The configuration of both machine are same. The compile error looks like org.apache.jasper.JasperException: Unable to compile class for JSP xx.java Class MODIS_GlobalVars not found in import import MODIS_GlobalVars; ^ 1 error Could you give me some idea? Thanks very much. --- ???
DO NOT REPLY [Bug 15456] New: - NullPointerException in JkCoyoteHandler when connecting using SSL on Apache server
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=15456. 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=15456 NullPointerException in JkCoyoteHandler when connecting using SSL on Apache server Summary: NullPointerException in JkCoyoteHandler when connecting using SSL on Apache server Product: Tomcat 4 Version: 4.1.17 Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Connector:Coyote JK 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] java.lang.NullPointerException at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:386) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.tomcat4.CoyoteAdapter.postParseRequest (CoyoteAdapter.java:310) at org.apache.coyote.tomcat4.CoyoteAdapter.service (CoyoteAdapter.java:221) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:632) at org.apache.jk.common.ChannelSocket.processConnection (ChannelSocket.java:590) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:707) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (ThreadPool.java:530) at java.lang.Thread.run(Thread.java:536) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15462] New: - Location directive breaks mod_jk finding index.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=15462. 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=15462 Location directive breaks mod_jk finding index.jsp Summary: Location directive breaks mod_jk finding index.jsp Product: Tomcat 4 Version: 4.0.6 Final Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: Connector:JK/AJP (deprecated) AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] This is with Apache 2.0.40 (Red Hat 8.0) and mod_jk.so built from jakarta- tomcat-connectors-jk-1.2.1-src. Inside a SSL-enabled virtual host, a directory requested that falls under a Location directive that is also served by Tomcat will cause a Bad Request (code 400) page. For example, if I have the following Apache config: Begin sample Apache conf VirtualHost _default_:443 [... (extra config removed)] # SSL Engine Switch: # Enable/Disable SSL for this virtual host. SSLEngine on [...] Location /my-open-web-context Order Allow,Deny Allow from all Satisfy any /Location # Require authentication for rest of virt host... /VirtualHost [...] JkMount /my-open-web-context ajp13 JkMount /my-open-web-context/* ajp13 End sample Apache conf I can successfully get this URL: https://my-host/my-open-web-context/index.jsp But if I leave out the index.jsp, I get a 400 Error with the following URL rewritten in the browser: http://my-host:443/my-open-web-context/index.jsp This exact same config worked fine with Apache 1.3 and the same version of mod_jk and Tomcat. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-servletapi-5/jsr152/examples/xml xml.jsp xml.txt
kinman 2002/12/17 14:16:56 Modified:jsr152/examples/xml xml.jsp xml.txt Log: - Modified to work to namespace-aware XML parser. Revision ChangesPath 1.2 +1 -1 jakarta-servletapi-5/jsr152/examples/xml/xml.jsp Index: xml.jsp === RCS file: /home/cvs/jakarta-servletapi-5/jsr152/examples/xml/xml.jsp,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- xml.jsp 27 Aug 2002 13:16:50 - 1.1 +++ xml.jsp 17 Dec 2002 22:16:56 - 1.2 @@ -1,5 +1,5 @@ ?xml version=1.0? -jsp:root xmlns=http://java.sun.com/JSP/Page; +jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=1.2 jsp:directive.page contentType=text/html/ jsp:directive.page import=java.util.Date, java.util.Locale/ 1.2 +1 -1 jakarta-servletapi-5/jsr152/examples/xml/xml.txt Index: xml.txt === RCS file: /home/cvs/jakarta-servletapi-5/jsr152/examples/xml/xml.txt,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- xml.txt 27 Aug 2002 13:16:51 - 1.1 +++ xml.txt 17 Dec 2002 22:16:56 - 1.2 @@ -1,5 +1,5 @@ ?xml version=1.0? -jsp:root xmlns=http://java.sun.com/JSP/Page; +jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=1.2 jsp:directive.page contentType=text/html/ jsp:directive.page import=java.util.Date, java.util.Locale/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-servletapi-5/jsr154/examples/WEB-INF web.xml
kinman 2002/12/17 14:23:23 Modified:jsr152/examples/WEB-INF web.xml jsr154/examples/WEB-INF web.xml Log: - Patch by Glenn Nielsen [EMAIL PROTECTED] Adds display name and descriptions to their web.xml files, so that the HTML manager app has a name to display for these webapps. Revision ChangesPath 1.6 +5 -0 jakarta-servletapi-5/jsr152/examples/WEB-INF/web.xml Index: web.xml === RCS file: /home/cvs/jakarta-servletapi-5/jsr152/examples/WEB-INF/web.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- web.xml 29 Oct 2002 17:42:57 - 1.5 +++ web.xml 17 Dec 2002 22:23:23 - 1.6 @@ -5,6 +5,11 @@ xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee web-app_2_4.xsd version=2.4 +display-nameJSP 2.0 Examples/display-name +description + JSP 2.0 Examples. +/description + !-- Define servlet-mapped and path-mapped example filters -- filter filter-nameServlet Mapped Filter/filter-name 1.4 +5 -0 jakarta-servletapi-5/jsr154/examples/WEB-INF/web.xml Index: web.xml === RCS file: /home/cvs/jakarta-servletapi-5/jsr154/examples/WEB-INF/web.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- web.xml 29 Oct 2002 17:42:57 - 1.3 +++ web.xml 17 Dec 2002 22:23:23 - 1.4 @@ -6,6 +6,11 @@ web-app +display-nameServlet 2.4 Examples/display-name +description + Servlet 2.4 Examples. +/description + !-- Define servlet-mapped and path-mapped example filters -- filter filter-nameServlet Mapped Filter/filter-name -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15463] New: - StandardManager incorrectly uses getLastAccessedTime
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=15463. 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=15463 StandardManager incorrectly uses getLastAccessedTime Summary: StandardManager incorrectly uses getLastAccessedTime Product: Tomcat 4 Version: 4.1.12 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] See http://nagoya.apache.org/bugzilla/show_bug.cgi?id=570 This bug was fixed in 3.x by Marc Saegesser but 4.1.12 suffers from the same problem. It appears that the same solution can be applied to 4.1.12. This bug produces incorrect early session expiration. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15464] New: - CoyoteResponse.encodeURL fails to encode relative paths.
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=15464. 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=15464 CoyoteResponse.encodeURL fails to encode relative paths. Summary: CoyoteResponse.encodeURL fails to encode relative paths. Product: Tomcat 4 Version: 4.1.17 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: Connector:Coyote HTTP/1.1 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If a call to response.encodeURL is made from a jsp passing a relative path as the argumen, the implementation CoyoteResponse.encodeURL attempts to encode the String argument as an absolute URL, throwing a IllegalArgumentException. Example: response.encodeURL( myTest.jsp ) - fails to compile response.encodeURL( /myTest.jsp ) - compiles fine but access fails Prepeding the argument with / seems to allow the page to be compiled, however, references to the encoded URL result in the error: HTTP Status 500 - No Context configured to process this request. This error is not present in Tomcat 3.3.1 (release I am migrating from). -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[Help] Tomcat 4.1.17 loosing session when switching from HTTPS to HTTP
We use to show login page via HTTPS and then redirect to HTTP. It worked fine with tomcat 3.x + Apache with ssl. Can't make it work with 4.1.17 and Apache with ssl - when I change protocol it creates new session and as a result forces me to login again. Is it expected behavior? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[PATCH] jakarta-servletapi-5
Attached are a set of API patches leading up to PFD2 of the
specification. Look for a corresponding patch to jakarta-tomcat-jasper
to bring it up to date with these APIs.
Also note the attached replacement for TagProtocol.gif.
jsr152/src/share/javax/servlet/jsp/tagext/doc-files/TagProtocol.gif
- Updated diagram to remove arrow from released state to all
properties initialized state.
- Moved label [3] to another arrow.
jsr152/src/share/javax/servlet/jsp/tagext/Tag.java
- Removed state transition [3] from class javadocs.
- Added a new [3] label clarifying details about what may be called
on tag reuse.
jsr152/src/share/javax/servlet/jsp/tagext/TagData.java
- Updated description for getAttribute() to clarify
REQUEST_TIME_VALUE is returned for any dynamic attribute set
via jsp:attribute.
jsr152/src/share/javax/servlet/jsp/tagext/JspFragment.java
- for example -- in other words
jsr152/src/share/javax/servlet/jsp/tagext/VariableInfo.java
- Fixed incorrect class comment about variable scope.
- Removed old comment about JLS verbiage.
- Improved description of why 'boxed' types are necessary.
jsr152/src/share/javax/servlet/jsp/tagext/TagVariableInfo.java
- Fixed erroneous comment about only being available in JSP 2.0
format
jsr152/src/share/javax/servlet/jsp/tagext/SimpleTag.java
- Clarified SimpleTag has the equivalent power of BodyTag but with a
much simpler lifecycle.
jsr152/src/share/javax/servlet/jsp/tagext/IterationTag.java
- Clarified description for return value of SKIP_BODY from
doAfterBody()
jsr152/src/share/javax/servlet/jsp/PageContext.java
- Fixed class description as some elements were moved to JspContext.
jsr152/src/share/javax/servlet/jsp/JspContext.java
- Fixed class description as some elements were moved from
PageContext.
- Removed constants PAGE_SCOPE, REQUEST_SCOPE, SESSION_SCOPE and
APPLICATION_SCOPE as these are duplicated in PageContext.
jsr152/src/share/javax/servlet/jsp/tagext/BodyTag.java
- Clarified that in a classic tag invocation with an empty body
(e.g. my:tag/), the body methods are not to be called by the
container.
jsr152/src/share/javax/servlet/jsp/tagext/TagLibraryValidator.java
- A validator operates on the XML view associated with the JSP page,
not the XML document.
jsr152/src/share/javax/servlet/jsp/el/VariableResolver.java
- Removed pContext parameter from resolveVariable()
jsr152/src/share/javax/servlet/jsp/el/ExpressionEvaluator.java
- Changed from an interface to an abstract class.
jsr152/src/share/javax/servlet/jsp/el/Expression.java
- Changed from an interface to an abstract class.
---
Mark Roth, Java Software
JSP 2.0 Co-Specification Lead
Sun Microsystems, Inc.
Index: jsr152/src/share/javax/servlet/jsp/JspContext.java
===
RCS file:
/home/cvspublic/jakarta-servletapi-5/jsr152/src/share/javax/servlet/jsp/JspContext.java,v
retrieving revision 1.5
diff -u -r1.5 JspContext.java
--- jsr152/src/share/javax/servlet/jsp/JspContext.java 8 Nov 2002 21:30:21 -
1.5
+++ jsr152/src/share/javax/servlet/jsp/JspContext.java 18 Dec 2002 02:36:33 -
@@ -84,45 +84,30 @@
*
* pBMethods Intended for JSP authors/B
* p
+ * Some methods provide Buniform access/B to the diverse objects
+ * representing scopes.
+ * The implementation must use the underlying machinery
+ * corresponding to that scope, so information can be passed back and
+ * forth between the underlying environment (e.g. Servlets) and JSP pages.
+ * The methods are:
+ * codesetAttribute()/code, codegetAttribute()/code,
+ * codefindAttribute()/code, coderemoveAttribute()/code,
+ * codegetAttributesScope()/code and
+ * codegetAttributeNamesInScope()/code.
+ *
+ * p
* The following methods provide Bconvenient access/B to implicit objects:
- * ul
* codegetOut()/code
*
+ * p
+ * The following methods provide Bprogrammatic access/b to the
+ * Expression Language evaluator:
+ * codegetExpressionEvaluator()/code, codegetVariableResolver()/code
+ *
* @since 2.0
*/
public abstract class JspContext {
-
-/**
- * Page scope: (this is the default) the named reference remains available
- * in this JspContext until the return from the current Servlet.service()
- * invocation.
- */
-
-public static final int PAGE_SCOPE = 1;
-
-/**
- * Request scope: the named reference remains available from the
- * ServletRequest associated with the Servlet until the current
- * request is completed.
- */
-
-public static final int REQUEST_SCOPE = 2;
-
-/**
- * Session scope (only valid if this page participates in a session):
- * the named reference remains available from the HttpSession (if any)
- * associated with the Servlet until the HttpSession is invalidated.
- */
-
-public static final int
[PATCH] jakarta-tomcat-jasper
Attached is a patch to bring Japser2 up to date with the latest APIs
from the JSR-152 Expert Group.
jasper2/src/share/org/apache/jasper/runtime/JspContextWrapper.java
- Updated to conform to new VariableResolver API
jasper2/src/share/org/apache/jasper/runtime/PageContextImpl.java
- Updated to conform to new VariableResolver API
jasper2/src/share/org/apache/jasper/runtime/ExpressionEvaluatorImpl.java
- Updated to conform to new VariableResolver API
- Updated to conform to new ExpressionEvaluator API (which is now an
abstract class instead of an interface)
- Updated to conform to new Exrpression API (which is now an
abstract class instead of an interface)
---
Mark Roth, Java Software
JSP 2.0 Co-Specification Lead
Sun Microsystems, Inc.
Index: jasper2/src/share/org/apache/jasper/runtime/ExpressionEvaluatorImpl.java
===
RCS file:
/home/cvspublic/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime/ExpressionEvaluatorImpl.java,v
retrieving revision 1.5
diff -u -r1.5 ExpressionEvaluatorImpl.java
--- jasper2/src/share/org/apache/jasper/runtime/ExpressionEvaluatorImpl.java29 Aug
2002 02:04:21 - 1.5
+++ jasper2/src/share/org/apache/jasper/runtime/ExpressionEvaluatorImpl.java18 Dec
+2002 02:37:36 -
@@ -74,7 +74,7 @@
*/
public class ExpressionEvaluatorImpl
-implements ExpressionEvaluator
+extends ExpressionEvaluator
{
private PageContextImpl pageContext;
@@ -153,7 +153,7 @@
// pContext parameter is going away in JSP 2.0
Object result;
try {
-result = delegate.resolveVariable( pName, null );
+result = delegate.resolveVariable( pName );
}
catch( ELException e ) {
throw new org.apache.jasper.runtime.el.jstl.ELException(
@@ -255,7 +255,7 @@
* can be moved out of JSTL into its own project.
*/
private class JSTLExpression
-implements Expression
+extends Expression
{
private String expression;
private Class expectedType;
Index: jasper2/src/share/org/apache/jasper/runtime/JspContextWrapper.java
===
RCS file:
/home/cvspublic/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime/JspContextWrapper.java,v
retrieving revision 1.9
diff -u -r1.9 JspContextWrapper.java
--- jasper2/src/share/org/apache/jasper/runtime/JspContextWrapper.java 3 Dec 2002
23:17:48 - 1.9
+++ jasper2/src/share/org/apache/jasper/runtime/JspContextWrapper.java 18 Dec 2002
+02:37:37 -
@@ -303,16 +303,14 @@
/**
* VariableResolver interface
*/
-public Object resolveVariable( String pName, Object pContext )
+public Object resolveVariable( String pName )
throws ELException
{
if (invokingJspCtxt instanceof PageContextImpl) {
- return ((PageContextImpl) invokingJspCtxt).resolveVariable(pName,
- pContext);
+ return ((PageContextImpl) invokingJspCtxt).resolveVariable(pName);
}
- return ((JspContextWrapper) invokingJspCtxt).resolveVariable(pName,
-pContext);
+ return ((JspContextWrapper) invokingJspCtxt).resolveVariable(pName);
}
/**
Index: jasper2/src/share/org/apache/jasper/runtime/PageContextImpl.java
===
RCS file:
/home/cvspublic/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime/PageContextImpl.java,v
retrieving revision 1.37
diff -u -r1.37 PageContextImpl.java
--- jasper2/src/share/org/apache/jasper/runtime/PageContextImpl.java3 Dec 2002
01:58:36 - 1.37
+++ jasper2/src/share/org/apache/jasper/runtime/PageContextImpl.java18 Dec 2002
+02:37:45 -
@@ -640,13 +640,12 @@
/**
* VariableResolver interface
*/
-public Object resolveVariable( String pName, Object pContext )
+public Object resolveVariable( String pName )
throws ELException
{
-// Note: pContext will be going away.
try {
-return PageContextImpl.variableResolver.resolveVariable(
-pName, this );
+return PageContextImpl.variableResolver.resolveVariable( pName,
+this );
}
catch( org.apache.jasper.runtime.el.jstl.ELException e ) {
throw new ELException( e );
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15470] New: - The result of servlet called from a framed html page is unstable
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=15470. 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=15470 The result of servlet called from a framed html page is unstable Summary: The result of servlet called from a framed html page is unstable Product: Tomcat 4 Version: 4.1.17 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Critical Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] - start of test.html !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Frameset//EN http://www.w3.org/TR/html4/frameset.dtd; html head meta http-equiv=Content-Type content=text/html; charset=gb2312 titleFrame Servlet Test /title /head frameset rows=50%,50% cols=* frameborder=NO border=0 framespacing=0 frame src=http://127.0.0.1:8080/examples/servlet/HelloWorldExample; name=leftFrame scrolling=NO noresize frame src=http://127.0.0.1:8080/examples/servlet/HelloWorldExample; name=mainFrame !-- frame src=http://192.168.0.12:8080/examples/servlet/HelloWorldExample; name=leftFrame scrolling=NO noresize frame src=http://192.168.0.12:8080/examples/servlet/HelloWorldExample; name=mainFrame -- /frameset /html - end of test.html I put the test.html in the examples context directory, then call it by http://localhost:8080/examples/test.html;, the output result in the browser is very unstable, one frame or both of them are not displayed in the browser and sometime the display is correct. The browser that I used is IE 6.0.2800.1106 and Mozilla 1.2.1(Build ID: 2002113012) My JDK version is SUN JDK1.3.1_04. My OperationSystem is Windows2000 Professional with SP3 My Tomcat version is 4.1.17, the .exe file downloaded from the jakarta.apache.org/build. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15470] - The result of servlet called from a framed html page is unstable
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=15470. 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=15470 The result of servlet called from a framed html page is unstable --- Additional Comments From [EMAIL PROTECTED] 2002-12-18 03:39 --- Created an attachment (id=4212) Put the test.html in the examples context directory -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[ANN] Apache Tomcat 4.1.17 Stable released
The Tomcat Team announces the immediate availability of Apache Tomcat 4.1.17 Stable. Tomcat 4.1.17 includes many bugfixes and performance tweaks over Tomcat 4.1.12. Please see the release notes for a complete list of the changes. Downloads (source and binaries): http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.17/ Release notes: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.17/RELEASE-NOTES Important note: When upgrading from another Tomcat 4.x release, the Tomcat work directory must be cleared. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Upgrade to Tomcat 4.1.17 - server has reset connection
I upgraded my site to use Tomcat 4.1.17 tonight. While this fixed all my previous ClassNotFound errors for the hsql jdbc driver (in Tomcat 4.0.6), I started getting a new error: 17-Dec-2002 10:02:52 PM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection I don't know if this is a Tomcat bug or if it's something in my application (Roller). It seems to occur when someone views the site, but it doesn't seem to affect the site at all. Thanks, Matt
Re: Upgrade to Tomcat 4.1.17 - server has reset connection
Matt Raible wrote: I upgraded my site to use Tomcat 4.1.17 tonight. While this fixed all my previous ClassNotFound errors for the hsql jdbc driver (in Tomcat 4.0.6), I started getting a new error: 17-Dec-2002 10:02:52 PM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection I don't know if this is a Tomcat bug or if it's something in my application (Roller). It seems to occur when someone views the site, but it doesn't seem to affect the site at all. I assume you are using Apache 1.3 ? This is a message indicating that the web server has been restarted. Probably we should downgrade the message to debug, since this is normal for apache ( it is not normal for other servers ). Apache has a config option to restart itself after a number of requests - to avoid memory leaks on some OSes. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Thread priority
Thanks for the link Filip. It is specific to JVM 1.4.1, but has alot of good information. The problem is that there is no one good set of jvm args to tune memory and GC, it really depends on so many things. Hardware, OS, memory, applications, etc. But there are some general rules that can be distilled from this. Regards, Glenn Filip Hanik wrote: here is a good link about the different VM settings for the GC. should be worth trying out the different ones to see which one is best for Tomcat http://wireless.java.sun.com/midp/articles/garbagecollection2/ Filip ~ Namaste - I bow to the divine in you ~ Filip Hanik Software Architect www.filip.net -Original Message- From: Peter Lin [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 17, 2002 6:55 AM To: Tomcat Developers List Subject: Re: Thread priority My 2 cents. I rather a server deny connections and keep on running than accept connections until it dies :) peter lin Remy Maucherat [EMAIL PROTECTED] wrote:Glenn Nielsen wrote: Is there a reported bug you are trying to address? Not really. The test here reported a lot of connection failures: http://webperformanceinc.com/library/ServletReport/ Tomcat 4.1.17 should improve the results over 4.1.12 (it's faster and would probably lower slightly GC), but I think the number of errors was higher than it should have been. This could be caused by GC, or possibly because the accepting thread couldn't get the job done, or some other unknown factor. I have not noticed any problems related to thread scheduling with the medium volume site I administer. It is possible that this change could cause threads other than the socket accept thread to be starved. I would be -1 for making this change unless there is a significant reported bug that these changes would address. If it ain't broke, don't fix it. ;-) Remy -- To unsubscribe, e-mail: For additional commands, e-mail: - Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now -- 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 15474] New: - tomcatAuthentication ignored for Coyote JK 2 connector
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15474. 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=15474 tomcatAuthentication ignored for Coyote JK 2 connector Summary: tomcatAuthentication ignored for Coyote JK 2 connector Product: Tomcat 4 Version: 4.1.17 Platform: All OS/Version: All Status: NEW Severity: Blocker Priority: Other Component: Connector:Coyote JK 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] We have a patched Tomcat 4.1.12 working fine for us (the patch is to make request.getSheme() return https when appropriate under the Coyote JK 2 connector) with mod_jk 1.2.1 and Apache 2.0.43 (and 1.3.27) on Windows. Hoping to eliminate the need for the patch, I tried 4.1.17. All went well until I tried to authenticate. We use Apache for authentication and need to set tomcatAuthentication=false on the connector. The Coyote JK 2 (port 8009 as per default) connector ignores this attribute in 4.1.17, whereas it obeys it in 4.1.12. Just about everything else is held constant between these two versions in terms of setup, so I am 99.99% certain this is a new Tomcat 4.1.x bug. Patches or even hints as to where to look would be appreciated. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15470] - The result of servlet called from a framed html page is unstable
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=15470. 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=15470 The result of servlet called from a framed html page is unstable [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-12-18 06:56 --- Frames are a client side thing. Not surprisingly, this works fine for me (with Mozilla and IE); I assume there's a more obvious problem with your setup. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15464] - CoyoteResponse.encodeURL fails to encode relative paths.
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=15464. 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=15464 CoyoteResponse.encodeURL fails to encode relative paths. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-12-18 07:22 --- I cannot reproduce this. Adding: %= response.encodeURL( myTest.jsp ) % %= response.encodeURL( /myTest.jsp ) % to the example date.jsp does not cause any error. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15475] New: - JAR file in WEB-INF not be loaded
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=15475. 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=15475 JAR file in WEB-INF not be loaded Summary: JAR file in WEB-INF not be loaded Product: Tomcat 4 Version: 4.1.17 Platform: Other OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I modified mail.jar to compatible with my application and placed it in /WEB-INF/lib. It worked perfectly under tomcat 4.0.3 and jdk1.3.1_06. When I migrated to tomcat 4.1.17, it seemed my new mail.jar would not be loaded. Tomcat loaded mail.jar in /common/lib instead of using /WEB-INF/lib. As I know, jar files in /WEB-INF/lib must be loaded before jar files in /common/lib. Is this bug? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
