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
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
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
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
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
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
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
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]
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,
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.
The reason - it's a huge security hole to not check them ( IMHO ) - a site
running multiple webapps ( with different security constraints ) may be
compromised if the constraints of the original requests are propagated on
forward. ( you can get a request dispatcher for a different webapp -
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
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,
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
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
(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.
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
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
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
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
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
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 Jason,
First, it's really great to see the discussions about performance !
Your tests are extremely usefull
I use ab and apache very often ( I used it as the main tool to tune tomcat
3.2 and now 3.3 ). One thing that strikes me is the fact that I have a
slower computer ( Celeron / 363 ) my
Hi Jason,
It's nice, isn't it? I was going to write something like it, but since it was
already there, I just used it. Like I said, it's got a few bugs, but it mostly
gives useful information, and works pretty well.
Open source :-)
I may know why this is. Before running my benchmarks, I
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
To fix these major issues will require modifying the protocol. I have
some ideas on how to do so, but I want to get some feedback on the best
way to go about making these changes. I could just modify the protocol
itself, and change the mod_jk code and Ajp13 code in the tomcat-3.3
branch.
The problem in your case is that the ParserFactory will be loaded by the
tomcat's classloader, and that classloader doesn't know about the child
class loader.
What you can do is:
Class c=Class.forName( parserClass );
sXMLParser=c.newInstance();
That will load the parserClass using the servlet
Yeah, MimeHeaders could use some work (it's got a disturbingly high
rate of 'XXX' comments).
A first step toward that is in util.collections and util.http:
I Split the MimeHeaders in:
1. the general-purpose org.apache.tomcat.util.collections.MultiMap:
- a specialized map that has
Thanks, Jim. I'll fix it asap.
It is a clear bug, but I am not sure about "pool will never contain any
value". For most of the stuff that I introduced in 3.2 for performance
tunning I did pre/post benchmarks ( it's amazing how many things that look
"cool" have just minimal effect ) - and the
Hi Larry,
I'm +1 on implementing your changes - setting options for jsp is very
important ( I use jikes most of the time ).
Setting jasper options in web.xml has many problems, and I don't think we
should do it.
I agree adding a ContextManager/Context property is the best solution for
3.2 -
Hi Larry,
Suggestion 1) In Handler and ServletWrapper some calls are made to
contextM.handleStatus() and contextM.handleError(). I think it would
be an improvement to add handlerStatus() and handleError() to
Handler, which would make the call to contextM.handleXXX. This would
allow,
Hi Hans,
for servlet tags and NCSA SSI directives, I decided to port Apache
JSSI to Tomcat. Now it's basically done for TC 3.2, and the question is
what to do with it ;-)
1) Make this a new Jakarta subproject, named jakarta-jssi.
The reason for this is that it's an optional module and
Even though the "org.apache.java.*" classes are not directly tied to
JSSI, I have a feeling they are not all that useful for other projects.
And without a real "shared Java utils" package within Apache, it's a
pain to coordinate the development of shared code. I therefore suggest
this
Okay, I appreciate if you can take a look at it. I must admit I have not
looked at the interceptor stuff enough to see how it should be done. To
me, "interceptor" sounds like something that intercepts a specific request
and does something with it, not a component that can provide an interface
Given that the default web.xml is not being read, how do you enable Jikes as
the JspCompiler? That setting used to be in web.xml. What's the syntax to
specify it in server.xml, or did we lose this functionality for Tomcat 3.2?
(If so, could it be put back, or define a syntax in server.xml
Given that the default web.xml is not being read, how do you enable Jikes as
the JspCompiler? That setting used to be in web.xml. What's the syntax to
specify it in server.xml, or did we lose this functionality for Tomcat 3.2?
(If so, could it be put back, or define a syntax in
I'll very happy to see that the works done on my jakarta/xml RPM used more
heavily
on Apache projects (at least on Linux/Unix boxes).
So I propose that the sources and binaries RPMs I've done for
jakarta.apache.org and
xml.apache.org projects and which live now at ftp://ftp.falsehope.com
While jakarta-servletapi-4.0 and TC4.0 builds are being
re-developed, could we please *stop* them creating
directories higher in the hierarchy thantheir own root?
ie
/jakarta-tomcat/ shouldn't then create ../build/ - it's
not nice!
An alternate perspective - I like the fact that
On Fri, 15 Dec 2000, David Brown wrote:
Hi David,
String usage is a big performance problem in tomcat - we are just
beginning to resolve this problem in the servlet container ( starting with
3.3, where the core will be able to work without allocating strings ),
but we will continue even after
I think Larry is also working on something - he sent a proposal few days
ago about how to enable debugging ( and pass options to jasper ). It'll
probably be part of a 3.2.x bug-fix release, as it requires some changes
in the existing code.
Since there were no +1's for 3.2.x, I'm
Some of you probably know that the httpd group is getting ready to release
Apache 2.0. We are all set to release our first beta on Friday. As a
part of this, we are looking into getting Apache.org running 2.0. So, the
next question we have to deal with is how does Tomcat run on 2.0?
I
On the other hand, it should be noted that mod_jk has substantial deficiencies.
Like mod_jserv before it, this connector is substantially limited -- it requires
users to double-configure many of the key attributes of a web application
(security, mapping URIs to particular handlers,
should be very amenable to the Apache 2.0 infrastructure. I would not
personally spend any time trying to make mod_jk or mod_jserv work in a 2.0
environment, when the future is clearly in a different direction.
Since I believe in a different future and direction, I'll spend the
time to
Ok, too much mail on this thread, I'll try to summarize my answers:
- The only reason for me to stay on this project is that I want to finish
something that I started. In my view, tomcat 3.3 ( or what will be in the
main branch of cvs in about a month or 2 ) will be the "right" thing
based on
+1
Costin
On Tue, 19 Dec 2000, Craig R. McClanahan wrote:
Marc Saegesser wrote:
Craig,
I'm willing to volunteer my time and effort to help out with maintenance of
3.x. We are embedding Tomcat 3.2.x into our product so I have a vested
interest in making sure that the 3.2.x product
Hi,
Both Petr and Vasile are commiters - since december, last year :-)
Petr did a lot of pathces to JSP, Vasile ported mod_jk to AOLServer.
It seems some mailers have a late Y2K problem on sorting the mail, and we
are now responding to 1999 posts.
To be honest, it would be very interesting to
Ok, I just got off the phone with Pier (who just broke both of his thumbs
skiing this weekend ouch) and he has clarified a bit of what Costin
expressed to him about what he really wants to do, so let me repeat it to
see if I got it right now:
Thanks, Pier :-)
Costin wants to
Hi,
Way back to technic ;-)
Great too see that.
When linking apache to tomcats in an untrusted networks, ajp12/ajp13
streams are in clear.
What about crypt stream between apache and tomcat ? Something like
DES with a known key between the two or something like a ticket ?
Actually
Hi,
I would like to thank again Jon for his good intentions, and apologize if
I offended him or anyone else - it's very easy to do so in email.
Jon: I believe you had the best intentions, but you have to admit you may
be worse than I am at diplomacy :-) ( and I'm very bad at that )
Going back
Okay, after a full day's work, I have a working JAASRealm that lets you
use a JAAS LoginModule (or many LoginModules) for authenticating Web
clients. My company's KerberosLoginModule now happily authenticates a user
against our Kerberos 5 KDC from inside Catalina. Jazzy.
Great !
This is
Hi again, Jon.
I downloaded the latest J2EE and it includes Tomcat. However, when I looked
on your website, it says that you have two versions of Tomcat. Which one
comes with J2EE? Which one should I be using?
I'm sure J2EE will have a README telling you what version it includes.
As for
I've got the _a9 sources, and I was able to compile - but apache crashed.
There are known issues with _a9. I would suggest ignoring it completely.
Ok, good to know. I'll stay with the CVS then.
Now I'm trying to get apache2.0 using anonymous CVS, and I get:
ap_buckets_file.c
Ops, sorry about that.
Now it compiles - but crashes with SIGSEGV in reinit_scoreboard.
I'll try with dexter, it seems it may work without a scoreboard , and I'll
also try again to compile a file-based scoreboad.
Damn, Linux was supposed to be a bit better... What's very strange is that
all
Another update - I got mod_jk up and running, it can serve a simple
servlet or a jsp page.
There are few bugs for some pages, I'll work on it tommorow.
Costin
Ops, sorry about that.
Now it compiles - but crashes with SIGSEGV in reinit_scoreboard.
I'll try with dexter, it seems it
On Wed, 20 Dec 2000, Nick Bauman wrote:
Okay, thanks for the clarification. Not sure I understand why it wasn't
just merged into SimpleMapper, but maybe in the rush to release things get
dog-eared sometimes.
It was intentional.
SimpleMapper1 is not just a patch to SimpleMapper, is a whole
Not true at all. 3.x only implements Servlet API 2.2 and 4.0 implements
Servlet API latest and greatest.
On top of it, I (and others) would be STRONGLY -1 for adding Servlet API 2.3
support to 3.x within the Jakarta project. That is why Costin has already
agreed and stated that he will
The future of Tomcat 3.3 seems to be outside Apache now.
It's really sad.
Sorry, but that's not what I said Henry. Last month I even came up with
a proposal that got accepted (but never turned to reality) on how to
handle this situation... But it seems to me, that everyone here is
Well, I am not that good at getting all this flames ( and to be honest I'm
not used to get the "thanks" that I got lately - mostly in private mail -
it looks like a very different world, and an wonderful Christmas gift for
me )
In any case, I'll try to stay away from further arguments - I know
My plan:
TOMCAT 3.2:
Start using it :-)
TOMCAT 3.3:
As I said:
- merge all changes/bug-fixes from 3.2 ( that are not merged by their
authors )
- finish the core refactoring, try to get as much feedback as possible
( estimate - 1 month )
- build milestones, build beta, build release-proposal,
Hi Shai,
Thanks for your patch, it's a very good start and I think it'll be useful
for many users.
I think it needs some more work - I'm not talking about the main
functionality you are implementing, which I'm sure will be tested and
improved and will have a nice evolution.
I'm talking as a
I wrote _a_lot__ of the code that went into 3.2, and I did more work
than you can imagine, Jon. I did that even if I had a job that is not
tomcat, but xml-xalan.
In fact, you did some of that work during your day time job. :-)
And thanks to my managers for not firing me, I'm lucky to
Hi Nacho,
Sorry about this - I'll fix it back if it broke something. I was not sure
about the way Digest worked, and I wanted to find a way to use it in all
realms.
-public int authorize( Request req, Response response,
String roles[] )
-if(
To be honest, I don't know too much about Digest authentication - you
spent more time on this issue anyway.
You are confused with this code, this enables the ability of use
Digested passwords in the JDBCRealm nothing to do with DIGEST auth, it's
only to read digested passwords from
Jon Stevens wrote:
Why does this scare me into thinking that if people
start to base their code on top of this that they
will be tying themselves to a single servlet engine?
Isn't that something that we were trying to avoid?
Correct me if I'm wrong.
I see it as a good
I'll check in the fix tommorow - the HttpSessionBindingEvent and
session reloading should go into the facade22 module.
I was thinking about this - does it make sense to keep the session code in
the core ? It seems to me that maintaining an object store is orthogonal
to the http functionality -
Hi Dan,
In the course of some work I've been doing on Tomcat, I've been
thinking about using a Thread Pool. There is currently a bunch of code
doing this in both TC 3 and TC 4, but, no surprise, it's extremely
difficult to understand and/or extend.
Well, it is a big surprise - I thought TC
On Sat, 30 Dec 2000 [EMAIL PROTECTED] wrote:
Thanks. I'll love to see this.
I'm rewriting the session serialize code as a plug-in module (that was your
offer), so I need sterilization support for ServerSession.
Please take care of that as fast as you can.
I'm working on it - sorry for
so +1 , but i continue to not see any advantages in maintain another
repository..
Like Nacho I turn my -1 to +1 since I don't want the TC 4.x development
to be stopped or features freezed but I feel that It will became
hard to find our way in 3.2, 3.3, 4.0 and 4.1
I don't see any
Hi Simon,
One idea:
I know nothing about the AJP12 protocol but isn't it possible
to generate some random seed (or whatever) while starting
up tomcat, saving it to disk and then when the shutdown request
Done. ( part of 3.3 ). I can back-port it into Tomcat3.2, but it's more
than a bug fix
I need to get a count of the number of active sessions in an instance of
Tomcat.
Was hoping it could be a flag (Tomcat -getSessionCount) or the like, so I've
been looking at adding a getSessionCount() method from the StandardManager,
through to Tomcat... But I need to get the
One idea:
I know nothing about the AJP12 protocol but isn't it possible
to generate some random seed (or whatever) while starting
up tomcat, saving it to disk and then when the shutdown request
Done. ( part of 3.3 ). I can back-port it into Tomcat3.2, but it's more
than a bug fix (
Hi,
Solution: Dan Milstein is adding my patch to mod_jk. It forces an instance
of Tomcat in the load balance list to reject new connections, but continue
to service existing sessions. (by setting worker.name.active=0, and
restarting my apaches)
Question: can this be done _without_
I agree that a jk_admin type application to control the load balancer and
get session info would be great and very usefull, but that would have to
access information from the web server (who's in the list, who's active) and
each TC (how many sessions). So even if I built an Apache admin app,
1. Extensible/Modular. Maybe you want to get other internal
informations,
or change other parameters at run time.
2. Minimal ( or no ) changes in the core or protocols. Changes are bad
bacause they add bugs, require releases , etc, and if we do (1) right,
then no other change is
1 - 100 of 654 matches
Mail list logo
