Creating tomcat VFS
Hi, I'm working for quite some time on the light-weight VFS layer (with the java.io.* as the only provider at the moment) to be used as the Tomcat's physical file system access. The ultimate goal is to be able to run the Tomcat on top of things like Hadoop or similar distributed file systems (eg. GFS) by just using the provider module. Now, the amount of changes is pretty huge but it involves mostly changing the java.io.* with the o.a.t.vfs.* counterparts. Since this "Pseudo VFS" has exactly the same API (with the Java7 additions), no functional code change is needed. Sure there are some additional config directives used to define which parts are using which vfs provider as default. (or by just using the root="file://web/apps" or hdfs://:/web/apps notion for non-clustered environments) I'd like to create a sandbox project for that (was thinking of /sandbox/tomcat-vfs) Comments? Regards -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Creating tomcat VFS
On 15/10/2010 08:02, Mladen Turk wrote: > Hi, > > I'm working for quite some time on the light-weight > VFS layer (with the java.io.* as the only provider at > the moment) to be used as the Tomcat's physical file > system access. The ultimate goal is to be able to run > the Tomcat on top of things like Hadoop or similar distributed > file systems (eg. GFS) by just using the provider module. Sounds interesting. What is the use case? Resilience? How far does just a DirContext implementation get you? > Now, the amount of changes is pretty huge but it involves > mostly changing the java.io.* with the o.a.t.vfs.* > counterparts. "huge" makers me nervous but it if is mostly search and replace that is less of a concern. Any feeling at the moment to the amount of overhead this adds? > Since this "Pseudo VFS" has exactly the same API > (with the Java7 additions), no functional code change is needed. > Sure there are some additional config directives used > to define which parts are using which vfs provider as default. > (or by just using the > root="file://web/apps" or hdfs://:/web/apps > notion for non-clustered environments) > > I'd like to create a sandbox project for that > (was thinking of /sandbox/tomcat-vfs) +1. If there are any re-factorings that would make this easier then we should look at the feasibility of putting them in trunk. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Creating tomcat VFS
On 10/15/2010 09:58 AM, Mark Thomas wrote: On 15/10/2010 08:02, Mladen Turk wrote: Hi, I'm working for quite some time on the light-weight VFS layer (with the java.io.* as the only provider at the moment) to be used as the Tomcat's physical file system access. The ultimate goal is to be able to run the Tomcat on top of things like Hadoop or similar distributed file systems (eg. GFS) by just using the provider module. Sounds interesting. What is the use case? Resilience? Current users that use NFS for sharing the common data among cluster of Tomcat's. Real cloud deployments. Some more which I cannot talk about at this moment :) How far does just a DirContext implementation get you? Depending on the provider and the API he offers. Basically anything that touches the file system directly has it's wrapper in o.a.t.vfs Yes, for some providers it can be very complex, but at the end it's plugable module, so outside of the core Tomcat, and as such does not influence the Tomcat code stability. Now, the amount of changes is pretty huge but it involves mostly changing the java.io.* with the o.a.t.vfs.* counterparts. "huge" makers me nervous but it if is mostly search and replace that is less of a concern. Any feeling at the moment to the amount of overhead this adds? For default provider which wraps the java.io at all, almost none. Majority is just ruled out by JIT. For others if you use a custom zip layer the load time can fall dramatically. Sure if running on top of Hadoop things will be noticeably slowly then on physical file system, but we are comparing apples and pears. As final, it'll be in the sandbox, and I really have no plan to touch the core Tomcat until proven stable and performant, and then eventually accepted. Regards -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[VOTE] Release Apache Tomcat 7.0.4
The proposed Apache Tomcat 7.0.4 release is now available for voting. It can be obtained from: http://people.apache.org/~markt/dev/tomcat-7/v7.0.4/ The svn tag is: http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_4/ As with previous votes, I have included a stable option below although my personal inclination is still to vote beta. The proposed 7.0.4 release is: [ ] Broken - do not release [ ] Alpha - go ahead and release as 7.0.4 Alpha [ ] Beta - go ahead and release as 7.0.4 Beta [ ] Stable - go ahead and release as 7.0.4 Stable This vote will run until 10.00 UTC Wednesday 20th October (3 working days). Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Creating tomcat VFS
2010/10/15 Mladen Turk : > Hi, > > > I'm working for quite some time on the light-weight > VFS layer (with the java.io.* as the only provider at > the moment) to be used as the Tomcat's physical file > system access. The ultimate goal is to be able to run > the Tomcat on top of things like Hadoop or similar distributed > file systems (eg. GFS) by just using the provider module. > > Now, the amount of changes is pretty huge but it involves > mostly changing the java.io.* with the o.a.t.vfs.* > counterparts. > Since this "Pseudo VFS" has exactly the same API > (with the Java7 additions), no functional code change is needed. > Sure there are some additional config directives used > to define which parts are using which vfs provider as default. > (or by just using the > root="file://web/apps" or hdfs://:/web/apps > notion for non-clustered environments) > > I'd like to create a sandbox project for that > (was thinking of /sandbox/tomcat-vfs) > > Comments? Seems to me a good idea, I'm also investigate stuff around VFS and Hadoop. Since the VFS word could be an issue, term should be updated may be (Wrapper FS or whatever), but I like the idea. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Creating tomcat VFS
I remembered Mladen and VFS discussion, elsewhere. Google confirmed it to me : http://www.mail-archive.com/commons-...@jakarta.apache.org/msg82888.html Your code is still http://apvfs.sourceforge.net/ ? - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: svn commit: r1005192 - /tomcat/tc6.0.x/trunk/STATUS.txt
2010/10/14 Mark Thomas : > On 14/10/2010 09:02, Konstantin Kolinko wrote: >> OK. Looks that the patch is working. The snoop.jsp displays the full >> original path as "Request URI" (aka request.getRequestURI()). >> >> Other things there >> 1) Add http://svn.apache.org/viewvc?rev=1022389&view=rev > +1 > >> 2) protected method CoyoteAdapter.parseSessionId(..) is no more used. >> Deprecate it? > +1 > >> 3) path parameters that have no '=' in them are not added to the map. > Could you find a definitive reference on how path parameters are defined > for HTTP (i.e. use ';' as the separator, value required/optional, > defining multiple values for one parameter, path segment is/isn't > significant etc.)? I looked but couldn't find anything. > There is RFC 3986 ch.3.3 [1] that I already mentioned, [1] http://tools.ietf.org/html/rfc3986#section-3.3 but that is not specific for HTTP. [1] also shows quite different examples, such as "name;v=1.1" and "name,1.1". The HTTP1.1 RFC 2616 ch.3.2.2 [2] http://tools.ietf.org/html/rfc2616#section-3.2.2 [[[ The semantics are that the identified resource is located at the server listening for TCP connections on that port of that host, and the Request-URI for the resource is abs_path (section 5.1.2). ]]] so abs_path is directly sent to the server as Request-URI. from ch.5.2 of the same RFC 2616 [[[ 5.2 The Resource Identified by a Request The exact resource identified by an Internet request is determined by examining both the Request-URI and the Host header field. ]]] so I think that is up to the server how to interpret the Request-URI and in Tomcat case the "server" is Tomcat+webapp and we pre-interpret that Request-URI before passing it to our applications. My thought regarding Request.pathParameters map is that it is inadequate, but at least it provides an indication that a parameter was present. Though request.getRequestURI().indexOf() will provide such indication as well. I would prefer if your issue can be fixed without introducing this pathParameters map, but I actually do not mind much if the map can be useful for someone. Maybe I am resenting that we are using good names for it, while we might want to refine the API in the future. BTW, will it affect security, that a path is callable by different URIs? Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1022883 - /tomcat/tc6.0.x/trunk/STATUS.txt
Author: kkolinko Date: Fri Oct 15 11:03:54 2010 New Revision: 1022883 URL: http://svn.apache.org/viewvc?rev=1022883&view=rev Log: proposal Modified: tomcat/tc6.0.x/trunk/STATUS.txt Modified: tomcat/tc6.0.x/trunk/STATUS.txt URL: http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=1022883&r1=1022882&r2=1022883&view=diff == --- tomcat/tc6.0.x/trunk/STATUS.txt (original) +++ tomcat/tc6.0.x/trunk/STATUS.txt Fri Oct 15 11:03:54 2010 @@ -276,4 +276,10 @@ PATCHES PROPOSED TO BACKPORT: http://svn.apache.org/viewvc?rev=1022623&view=rev (cache sizes) +1: markt -1: - \ No newline at end of file + +* Do not call reset if the default LogManager is in use + (an additional fix for https://issues.apache.org/bugzilla/show_bug.cgi?id=48716) + Patch by markt. + http://svn.apache.org/viewvc?rev=1005802&view=rev + +1: kkolinko + -1: - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 48716] Embedded Tomcat JULI aggressively resetting default logging configuration
https://issues.apache.org/bugzilla/show_bug.cgi?id=48716 --- Comment #21 from Konstantin Kolinko 2010-10-15 07:19:15 EDT --- I proposed r1005802 for backport to 6.0. Though maybe we can enhance that to print some warning when it happens, or maybe just one warning at startup time. BTW, I have a use case where the default LogManager is useful for us. That is not in production, but during development only. We have several webapps where there is a WEB-INF/classes/logging.properties file that is configured to do not output anything to the console. When we debug those applications it is helpful to use the default LogManager instead of JULI, so that those logging.properties are ignored and all debug output goes to the console. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Tomcat Wiki] Update of "PoweredBy" by ThorstenMarx
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change
notification.
The "PoweredBy" page has been changed by ThorstenMarx.
http://wiki.apache.org/tomcat/PoweredBy?action=diff&rev1=270&rev2=271
--
=== LUXMS ===
{{http://www.luxms.com/luxms/jsp/pictures/logo.jpg}}
[[http://www.luxms.com|LUXMS: Luxury messaging]] - Wide range of wireless
messaging services, including email SMS notification and delivery of important
information from desktop to your phone.
+
+ === Lagerverkauf-Finden ===
+ [[http://www.lagerverkauf-finden.de/|Lagerverkauf-Finden]] - German
Searchsite for factory outlet stores. Based on a custom developed lucene based
nosql database and running on tomcat.
+
+ === HandyBundle-Finden ===
+ [[http://www.handybundle-finden.de/|HandyBundle-Finden]] - German site for
mobile phone bundles. Based on a custom developed lucene based nosql database
and running on tomcat.
=== Maxager ===
[http://www.maxager.com/home.htm ] Maxager's patented enterprise profit
optimization (EPO) solutions help leading companies increase cash and profit
worth 3-5% of revenue.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: svn commit: r1005192 - /tomcat/tc6.0.x/trunk/STATUS.txt
On 15.10.2010 12:51, Konstantin Kolinko wrote: 2010/10/14 Mark Thomas: On 14/10/2010 09:02, Konstantin Kolinko wrote: OK. Looks that the patch is working. The snoop.jsp displays the full original path as "Request URI" (aka request.getRequestURI()). Other things there 1) Add http://svn.apache.org/viewvc?rev=1022389&view=rev +1 2) protected method CoyoteAdapter.parseSessionId(..) is no more used. Deprecate it? +1 3) path parameters that have no '=' in them are not added to the map. Could you find a definitive reference on how path parameters are defined for HTTP (i.e. use ';' as the separator, value required/optional, defining multiple values for one parameter, path segment is/isn't significant etc.)? I looked but couldn't find anything. In addition to what Konstantin wrote: though I couldn't find a good authoritative reference concerning path parameter definition for HTTP URIs, I stumbled over a Tomcat discussion from 4 years ago: http://marc.info/?t=11534301641&r=1&w=2 http://marc.info/?t=11562101451&r=1&w=2 Regards, Rainer - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Apache alpha and mod_jk
Hi Tomcat dev, We have a scenario presently that is causing us some difficulties. Env is SPARC Solaris10, gcc. We wish to use the current alpha build of Apache because it includes new features in mod_cache that we want to use, they are checked into trunk. http://svn.apache.org/viewvc/httpd/httpd/trunk/ We also wish to use mod_jk to connect to Tomcat. Our issue is that we cannot get any version of mod_jk to work with this Apache. We have tried the pre-compiled binaries of mod_jk, and tried to compile our own mod_jk. Both scenarios are failing. When we use the pre-compiled binary mod_jk.so provided by the Tomcat connectors. http://archive.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/solaris/jk-1.2.30/sparc/ mod_jk-1.2.30-httpd-2.2.X.so bash-3.00# ./apachectl configtest httpd: Syntax error on line 139 of /apps/apache-2.3.8/conf/httpd.conf: Cannot load /apps/apache-2.3.8/modules/mod_jk.so into server: ld.so.1: httpd: fatal: relocation error: file /apps/apache-2.3.8/modules/mod_jk.so: symbol ap_log_error: referenced symbol not found bash-3.00# and when we try to compile mod_jk to work with the Apache it fails with the following errors. This mod_jk compiles fine for Apache 2.2 /home/tomcat-connectors-1.2.30-src/native#./configure --with-apxs=/apps/apache-2.3.8/bin/apxs no errors /home/tomcat-connectors-1.2.30-src/native#make Making all in common /apps/apache-2.3.8/build/libtool --silent --mode=compile gcc -std=gnu99 -I/apps/apache-2.3.8/include -g -O2 -g -O2 -DHAVE_APR -I/apps/apache-2.3.8/include -I/apps/apache-2.3.8/include -g -O2 -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE -I /include -I /include/ -c jk_ajp12_worker.c -o jk_ajp12_worker.lo /apps/apache-2.3.8/build/libtool --silent --mode=compile gcc -std=gnu99 -I/apps/apache-2.3.8/include -g -O2 -g -O2 -DHAVE_APR -I/apps/apache-2.3.8/include -I/apps/apache-2.3.8/include -g -O2 -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE -I /include -I /include/ -c jk_connect.c -o jk_connect.lo /apps/apache-2.3.8/build/libtool --silent --mode=compile gcc -std=gnu99 -I/apps/apache-2.3.8/include -g -O2 -g -O2 -DHAVE_APR -I/apps/apache-2.3.8/include -I/apps/apache-2.3.8/include -g -O2 -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE -I /include -I /include/ -c jk_msg_buff.c -o jk_msg_buff.lo /apps/apache-2.3.8/build/libtool --silent --mode=compile gcc -std=gnu99 -I/apps/apache-2.3.8/include -g -O2 -g -O2 -DHAVE_APR -I/apps/apache-2.3.8/include -I/apps/apache-2.3.8/include -g -O2 -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE -I /include -I /include/ -c jk_util.c -o jk_util.lo /apps/apache-2.3.8/build/libtool --silent --mode=compile gcc -std=gnu99 -I/apps/apache-2.3.8/include -g -O2 -g -O2 -DHAVE_APR -I/apps/apache-2.3.8/include -I/apps/apache-2.3.8/include -g -O2 -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE -I /include -I /include/ -c jk_ajp13.c -o jk_ajp13.lo /apps/apache-2.3.8/build/libtool --silent --mode=compile gcc -std=gnu99 -I/apps/apache-2.3.8/include -g -O2 -g -O2 -DHAVE_APR -I/apps/apache-2.3.8/include -I/apps/apache-2.3.8/include -g -O2 -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE -I /include -I /include/ -c jk_pool.c -o jk_pool.lo /apps/apache-2.3.8/build/libtool --silent --mode=compile gcc -std=gnu99 -I/apps/apache-2.3.8/include -g -O2 -g -O2 -DHAVE_APR -I/apps/apache-2.3.8/include -I/apps/apache-2.3.8/include -g -O2 -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE -I /include -I /include/ -c jk_worker.c -o jk_worker.lo /apps/apache-2.3.8/build/libtool --silent --mode=compile gcc -std=gnu99 -I/apps/apache-2.3.8/include -g -O2 -g -O2 -DHAVE_APR -I/apps/apache-2.3.8/include -I/apps/apache-2.3.8/include -g -O2 -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE -I /include -I /include/ -c jk_ajp13_worker.c -o jk_ajp13_worker.lo /apps/apache-2.3.8/build/libtool --silent --mode=compile gcc -std=gnu99 -I/apps/apache-2.3.8/include -g -O2 -g -O2 -DHAVE_APR -I/apps/apache-2.3.8/include -I/apps/apache-2.3.8/include -g -O2 -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE -I /include -I /include/ -c jk_lb_worker.c -o jk_lb_worker.lo /apps/apache-2.3.8/build/libtool --silent --mode=compile gcc -std=gnu99 -I/apps/apache-2.3.8/include -g -O2 -g -O2 -DHAVE_APR -I/apps/apache-2.3.8/include -I/apps/apache-2.3.8/include -g -O2 -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE -I /include -I /include/ -c jk_sockbuf.c -o jk_sockbuf.lo /apps/apache-2.3.8/build/libtool --silent --mode=compile gcc -std=gnu99 -I/apps/apache-2.3.8/include -g -O2 -g -O2 -DHAVE_APR -I/apps/apache-2.3.8/include -I/apps/apache-2.3.8/include -g -O2 -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE -I /include -I /include/ -c jk_map.c -o jk_map.lo /apps/apache-2.3.8/build/
JSESSIONID Cookie handle customizing
Hi Folks! I want to put some information on the JSESSIONID that tomcat generates. I'm using aspect programming so I don´t need to change the tomcat code itself. The thing is that I found many points where tomcat handle this information, I checked and notice that the head parser is made on the method parseSessionId and parseSessionCookiesId in the class org.apache.catalina.connector.CoyoteAdapter. I'm not convinced that there is the perfect point to make my code injection. I need to find out the exactly point that this information (Cookie JSESSIONID=22) is received by Tomcat and where tomcat sends this information to the browser, in other words, the first contact with this information when browser sends and the last contact before sending to browser. Thanks. Juliano PS: Sorry if this is not the adequate list, but the user one I got no answer. PS2: Sorry for duplicated message. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Creating tomcat VFS
Are you going to replace DirContext ? If yes - great, but please first send a quick summary comparing your API with the other VFS around in apache. I think commons has few targets, including a hdfs, I remember there are more. If no - not sure what's the point of replacing java.io impl, I assume you just need to add a DirContext for hadoop. I remember many years back I was arguing in favor of DirContext - pro arguments were "it's a standard", bundled in JDK, probably more target implementations will be available, etc. I think Remy was arguing that it's too complex and not a perfect fit. I guess he was right :-) Costin On Fri, Oct 15, 2010 at 12:02 AM, Mladen Turk wrote: > Hi, > > > I'm working for quite some time on the light-weight > VFS layer (with the java.io.* as the only provider at > the moment) to be used as the Tomcat's physical file > system access. The ultimate goal is to be able to run > the Tomcat on top of things like Hadoop or similar distributed > file systems (eg. GFS) by just using the provider module. > > Now, the amount of changes is pretty huge but it involves > mostly changing the java.io.* with the o.a.t.vfs.* > counterparts. > Since this "Pseudo VFS" has exactly the same API > (with the Java7 additions), no functional code change is needed. > Sure there are some additional config directives used > to define which parts are using which vfs provider as default. > (or by just using the > root="file://web/apps" or hdfs://:/web/apps > notion for non-clustered environments) > > I'd like to create a sandbox project for that > (was thinking of /sandbox/tomcat-vfs) > > Comments? > > > Regards > -- > ^TM > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
Re: Creating tomcat VFS
On Fri, 2010-10-15 at 07:57 -0700, Costin Manolache wrote: > I remember many years back I was arguing in favor of DirContext - pro > arguments were > "it's a standard", bundled in JDK, probably more target implementations will > be available, etc. > I think Remy was arguing that it's too complex and not a perfect fit. I > guess he was right :-) I ended up doing it after complaining for a while. I think it was a reasonable option at the time, and it was possible to make it fast enough. Rémy - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: JSESSIONID Cookie handle customizing
On 15/10/2010 15:49, Juliano Daloia de Carvalho wrote: > PS: Sorry if this is not the adequate list, but the user one I got no answer. You only asked there half an hour ago. p 0x62590808.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: Creating tomcat VFS
On 10/15/2010 04:57 PM, Costin Manolache wrote: Are you going to replace DirContext ? If yes - great, but please first send a quick summary comparing your API with the other VFS around in apache. I think commons has few targets, including a hdfs, I remember there are more. Well it's not a VFS, and it doesn't have an API. The API is java.io + java.util.zio with o.a.t.vfs namespace instead java.io (Frankly didn't came up to the DirContext in experiment, but it shouldn't be any different then others) So the o.a.t.vfs.File is java.io.File in case the provider in "transparent". In case it's "raw" (Those names are mine) the File is o.a.t.vfs.providers.raw.File which only makes sure that it doesn't cross the "root" mount point. The point here is that provider *can* use commons vfs, and that's the idea, but then again the Hadoop's hdfs has a descent API on it's own. Regards -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Creating tomcat VFS
On Fri, Oct 15, 2010 at 8:24 AM, Mladen Turk wrote: > On 10/15/2010 04:57 PM, Costin Manolache wrote: > >> Are you going to replace DirContext ? >> >> If yes - great, but please first send a quick summary comparing your API >> with the other VFS >> around in apache. I think commons has few targets, including a hdfs, I >> remember there are more. >> >> > Well it's not a VFS, and it doesn't have an API. > The API is java.io + java.util.zio with o.a.t.vfs namespace > instead java.io > (Frankly didn't came up to the DirContext in experiment, > but it shouldn't be any different then others) > > I'm not very comfortable with another layer below DirContext... Big +1 if you get rid of DirContext and replace it with your File. I did an experiment in lite - it is not very hard actually to replace DirContext with raw File. The main problem was that java.io - like DirContext - is an old and not very fit API, lot of cruft, blocking, etc. In any case - having a summary of the other VFS APIs would help a lot. Is there any existing API that support non-blocking access to files / streams ? Costin > So the o.a.t.vfs.File is java.io.File in case the provider > in "transparent". In case it's "raw" (Those names are mine) > the File is o.a.t.vfs.providers.raw.File which only makes > sure that it doesn't cross the "root" mount point. > > The point here is that provider *can* use commons vfs, > and that's the idea, but then again the Hadoop's hdfs has a > descent API on it's own. > > > > Regards > -- > ^TM > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
Re: Creating tomcat VFS
On Fri, Oct 15, 2010 at 8:13 AM, Remy Maucherat wrote: > On Fri, 2010-10-15 at 07:57 -0700, Costin Manolache wrote: > > I remember many years back I was arguing in favor of DirContext - pro > > arguments were > > "it's a standard", bundled in JDK, probably more target implementations > will > > be available, etc. > > I think Remy was arguing that it's too complex and not a perfect fit. I > > guess he was right :-) > > I ended up doing it after complaining for a while. I think it was a > reasonable option at the time, and it was possible to make it fast > enough. > > But I hope you agree you were right, at least in the long term :-) Costin > Rémy > > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
svn commit: r1022975 - in /tomcat/jk/trunk: native/apache-2.0/mod_jk.c xdocs/miscellaneous/changelog.xml
Author: rjung
Date: Fri Oct 15 15:51:11 2010
New Revision: 1022975
URL: http://svn.apache.org/viewvc?rev=1022975&view=rev
Log:
Add support for Apache 2.3/2.4.
Changes needed due to private use of the macro
APLOG_MARK which now has a different definition.
Modified:
tomcat/jk/trunk/native/apache-2.0/mod_jk.c
tomcat/jk/trunk/xdocs/miscellaneous/changelog.xml
Modified: tomcat/jk/trunk/native/apache-2.0/mod_jk.c
URL:
http://svn.apache.org/viewvc/tomcat/jk/trunk/native/apache-2.0/mod_jk.c?rev=1022975&r1=1022974&r2=1022975&view=diff
==
--- tomcat/jk/trunk/native/apache-2.0/mod_jk.c (original)
+++ tomcat/jk/trunk/native/apache-2.0/mod_jk.c Fri Oct 15 15:51:11 2010
@@ -123,6 +123,8 @@
#define NULL_FOR_EMPTY(x) ((x && !strlen(x)) ? NULL : x)
#define STRNULL_FOR_NULL(x) ((x) ? (x) : "(null)")
#define JK_LOG_LOCK_KEY ("jk_log_lock_key")
+#define JKLOG_MARK __FILE__,__LINE__
+
/*
* If you are not using SSL, comment out the following line. It will make
* apache run faster.
@@ -131,6 +133,11 @@
*/
#define ADD_SSL_INFO
+/* Needed for Apache 2.3/2.4 per-module log config */
+#ifdef APLOG_USE_MODULE
+APLOG_USE_MODULE(jk);
+#endif
+
/* module MODULE_VAR_EXPORT jk_module; */
AP_MODULE_DECLARE_DATA module jk_module;
@@ -636,9 +643,17 @@ static void jk_error_exit(const char *fi
ch++;
}
+#if (MODULE_MAGIC_NUMBER_MAJOR >= 20100606)
+ap_log_error(file, line, APLOG_MODULE_INDEX, level, 0, s, res);
+#else
ap_log_error(file, line, level, 0, s, res);
+#endif
if ( s ) {
+#if (MODULE_MAGIC_NUMBER_MAJOR >= 20100606)
+ap_log_error(file, line, APLOG_MODULE_INDEX, level, 0, NULL, res);
+#else
ap_log_error(file, line, level, 0, NULL, res);
+#endif
}
/* Exit process */
@@ -2826,7 +2841,7 @@ static void *merge_jk_config(apr_pool_t
if (overrides->uri_to_context && overrides->mountcopy == JK_TRUE) {
/* jk_map_copy() preserves existing entries in overrides map */
if (jk_map_copy(base->uri_to_context, overrides->uri_to_context) ==
JK_FALSE) {
-jk_error_exit(APLOG_MARK, APLOG_EMERG, overrides->s, p,
"Memory error");
+jk_error_exit(JKLOG_MARK, APLOG_EMERG, overrides->s, p,
"Memory error");
}
if (!overrides->mount_file)
overrides->mount_file = base->mount_file;
@@ -3269,7 +3284,7 @@ static int jk_post_config(apr_pool_t * p
if (sconf->uri_to_context) {
if (!uri_worker_map_alloc(&(sconf->uw_map),
sconf->uri_to_context,
sconf->log))
-jk_error_exit(APLOG_MARK, APLOG_EMERG, srv,
+jk_error_exit(JKLOG_MARK, APLOG_EMERG, srv,
srv->process->pool, "Memory error");
if (sconf->options & JK_OPT_REJECTUNSAFE)
sconf->uw_map->reject_unsafe = 1;
Modified: tomcat/jk/trunk/xdocs/miscellaneous/changelog.xml
URL:
http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/miscellaneous/changelog.xml?rev=1022975&r1=1022974&r2=1022975&view=diff
==
--- tomcat/jk/trunk/xdocs/miscellaneous/changelog.xml (original)
+++ tomcat/jk/trunk/xdocs/miscellaneous/changelog.xml Fri Oct 15 15:51:11 2010
@@ -60,6 +60,9 @@
Common: Don't destroy errno during trace logging. (rjung)
+Apache: Add support for Apache 2.3/2.4. (rjung)
+
+
Apache: Added version number resource for mod_jk.so on Windows. (timw)
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Apache alpha and mod_jk
Hi Damon, On 15.10.2010 16:13, Damon Green wrote: Hi Tomcat dev, We have a scenario presently that is causing us some difficulties. Env is SPARC Solaris10, gcc. We wish to use the current alpha build of Apache because it includes new features in mod_cache that we want to use, they are checked into trunk. http://svn.apache.org/viewvc/httpd/httpd/trunk/ Good! We also wish to use mod_jk to connect to Tomcat. Even better :) Our issue is that we cannot get any version of mod_jk to work with this Apache. We have tried the pre-compiled binaries of mod_jk, and tried to compile our own mod_jk. Both scenarios are failing. When we use the pre-compiled binary mod_jk.so provided by the Tomcat connectors. http://archive.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/solaris/jk-1.2.30/sparc/ mod_jk-1.2.30-httpd-2.2.X.so bash-3.00# ./apachectl configtest httpd: Syntax error on line 139 of /apps/apache-2.3.8/conf/httpd.conf: Cannot load /apps/apache-2.3.8/modules/mod_jk.so into server: ld.so.1: httpd: fatal: relocation error: file /apps/apache-2.3.8/modules/mod_jk.so: symbol ap_log_error: referenced symbol not found bash-3.00# That's expected, binaries are not compatible between middle releases. and when we try to compile mod_jk to work with the Apache it fails with the following errors. This mod_jk compiles fine for Apache 2.2 ... Is anyone able to shed any light on this issue? Is it likely that we will be able to get mod_jk to work with the latest Apache code? Yes, one of the macros copied in from Apache to mod_jk changed its meaning, that's why the build breaks. It's a known and documented issue and I applied the following change to mod_jk right now: http://svn.apache.org/viewvc?view=revision&revision=1022975 Can you try this patch? I expect it applies cleanly to 1.2.30 also, but didn't actually test it. There is still some constness warning, but I hope it'll work nevertheless. Any feedback would be helpful. Thanks for bringing this up! Regards, Rainer - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Apache alpha and mod_jk
On Fri, Oct 15, 2010 at 4:56 PM, Rainer Jung wrote: > Hi Damon, > > > On 15.10.2010 16:13, Damon Green wrote: > >> Hi Tomcat dev, >> >> We have a scenario presently that is causing us some difficulties. >> >> Env is SPARC Solaris10, gcc. >> >> We wish to use the current alpha build of Apache because it includes >> new features in mod_cache that we want to use, they are checked into >> trunk. http://svn.apache.org/viewvc/httpd/httpd/trunk/ >> > > Good! > > > We also wish to use mod_jk to connect to Tomcat. >> > > Even better :) > > > Our issue is that we cannot get any version of mod_jk to work with this >> Apache. >> >> We have tried the pre-compiled binaries of mod_jk, and tried to >> compile our own mod_jk. Both scenarios are failing. >> >> When we use the pre-compiled binary mod_jk.so provided by the Tomcat >> connectors. >> >> >> http://archive.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/solaris/jk-1.2.30/sparc/ >> >> mod_jk-1.2.30-httpd-2.2.X.so >> >> bash-3.00# ./apachectl configtest >> httpd: Syntax error on line 139 of /apps/apache-2.3.8/conf/httpd.conf: >> Cannot load /apps/apache-2.3.8/modules/mod_jk.so into server: ld.so.1: >> httpd: fatal: relocation error: file >> /apps/apache-2.3.8/modules/mod_jk.so: symbol ap_log_error: referenced >> symbol not found >> bash-3.00# >> > > That's expected, binaries are not compatible between middle releases. > > > and when we try to compile mod_jk to work with the Apache it fails with >> the >> following errors. This mod_jk compiles fine for Apache 2.2 >> > > ... > > > Is anyone able to shed any light on this issue? Is it likely that we will >> be >> able to get mod_jk to work with the latest Apache code? >> > > Yes, one of the macros copied in from Apache to mod_jk changed its meaning, > that's why the build breaks. It's a known and documented issue and I applied > the following change to mod_jk right now: > > http://svn.apache.org/viewvc?view=revision&revision=1022975 > > Can you try this patch? I expect it applies cleanly to 1.2.30 also, but > didn't actually test it. There is still some constness warning, but I hope > it'll work nevertheless. Any feedback would be helpful. > > Thanks for bringing this up! > > Regards, > > Rainer > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > Thanks Rainer, were going to try that now. Will report back soon. Might be Monday now ;) Regards Damon.
Re: Creating tomcat VFS
On Fri, 2010-10-15 at 08:43 -0700, Costin Manolache wrote: > But I hope you agree you were right, at least in the long term :-) Who cares about the long term, nobody uses 10 years old code. Oh, wait ;) Rémy - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1023020 - /tomcat/jk/trunk/native/common/jk_map.c
Author: rjung
Date: Fri Oct 15 16:59:40 2010
New Revision: 1023020
URL: http://svn.apache.org/viewvc?rev=1023020&view=rev
Log:
Fix test that returns always true.
Only a problem, if the token to trim were actually
empty.
Modified:
tomcat/jk/trunk/native/common/jk_map.c
Modified: tomcat/jk/trunk/native/common/jk_map.c
URL:
http://svn.apache.org/viewvc/tomcat/jk/trunk/native/common/jk_map.c?rev=1023020&r1=1023019&r2=1023020&view=diff
==
--- tomcat/jk/trunk/native/common/jk_map.c (original)
+++ tomcat/jk/trunk/native/common/jk_map.c Fri Oct 15 16:59:40 2010
@@ -634,10 +634,13 @@ static size_t trim(char *s)
/* check for empty strings */
if (!(i = strlen(s)))
return 0;
-for (i = i - 1; (i >= 0) &&
+for (i = i - 1; (i > 0) &&
isspace((int)((unsigned char)s[i])); i--);
+if ((i > 0) || !isspace((int)((unsigned char)s[i]))) {
+ i++;
+}
-s[i + 1] = '\0';
+s[i] = '\0';
for (i = 0; ('\0' != s[i]) &&
isspace((int)((unsigned char)s[i])); i++);
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.4
On 15/10/2010 09:47, Mark Thomas wrote: > The proposed Apache Tomcat 7.0.4 release is now available for voting. > > It can be obtained from: > http://people.apache.org/~markt/dev/tomcat-7/v7.0.4/ > The svn tag is: > http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_4/ > > As with previous votes, I have included a stable option below although > my personal inclination is still to vote beta. > > The proposed 7.0.4 release is: > > [ ] Broken - do not release > [ ] Alpha - go ahead and release as 7.0.4 Alpha > [X] Beta - go ahead and release as 7.0.4 Beta > [ ] Stable - go ahead and release as 7.0.4 Stable > > This vote will run until 10.00 UTC Wednesday 20th October (3 working days). Sevlet TCK passes with security manager for HTTP BIO, NIO & APR/native Sevlet TCK passes with security manager for AJP BIO & APR/native JSP TCK passes with security manager EL TCK passes with security manager The bug count is currently nice and low. If we don't see any nasty issues between this and the next release I'd be tempted to start voting stable. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1023055 - in /tomcat/site/trunk: docs/index.html xdocs/index.xml
Author: markt Date: Fri Oct 15 18:18:42 2010 New Revision: 1023055 URL: http://svn.apache.org/viewvc?rev=1023055&view=rev Log: Remove out of date links. Happy to replace them with something more recent if someone points it out. Modified: tomcat/site/trunk/docs/index.html tomcat/site/trunk/xdocs/index.xml Modified: tomcat/site/trunk/docs/index.html URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/index.html?rev=1023055&r1=1023054&r2=1023055&view=diff == --- tomcat/site/trunk/docs/index.html (original) +++ tomcat/site/trunk/docs/index.html Fri Oct 15 18:18:42 2010 @@ -3,18 +3,18 @@ Apache Tomcat - Welcome! - - - + + + - - + + http://tomcat.apache.org/";> - + @@ -25,28 +25,28 @@ http://www.apache.org/";> -http://www.apache.org/images/asf-logo.gif"; /> +http://www.apache.org/images/asf-logo.gif"; align="right" alt="Apache Logo" border="0"/> -http://www.google.com/search";> - - - +http://www.google.com/search"; method="get"> + + + - + - + - + Apache Tomcat @@ -178,11 +178,11 @@ - - + + - + @@ -197,8 +197,9 @@ -Apache Tomcat is an open source software implementation of the http://java.sun.com/products/servlets";>Java Servlet and http://java.sun.com/products/jsp";>JavaServer Pages technologies. -The Java Servlet and JavaServer Pages specifications are developed under the +Apache Tomcat is an open source software implementation of the Java Servlet +and JavaServer Pages technologies. The Java Servlet and JavaServer Pages +specifications are developed under the http://jcp.org/en/introduction/overview";>Java Community Process. @@ -219,14 +220,14 @@ and their stories are listed on the - + - + - + @@ -235,8 +236,8 @@ and their stories are listed on the - - + + 2010-08-11 @@ -262,14 +263,14 @@ content directly in a web application (a - + - + - + @@ -278,8 +279,8 @@ content directly in a web application (a - - + + 2010-07-22 @@ -303,14 +304,14 @@ Apache Tomcat. This release includes bug - + - + - + @@ -319,8 +320,8 @@ Apache Tomcat. This release includes bug - - + + 2010-09-16 @@ -345,14 +346,14 @@ fixes over Apache Tomcat 5.5.30. - + - + - + @@ -361,8 +362,8 @@ fixes over Apache Tomcat 5.5.30. - - + + 2010-05-27 @@ -373,7 +374,7 @@ fixes over Apache Tomcat 5.5.30. http://na.apachecon.com/c/acna2010/";> - + http://na.apachecon.com/c/acna2010/";>ApacheCon North America 2010 will be held 1-5 November 2010, at the Westin Peachtree in Atlanta, Georgia, USA. @@ -395,14 +396,14 @@ Additionally we have a + - + @@ -411,8 +412,8 @@ Additionally we have a - + + 2010-03-01 @@ -431,7 +432,7 @@ This release includes mainly bug fixes a ChangeLog for 1.2.30 - + Notice Apache Tomcat Connectors version 1.2.29 was withdrawn from the release due to regression with Microsoft IIS connector. @@ -441,14 +442,14 @@ regression with Microsoft IIS connector. - + - + - + @@ -457,8 +458,8 @@ regression with Microsoft IIS connector. - - + + 2010-02-17 @@ -481,14 +482,14 @@ This version is principally a bugfix rel - + - + - + @@ -511,7 +512,7 @@ This version is principally a bugfix rel - + @@ -520,17 +521,17 @@ This version is principally a bugfix rel - + - + Copyright © 1999-2010, The Apache Software Foundation - + "Apache", the Apache feather, and the Apache Tomcat logo are trademarks of the Apache Software Foundation for our open source software. Modified: tomcat/site/trunk/xdocs/index.xml URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/index.xml?rev=1023055&r1=1023054&r2=1023055&view=diff == --- tomcat/site/trunk/xdocs/index.xml (original) +++ tomcat/site/trunk/xdocs/index.xml Fri Oct 15 18:18:42 2010 @@ -10,10 +10,9 @@ -Apache Tomcat is an open source software implementation of the http://java.sun.com/products/servlets";>Java Servlet and http://java.sun.com/products/jsp";>JavaServer Pages technologies. -The Java Servlet and JavaServer Pages specifications are developed under the +Apache Tomcat is an open source software implementation of the Java Servlet +and JavaServer Pages technologies. The Java Servlet and JavaServer Pages +specifications are developed under the http://jcp.org/en/introduction/overview";>Java Community Process. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1023056 - in /tomcat/site/trunk: docs/whichversion.html xdocs/whichversion.xml
Author: markt Date: Fri Oct 15 18:20:21 2010 New Revision: 1023056 URL: http://svn.apache.org/viewvc?rev=1023056&view=rev Log: Trademark guidelines: "... any overview download pages for the product ... and must include a brief one sentence description of the function of the product." Modified: tomcat/site/trunk/docs/whichversion.html tomcat/site/trunk/xdocs/whichversion.xml Modified: tomcat/site/trunk/docs/whichversion.html URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/whichversion.html?rev=1023056&r1=1023055&r2=1023056&view=diff == --- tomcat/site/trunk/docs/whichversion.html (original) +++ tomcat/site/trunk/docs/whichversion.html Fri Oct 15 18:20:21 2010 @@ -197,9 +197,11 @@ -Different versions of Apache Tomcat are available for different versions -of the Servlet and JSP specifications. The mapping between the specifications -and the respective Apache Tomcat versions is: +Apache Tomcat is an open source software implementation of the Java Servlet +and JavaServer Pages technologies. Different versions of Apache Tomcat are +available for different versions of the Servlet and JSP specifications. The +mapping between the specifications and the respective Apache Tomcat versions is: + Modified: tomcat/site/trunk/xdocs/whichversion.xml URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/whichversion.xml?rev=1023056&r1=1023055&r2=1023056&view=diff == --- tomcat/site/trunk/xdocs/whichversion.xml (original) +++ tomcat/site/trunk/xdocs/whichversion.xml Fri Oct 15 18:20:21 2010 @@ -10,9 +10,11 @@ -Different versions of Apache Tomcat are available for different versions -of the Servlet and JSP specifications. The mapping between the specifications -and the respective Apache Tomcat versions is: +Apache Tomcat is an open source software implementation of the Java Servlet +and JavaServer Pages technologies. Different versions of Apache Tomcat are +available for different versions of the Servlet and JSP specifications. The +mapping between the specifications and the respective Apache Tomcat versions is: + - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1023064 - in /tomcat/site/trunk: docs/index.html xdocs/index.xml
Author: markt Date: Fri Oct 15 18:38:46 2010 New Revision: 1023064 URL: http://svn.apache.org/viewvc?rev=1023064&view=rev Log: Trademark guidelines: "All project or product homepages must feature a prominent trademark attribution of all applicable ASF marks" Modified: tomcat/site/trunk/docs/index.html tomcat/site/trunk/xdocs/index.xml Modified: tomcat/site/trunk/docs/index.html URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/index.html?rev=1023064&r1=1023063&r2=1023064&view=diff == --- tomcat/site/trunk/docs/index.html (original) +++ tomcat/site/trunk/docs/index.html Fri Oct 15 18:38:46 2010 @@ -214,6 +214,10 @@ involved, cli across a diverse range of industries and organizations. Some of these users and their stories are listed on the http://wiki.apache.org/tomcat/PoweredBy";>PoweredBy wiki page. + +Apache Tomcat, Tomcat, Apache, the Apache feather, and the Apache Tomcat +project logo are trademarks of the Apache Software Foundation. + Modified: tomcat/site/trunk/xdocs/index.xml URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/index.xml?rev=1023064&r1=1023063&r2=1023064&view=diff == --- tomcat/site/trunk/xdocs/index.xml (original) +++ tomcat/site/trunk/xdocs/index.xml Fri Oct 15 18:38:46 2010 @@ -27,6 +27,10 @@ involved, cli across a diverse range of industries and organizations. Some of these users and their stories are listed on the http://wiki.apache.org/tomcat/PoweredBy";>PoweredBy wiki page. + +Apache Tomcat, Tomcat, Apache, the Apache feather, and the Apache Tomcat +project logo are trademarks of the Apache Software Foundation. + - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1023067 - in /tomcat/site/trunk: docs/doap_Tomcat.rdf xdocs/doap_Tomcat.rdf
Author: markt Date: Fri Oct 15 18:45:53 2010 New Revision: 1023067 URL: http://svn.apache.org/viewvc?rev=1023067&view=rev Log: Trademark guidelines: Update doap Modified: tomcat/site/trunk/docs/doap_Tomcat.rdf tomcat/site/trunk/xdocs/doap_Tomcat.rdf Modified: tomcat/site/trunk/docs/doap_Tomcat.rdf URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/doap_Tomcat.rdf?rev=1023067&r1=1023066&r2=1023067&view=diff == --- tomcat/site/trunk/docs/doap_Tomcat.rdf (original) +++ tomcat/site/trunk/docs/doap_Tomcat.rdf Fri Oct 15 18:45:53 2010 @@ -12,11 +12,19 @@ http://tomcat.apache.org"; /> http://tomcat.apache.org"; /> A Java Servlet and Java Servet Pages specifications implementation. -Apache Tomcat is the servlet container that is used in the official Reference Implementation for the Java Servlet and JavaServer Pages technologies. The Java Servlet and JavaServer Pages specifications are developed by Sun under the Java Community Process. - -Apache Tomcat is developed in an open and participatory environment and released under the Apache License version 2. Apache Tomcat is intended to be a collaboration of the best-of-breed developers from around the world. We invite you to participate in this open development project. To learn more about getting involved, click here. - -Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations. Some of these users and their stories are listed on the PoweredBy wiki page. +Apache Tomcat is an open source software implementation of the +Java Servlet and JavaServer Pages technologies. The Java Servlet and +JavaServer Pages specifications are developed under the Java Community +Process. Apache Tomcat is developed in an open and participatory environment +and released under the Apache License version 2. + +Apache Tomcat is intended to be a collaboration of the best-of-breed +developers from around the world. We invite you to participate in this open +development project. + +Apache Tomcat powers numerous large-scale, mission-critical web applications +across a diverse range of industries and organizations. Some of these users +and their stories are listed on the PoweredBy wiki page. http://issues.apache.org/bugzilla"; /> http://tomcat.apache.org/lists.html"; /> http://tomcat.apache.org"; /> @@ -31,15 +39,15 @@ Apache Tomcat powers numerous large-scal Latest Stable 6.0.x Release -2010-03-12 -6.0.26 +2010-07-22 +6.0.29 Latest Stable 5.5.x release -2010-04-20 -5.5.29 +2010-09-16 +5.5.31 @@ -52,16 +60,16 @@ Apache Tomcat powers numerous large-scal Java Servlets JCP -JSR 154 -http://www.jcp.org/en/jsr/detail?id=154"/> +JSR 315 +http://www.jcp.org/en/jsr/detail?id=315"/> Java Server Pages JCP -JSR 152 -http://www.jcp.org/en/jsr/detail?id=152"/> +JSR 245 +http://www.jcp.org/en/jsr/detail?id=245"/> Modified: tomcat/site/trunk/xdocs/doap_Tomcat.rdf URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/doap_Tomcat.rdf?rev=1023067&r1=1023066&r2=1023067&view=diff == --- tomcat/site/trunk/xdocs/doap_Tomcat.rdf (original) +++ tomcat/site/trunk/xdocs/doap_Tomcat.rdf Fri Oct 15 18:45:53 2010 @@ -12,11 +12,19 @@ http://tomcat.apache.org"; /> http://tomcat.apache.org"; /> A Java Servlet and Java Servet Pages specifications implementation. -Apache Tomcat is the servlet container that is used in the official Reference Implementation for the Java Servlet and JavaServer Pages technologies. The Java Servlet and JavaServer Pages specifications are developed by Sun under the Java Community Process. - -Apache Tomcat is developed in an open and participatory environment and released under the Apache License version 2. Apache Tomcat is intended to be a collaboration of the best-of-breed developers from around the world. We invite you to participate in this open development project. To learn more about getting involved, click here. - -Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations. Some of these users and their stories are listed on the PoweredBy wiki page. +Apache Tomcat is an open source software implementation of the +Java Servlet and JavaServer Pages technologies. The Java Servlet and +JavaServer Pages specifications are developed under the Java Community +Process. Apache Tomcat is developed in an open and participatory environment +and released und
Re: Tomcat diagnostics
Pid, A late comment on this thread. On 9/25/2010 10:10 AM, Pid wrote: > A user asked if it was possible for Tomcat to > detect duplicate classes in the classpath and report which jar they were in. I suppose Tomcat could be instructed to do this, but it would have to step outside of the ClassLoader scheme and do everything manually: 1. Enumerate all the JAR files that would be in the ClassLoader's classpath 2. Open each JAR file (probably using java.util.Zip) 3. Scan each file and take a fingerprint (file length + SHA1 hash?, or is it enough to just have the same FQCN?) 4. Compare all fingerprints You can't use a ClassLoader directly because it will find the first matching Class and ignore the rest. It also won't provide anything that you can fingerprint (except maybe a list of methods/fields/etc.). -chris signature.asc Description: OpenPGP digital signature
Re: More Flexible DataSourceRealm
Mark, On 9/30/2010 5:59 PM, Mark Thomas wrote: > On 30/09/2010 22:50, ◙ Ludovic BERT ◙ wrote: >> Dear, >> >> I have developed a more flexible DataSourceRealm than the one provided in >> standard with Tomcat. This new DataSourceRealm is strictly the same than the >> one which is provided in standard, the difference is only in the way to >> configure it. >> >> This new realm does not expect several parameters for tables and for columns >> to generate the 2 prepared statements but expect the prepared statements in >> its configuration, so it gives more flexibility because, it can be plugged >> on any kind of DB schema which was not possible with the previous realm. > > What features does this provide that can't be implemented by adding a > couple of views to the database? This could help for dbs without VIEW capabilities (older versions of MySQL, etc.). -chris signature.asc Description: OpenPGP digital signature
Re: svn commit: r1022606 - in /tomcat/trunk/java: javax/el/BeanELResolver.java org/apache/el/lang/ExpressionBuilder.java org/apache/el/util/ConcurrentCache.java
2010/10/14 :
> Author: markt
> Date: Thu Oct 14 16:36:20 2010
> New Revision: 1022606
>
> URL: http://svn.apache.org/viewvc?rev=1022606&view=rev
> Log:
> Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=50078
> Thread safety in EL caches. Patch provided by Takayoshi Kimura
>
> Modified:
> tomcat/trunk/java/javax/el/BeanELResolver.java
> tomcat/trunk/java/org/apache/el/lang/ExpressionBuilder.java
> tomcat/trunk/java/org/apache/el/util/ConcurrentCache.java
>
> Modified: tomcat/trunk/java/javax/el/BeanELResolver.java
> URL:
> http://svn.apache.org/viewvc/tomcat/trunk/java/javax/el/BeanELResolver.java?rev=1022606&r1=1022605&r2=1022606&view=diff
>
(...)
> public V get(K key) {
> V value = this.eden.get(key);
> if (value == null) {
> - value = this.longterm.get(key);
> + synchronized (longterm) {
> + value = this.longterm.get(key);
> + }
> if (value != null) {
> this.eden.put(key, value);
> }
> @@ -344,7 +346,9 @@ public class BeanELResolver extends ELRe
>
> public void put(K key, V value) {
> if (this.eden.size() >= this.size) {
> - this.longterm.putAll(this.eden);
> + synchronized (longterm) {
> + this.longterm.putAll(this.eden);
> + }
> this.eden.clear();
> }
> this.eden.put(key, value);
>
I think that a ReadWriteLock will be more suitable here, because
there will be a thousand of reads for a single write.
> this.eden.clear();
Shouldn't the above line be inside the lock as well?
Best regards,
Konstantin Kolinko
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.4
I just played with a Roo application and I get a 404 with 7.0.4 whereas the very same application works OK with 6.0.29. I'll try to investigate this week-end. Sylvain On 15 oct. 2010, at 10:47, Mark Thomas wrote: > The proposed Apache Tomcat 7.0.4 release is now available for voting. > > It can be obtained from: > http://people.apache.org/~markt/dev/tomcat-7/v7.0.4/ > The svn tag is: > http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_4/ > > As with previous votes, I have included a stable option below although > my personal inclination is still to vote beta. > > The proposed 7.0.4 release is: > > [ ] Broken - do not release > [ ] Alpha - go ahead and release as 7.0.4 Alpha > [ ] Beta - go ahead and release as 7.0.4 Beta > [ ] Stable - go ahead and release as 7.0.4 Stable > > This vote will run until 10.00 UTC Wednesday 20th October (3 working days). > > Cheers, > > Mark > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Site redesign
Pid, On 10/4/2010 9:00 AM, Pid wrote: > For now: input into what people consider the most important things to > put in the green & blue boxes at the top part of the page would be > useful. E.g. > > 1. what are the most important things users should look for? * What is Tomcat (relegated to the bottom/right of the page) * Downloads (nicely placed, but could afford to move due to other issues * Help / Documentation* * Search (I see this isn't in your mock-up, but is on the main site) News is nice to have and gives readers a sense of activity, but I'm not sure it needs to have such a large section of the screen space devoted to it. > 2. what are the most important things users actually look for? Same list, IMO. > 3. what things does the community think should be prioritised. ASF promotes community itself, so I would have the word "community" somewhere on the page, probably under "Getting Involved". * Unfortunately, Tomcat has downloads and documentation for multiple products: TC 5.5, 6.0, 7.0, connectors, native, etc. That a lot of links. Consider presenting everything at once in a consistent format, but labeled according to version. Maybe something like the following: - Which Version? - Tomcat 7.0 - Download - Documentation Index - FAQ - Subversion Repo - Bug Database - Tomcat 6.0 - Download - Documentation Index - FAQ - Subversion Repo - Bug Database - Tomcat 5.5 - Download - Documentation Index - FAQ - Subversion Repo - Bug Database - Older versions - Download archive - Documentation archive Of course, lay it out in an attractive way instead of the HTML 0.9 style I have above :) This may be off-topic - I'm not sure how much site redesign you're considering, and I know that lots of version-specific may remain unchanged - but I'll give my two cents anyway. Something I find frustrating, as a tomcat-user contributor as well as a user of Tomcat, if the difficulty of finding a single source of information on a particular subject. There are many items in the "User Guide" (as in, the links to the left of the main content when browsing a particular TC version's documentation) that also have vital information in the "Configuration" section. For instance, "Connectors" has a short blurb about HTTP and AJP connectors, but has no links to the pages covering the connectors themselves. Sometimes information for certain things is "buried" under the Configuration section. Let's say I'm a naive user/reader and I want to know how to make Tomcat emit an Apache httpd-style access log. I find my version and start looking at the User Guide TOC. The only thing on that list that makes any sense in my context is "Logging", which of course covers application and code logging and not request logging. From there, you're essentially lost (unless you know how to use Google properly, which many people do not) and we get a question on the mailing list which could have easily been answered by the documentation. Where is the documentation on that? On the page covering configuration of Valves, of course. For some reason (probably because it was the only place at the time, way back when), the configuration reference for the component, which is pretty simple in and of itself, became the place to dump documentation about specific valves, regardless of their use. Logging (Access Log Valve), Security (Remote Address Filter, Remote Host Filter, Remote IP Valve, SSO Valve, Authenticator Valves), Debugging (Request Dumper Valve), and general hacks (WebDAV Fix Valve) are all documented on the same page. Some of these things aren't even valves. This is just one example. Again, it may be an issue of version-specific documentation (for which, of course, patches are always welcome), but I figured I'd mention something since Pid has been kind enough to volunteer to muck around with the site in the first place. Thanks, -chris signature.asc Description: OpenPGP digital signature
Re: svn commit: r1022606 - in /tomcat/trunk/java: javax/el/BeanELResolver.java org/apache/el/lang/ExpressionBuilder.java org/apache/el/util/ConcurrentCache.java
>> Modified:
>> tomcat/trunk/java/javax/el/BeanELResolver.java
>> tomcat/trunk/java/org/apache/el/lang/ExpressionBuilder.java
>> tomcat/trunk/java/org/apache/el/util/ConcurrentCache.java
>>
>> Modified: tomcat/trunk/java/javax/el/BeanELResolver.java
>> URL:
>> http://svn.apache.org/viewvc/tomcat/trunk/java/javax/el/BeanELResolver.java?rev=1022606&r1=1022605&r2=1022606&view=diff
>>
>
> (...)
>> public V get(K key) {
>> V value = this.eden.get(key);
>> if (value == null) {
>> - value = this.longterm.get(key);
>> + synchronized (longterm) {
>> + value = this.longterm.get(key);
>> + }
>> if (value != null) {
>> this.eden.put(key, value);
>> }
>> @@ -344,7 +346,9 @@ public class BeanELResolver extends ELRe
>>
>> public void put(K key, V value) {
>> if (this.eden.size() >= this.size) {
>> - this.longterm.putAll(this.eden);
>> + synchronized (longterm) {
>> + this.longterm.putAll(this.eden);
>> + }
>> this.eden.clear();
>> }
>> this.eden.put(key, value);
>>
>
> I think that a ReadWriteLock will be more suitable here, because
> there will be a thousand of reads for a single write.
This won't be straight forward since the data structure is being
modified in the get - you can't upgrade a ReentrantReadWriteLock from
a read lock to a write lock, so it doesn't handle this situation.
A ReentrantLock might do a better job than a synchronized block if
there's a real concern about the cost of syncs, but if not a rewrite
of the cache structure to use a more conventional LRU ordering on put
might be the best way.
>> this.eden.clear();
> Shouldn't the above line be inside the lock as well?
It doesn't really matter - there's a race on the overflow logic
anyway, so it'll still be called twice (and the underlying map is
concurrent).
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: svn commit: r1022606 - in /tomcat/trunk/java: javax/el/BeanELResolver.java org/apache/el/lang/ExpressionBuilder.java org/apache/el/util/ConcurrentCache.java
> This won't be straight forward since the data structure is being > modified in the get - you can't upgrade a ReentrantReadWriteLock from > a read lock to a write lock, so it doesn't handle this situation. Correction: the same lock is required to protect get and put operations on the WeakHashMap (same problem results though, since that lock would be necessity be the write lock). - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
