Hi Dan,
I think you'll be able to commit the patch yourself very soon.
I just have few comments - it's a good patch ( as it solves the problem),
but it's not good for performance.
We definitely need to do a refactoring of MimeHeaders :-)
The idea behind MimeHeaders is to allow efficient
I would be interested in hearing from folks here whether they percieve
a need for Debian packaging, or whether they prefer to "roll their
own"?
I'd love to see up-to-date Debian packaging, but I think it would be a
challenge to keep it quite as up-to-date as CVS. Perhaps a regular
Costin, could you please move your upload directory for these nightly builds to
someplace else? The problem is that you're confusing the people who wonder why
the nightly builds have nothing to do with the current (3.2) code release.
I can move them to tomcat-3.3 - I wanted to avoid
We had all our URL's (except our login form) stored in the web.xml file as
input parameters to out servlets, so I created a new context,altered the
URL's to include the context name, and started the tomcat server. It now
appears to be working fine under the new context.
If you used the
What are some methods people use to measure the performance of
Tomcat? I'm looking to do some tuning of the Ajp13 code, and I'd like
to build up an understanding of where the bottlenecks might be.
My recomendation is to start with simple tools - and "ab" is a perfect one
if you use it with
Hi Larry,
I'm in the process of porting the Tomcat 3.2 exception propagation
changes to Tomcat 3.3 that were made to Handler.java,
ServletWrapper.java, and RequestDispatcherImpl.java. I was trying
to review behavior as I do so to see what can be improved or cleaned
up.
The only important
...aka "Will the Real PoolTcpConnector.java please stand up?"
I've been reading through the Connector code in 3.3 (to try to understand the Java
side of the various protocols and to maybe contribute some work there). However, to
my great confusion, there seem to be two parallel versions of
Where can I get the tool to test my tomcat.
I know where to find Hello and helloW (Tomcat source ??), but I'm wondering
where I can get the tool you have used below to get this nice summary.
Wouldn't it be nicer if that tool was included with Tomcat distribution
(inc. hello/hellow)??
The
Thanks, I'll check it in. I was reviewing the 3.2 fixes in cookies,
I hope I'll get them all updated.
( including this one )
Costin
I was just flipping through this code because I did some changes to
CookieTools. To force a V0 cookie to be deleted properly, the time
should actually be set
Hi,
I spent many hours trying to fix a bug in tomcat3.3. I'm now down to
DependManager, and I really have no idea what's happening.
There is a method:
boolean shouldReload() {}
All return statements are:
"return expired;", where expired is an object property ( no local
variables - the class
This doesn't happen if I use IBM JDK1.3 - only with Blackdown 1.2.2 (
FCS,
BETA ).
VERY, VERY SCARRY !!!
Does disabling the JIT help any? ( -Djava.compiler= )
Doesn't help - I tried that.
Anyway - now we have a workaround, but we do print a warning when this
happens ( I still have
Hi Pier,
I know we discussed that, but I want to make sure everything is ok -
I would like to implement the java side of "warp" in tomcat3.3, and
reuse the C side from 4.0.
Would it be ok to make a symbolic link, so the native code is in sync ?
It's the simplest way to do that ( and I tested
For another approach at embedding Tomcat in an Enterprise server
check out Enhydra, which is Open Source, at http://www.enhydra.org/
particularly look at
modules/ServletContainer/src/org/enhydra/servlet/servletManager/ServletManager.java
which takes on many of the same roles as the
Hi!
Can anyone tell me if it's possible to run Tomcat together with NES 3.51, or
do I have to upgrade to NES 3.6 to get it work?
It should work - AFAIK mod_jk uses only generic nsapi calls.
You'll need to compile it yourself, there are only few peoples using
NES+tomcat.
If you succeed,
Hi,
As promised, no more checkins without nightly builds :-)
I created a simpler script, with fewer features - it seems to work
fine. Instead of one build, there are 3:
- tomcat 3.3 + extensions ( JSSE in CLASSPATH )
- tomcat 3.3 "basic" ( nothing in CLASSPATH except JAXP )
- tomcat 3.3 built
1) Using EmbededTomcat seems to require using a security manager. I
haven't tracked down why, yet, I just added a security policy that opens
everything up.
2) The contexts' context manager wasn't being set. I had to change the
order in which things got created and add a call to
(1) Build and release Tomcat 3.2 final on Wednesday 11/29/2000
+1
(2) Ongoing Support Plan for Tomcat 3.2
+1 ( until 3.3 is released and we'll switch to 3.3.1, etc)
In 3.3 the core will be finally finished in most aspects, and almost all
functionality will be part of replaceable modules.
Hola a Todos:
Asunto: cvs commit:
jakarta-tomcat/src/share/org/apache/tomcat/service/connector
Ajp13ConnectorRequest.java
How about definitely deprecate org.apache.tomcat.service packages??
The package has been refactored and moved to
org.apache.tomcat.modules.server.
The new
Hi Arieh,
I know about this problem, and 3.3 is going to fix this ( and other
similar problems ) by defining a startup order and changing the code
to implement it.
I don't know any simple fix for 3.2, there is a lot of code that has to be
changed.
Costin
On Mon, 20 Nov 2000, Arieh Markel
Hi,
As you know, 1-2 months ago, when Tomcat3.2 was frozen, I started to work
on all the long-delayed things that were too "dangerous" to implement in
tomcat3.2 time frame ( the list is at the end ).
Most of that has been implemented ( I sent quite a few mails in addition
to the normal CVS
I agree, +1 on option 2).
Regarding the proposed changes, I'm +0. I'd like to see 3.3 (or ideally it
should be called 3.2.x if you decide to start from scratch with the 3.2
base) as the continuation of 3.2, with focus on bug fixes and minor
improvements (e.g. performance, admin, etc.) in
Is there a separate mod_jk list?
I've posted a severe bug for ajp13, and I would like to contribute, but I
don't see a TODO for mod_jk or much discussion on plans for mod_jk and
related containers.
That's because right now ( AFAIK ) there is no imediate plan for mod_jk.
It works well
First of all thank you very much for you reply (to tell the truth, I started
to lose the light at the end of the tunnel).
Since we are entirely Java shop, I used pre-compiled mod_jk, and my platform
is Windows NT 4.0 (SP6) IPlanet4.1(SP3),
Yes, I tried to run Tomcat with the "ajp12" only,
As close as I can tell, SessionInterceptor needs to be called first to
parse the url sessionid out of the URL before it can be context mapped.
StandardSessionInterceptor lets you work with the sessions once you know
which context the request is going to. I've done some work in there,
but I
Hi Hans,
The patch is great, +1 from me. ( it's the way the code was supposed to
work - if you look back 2-3 revisions for that file you'll find very
similar code ). It seems the patch for "multiple session cookies" broke
this part - it's great that we fix it back.
For 3.3 we should probably
Is there a RFC on Ajp protocol? Or any documentation at all?
No, there are just incremental enhancements and changes to Ajp11 - and I
would say we might still have some changes and enhancements.
( there are additional messages that will probably be needed, the current
stuff is stable and if
6.8 Container Managed Security Constraints
Due to the way that Tomcat 3.2 is implemented, container managed security
constraints are imposed both on the original request URI *and* on subrequests
initiated to handle RequestDispatcher.forward() or RequestDispatcher.include()
calls.
Hi,
I couldn't locate the Ping Servlet, but did get one very close to it
called the UpperBound Servlet, which is attached. I haven't tried it.
Roy
In tomcat3(.3 - the main branch ) there are 2 servlets - Hello and HelloW,
both can be used for PingServlet.
( they display 100 bytes of data,
but it's worth mentioning that the main branch of
"jakarta-tomcat" (where you committed your change for build.xml) is the
"3.3" development tree.
If, on the other hand, you want to use the 3.2 branch that I'm preparing
for release, you will want to check out branch "tomcat_32" from
I guess I must have implemented it in our application ;).
It would be nice to contribute that into tomcat3.3 :-)
Costin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
No problemo. The GPL issue is being resolved (=we're switching license).
That's great ! There is a lot of code that should be reused/shared, and
it's really bad when the license prevents that.
additional permissions, like changing the class path, and also ACL
doesn't implement the
criteria on a limited set of requests. So, one more time: What workload
is Tomcat expected to run, and what will TC thruput and response be
running that workload on a particular architecture? Or, since TC is free,
this is up to the user to simply try it and see?
I don't think you can ( or
Hi,
After a lot of thinking, I decided to give up ( at least temporary ) my
plans for a tomcat revolution. It was very tempting, but I don't think
it's the right thing to do - evolution is still the best way to go :-)
It is important that tomcat3 has a design that allows support for future
Modified:src/doc Tag: tomcat_32 readme
Log:
Remove references to "Tomcat 3.3" and "Tomcat 3.4" since that code base is
now a "revolution", not the plan of record.
???
Supporting servlet2.3 is a revolution, but "performance enhancements" and
"security" and "I18N" are normal
Yes, We saw many reference of code to be fixed on 3.3. Now that some want to
kill 3.3 and directly play with 4.0, the risk of having a 3.x branch
(the current branch) falling in 'unsupported software land' is VERY HIGH.
This is open source - it's supported as long as some developers are
Sorry Pier, but I don't think I'm doing anything wrong.
I worked ( pretty hard ) on the last year or so on tomcat. I worked (
pretty hard ) convincing other people to contribute.
Tomcat 3.1 is better that tomcat 3.0 ( or the old JWSDK ). Tomcat 3.2 ( as
it was few months ago ) is better than
time explaining to people, "Well, 3.x is sort of this unfinished thing that
they weren't happy with, so they started 4.x". To me, that DOES give the
3.x and 4.x are 2 different servlet containers, with very different
design. The only confusing thing is the fact that the same name is used
for
That's a very interesting discussion, I certainly learned a lot from it.
So, tomcat3.3 is confusing and shouldn't be called tomcat because catalina
is tomcat. And while tomcat3.2 was ok, and nobody complained that the
performance increased several times and a lot of features were added, for
What about this:
- I start a new revolution in tomcat3.2 space ( proposals/something ),
and all the implementation of 2.3 and all controversial stuff will go
there ( i.e. all new features, like dav, http1.1, resource caching, the
new SMTP and POP3 protocols - since any feature will be in fact
- I start a new revolution in tomcat3.2 space ( proposals/something ),
and all the implementation of 2.3 and all controversial stuff will go
there ( i.e. all new features, like dav, http1.1, resource caching, the
new SMTP and POP3 protocols - since any feature will be in fact just an
How could we find more information (and even code) about mod_warp ?
I'll very happy to test it on Apache 1.3.14 .
BTW will it be used in TC 3.3 ?
I haven't seen the code, but if it is good code ( and knowing Pier, it'll
be) we'll use it in TC3.3 too - I like mod_jk, but having more choices
In order to test and integrate the new jasper ( from catalina ) we
need to move src/share/org/apache/jasper to src/jasper3/org/apache/jasper,
and import jakarta-tomcat-4.0/jasper into jakarta-tomcat.
I'll do that very soon - it'll generate a big diff file.
I'll also integrate the invocation
Costin,
I believe there would be (or at least SHOULD be! :) many more contributors
to these projects (Tomcat), but maybe some of us are intimidated by the
level of apparent expertise required for this stuff. (Then again, I know we
have some damn good people on these lists.) I am curious, is
The dependencies are with the resources package, to have some abstraction to
the data being served, instead of just hardcoding access to the filesystem.
It hasn't reduced performance in a noticeable way.
So I would suggest you port the resources related stuff, instead of
replacing the calls
the remaining 3.2 bugs (which you left behind on the 3.3 track) rather
than duplicating work that has already been done.
:-)
Costin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
The Tomcat community would certainly be better served if you cleaned up
the remaining 3.2 bugs (which you left behind on the 3.3 track) rather
than duplicating work that has already been done.
Craig
I agree.
Well, so do I - 3.3 will have fewer bugs than 3.2, I'm working on the
Hi,
I would like to propose a number of changes to the way tomcat is set up
and configured.
1. Support for virtual hosts. AutoSetup uses TOMCAT_HOME/webapps, but that
doesn't allow virtual hosts. The new mechanism should use something like
TOMCAT_HOME/hosts, with DEFAULT used for the default
Mark Porter wrote:
Why are the nightly builds broken (still!) and why is no-one answering
questions about builds/releases?!?
Probably because there is so little free time... It's a volunteer project
-
if you have a nightly build system that works and you have the time to
maintain it - I guess
601 - 648 of 648 matches
Mail list logo
