amyroh 2002/06/12 00:39:24
Modified:catalina/src/share/org/apache/catalina/mbeans
MBeanUtils.java NamingResourcesMBean.java
ServerLifecycleListener.java mbeans-descriptors.xml
Log:
Add JNDI resources support for Context.
[EMAIL PROTECTED] wrote:
On Tue, 11 Jun 2002, Remy Maucherat wrote:
I'll adopt a hard line stance, since I think it is the only way to avoid
the situation with dependencies to get out of hand (where we bundle
custom builds of every dependent module).
We have to use only release components
I was wondering if anyone in the Tomcat group has read this
document and what their opinion or official statement was.
http://radio.weblogs.com/0107789/stories/2002/05/28/isTomcatCrap.
html
We are in the process of deploying our application and trying to
determine the best servlet engine for
Hum, it seems apt has been discussed (planned/installed ?)
BTW, should we package a commons-logging-1.0.1cvs
or stay with commons-logging-1.0 ?
-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .)
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 12. lipanj 2002 0:09
To: [EMAIL PROTECTED]
Subject: cvs commit:
jakarta-tomcat-connectors/jk/native2/common jk_signal.c jk_user.c
costin 2002/06/11 15:09:11
Added: jk/native2/common
jfclere 2002/06/12 02:56:57
Modified:jk/native2/common jk_endpoint.c
Log:
Prevent core when createSlot fails.
Revision ChangesPath
1.19 +7 -1 jakarta-tomcat-connectors/jk/native2/common/jk_endpoint.c
Index: jk_endpoint.c
The core was the following:
+++
(gdb) where
#0 jk2_endpoint_init (env=0x8108b40, bean=0x8157de0)
at ../../common/jk_endpoint.c:89
#1 0x403b13ab in jk2_workerEnv_addEndpoint (env=0x8108b40, wEnv=0x80f2668,
ep=0x8157e58) at ../../common/jk_workerEnv.c:583
#2 0x403b26de in
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9772.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi,
I am having a problem trying to use a custom factory with JNDI. I get an
exception froom org.apache.naming.factory.ResourceFactory. I have added
debug and it appears that my factory parameter is not being picked up from
the server.xml.
Can somebody familiar with the naming code point me to
Hi all,
I have a small problem. I am trying out Session Replication in Tomcat
4.0.3.
But it does not work. In the site theserver.com there was a detailed
step by step installation procedure. I tried out that but it still
does not work.
They had mentioned 2 test programs to try out if it did
I was trying to get Axis running on Tomcat 4.0.3,
4.0.4b3 and 4.1.3b and had the same problem with all
of them. I finally got it to run but, had to spread
the Jars and class files around to do it.(Note, I was
able to get 4.0.4 beta3 Windows install to work but,
as I deploy on Linux, this isn't
When I push down scripts to a client by putting something like
Script LANGUAGE = 'JavaScript' SRC
='wwwroot/intranet/includes/menuBar.js'/Script in the document - all of
a sudden I can no longer store or retrieve values from the HTTPsession
object. I have to restart the server to get it back.
jfclere 2002/06/12 05:40:17
Modified:jk/native2/common jk_shm.c jk_workerEnv.c jk_worker_ajp13.c
Log:
Prevent the core when getSlot() failed.
Revision ChangesPath
1.27 +10 -8 jakarta-tomcat-connectors/jk/native2/common/jk_shm.c
Index: jk_shm.c
jfclere 2002/06/12 05:42:25
Modified:jk/native2/server/apache2 jk_logger_apache2.c
Log:
Allow to switch on the trace of env.
Revision ChangesPath
1.26 +2 -1
jakarta-tomcat-connectors/jk/native2/server/apache2/jk_logger_apache2.c
Index:
On June 11, 2002 10:19 pm, you wrote:
There are plenty of JSP1.1 pages out there, this will require people to
rewrite the pages just to add a 'kb' suffix ( which is pretty weird
by itself, almost everything else uses k, and is redundant - if
the size can only be specified in kb, there is no
Did there is still opened bugs in mod_jk 1.2.0 (jtc/native)
which could prevent us to make a release ?
Appart the AP 2.0 error when worker didn't exist.
=
Server error!
Error message:
handler jakarta-servlet not found for:
If you think this is a server error, please contact the webmaster
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3839.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
hgomez 2002/06/12 07:31:09
Modified:jk/native/apache-2.0 mod_jk.c
Log:
Fix the incorrect error reported when a worker is defined
but didn't exist (reported by Bojan)
Revision ChangesPath
1.45 +4 -1 jakarta-tomcat-connectors/jk/native/apache-2.0/mod_jk.c
This should fix the problem reported by Bojan.
What about tagging jtc for jk_1_2_0 release ?
-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .)
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
On Wed, 12 Jun 2002, Mladen Turk wrote:
Can you tell me what is the final goal of implementing the signals?
Well, my first 'itch' was the ability for a java program to send
a SIGHUP to apache. Beeing able to receive a SIGHUP seemed interesting
too :-)
I ask you that because I'm working on
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9650.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9650.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
De: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
Enviado el: 12 de junio de 2002 16:11
Did there is still opened bugs in mod_jk 1.2.0 (jtc/native)
which could prevent us to make a release ?
I was having problems with JNI worker, internal tomcat 3.3 test hang
tomcat AFAIK.
we need some time to
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9650.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I was having problems with JNI worker, internal tomcat 3.3
test hang tomcat AFAIK.
Urg, who could help in JNI/TC3.3 ?
we need some time to test jk 1.2 under IIS..
You're the boss here ;)
AFAIK there is some problems with file names, the given reg
file, docs and binaries has different names
mmanders2002/06/12 08:30:01
Modified:jk/native build.xml
Log:
Updated to match new libc directory structure for NetWare builds.
Revision ChangesPath
1.35 +1 -0 jakarta-tomcat-connectors/jk/native/build.xml
Index: build.xml
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7656.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
mmanders2002/06/12 08:51:48
Modified:jk/native/apache-1.3 mod_jk.c
Log:
Added check for NO_GETTIMEOFDAY since gettimeofday isn't supported on all platforms.
Revision ChangesPath
1.27 +5 -1 jakarta-tomcat-connectors/jk/native/apache-1.3/mod_jk.c
Index:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9772.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9715.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi!
I've tried to search FAQ's and newgroups and haven't
been able to find anything. Please forgive me if its
been answered.
With the Tomcat 3.3/IIS forwarding jsp responses, it
seems as though any url parameters are not being
forwarded and are returning NULL. ie.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5829.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7656.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I'd like to check in some (fairly minor) fixes to
jakarta-servletapi-4 and jakarta-watchdog-4.0, but I don't have
the karma. Is it a big deal to get added?
I wasn't sure if servletapi and watchdog were closely tied to
tomcat or their own whole thing with separate administration.
It looks like
On Wed, 12 Jun 2002, GOMEZ Henri wrote:
I was having problems with JNI worker, internal tomcat 3.3
test hang tomcat AFAIK.
Urg, who could help in JNI/TC3.3 ?
Can we just put it in the release notes, and focus on the
jni worker in jk2 ? ( i.e. people who use the JNI worker with
modjk1.1
I'd like to check in some (fairly minor) fixes to
jakarta-servletapi-4 and jakarta-watchdog-4.0, but I don't have
the karma. Is it a big deal to get added?
Will you apply some patches to jakarta-servletapi-4 code ?
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands,
jfclere 2002/06/12 09:47:05
Modified:.build.properties.sample build.xml
Log:
Arrange commons-logging... We have to use cvs until it gets released.
Revision ChangesPath
1.43 +3 -2 jakarta-tomcat-4.0/build.properties.sample
Index:
I was having problems with JNI worker, internal tomcat 3.3
test hang tomcat AFAIK.
Urg, who could help in JNI/TC3.3 ?
Can we just put it in the release notes, and focus on the
jni worker in jk2 ? ( i.e. people who use the JNI worker with
modjk1.1 should not upgrade ).
This affects only
GOMEZ Henri wrote:
I'd like to check in some (fairly minor) fixes to
jakarta-servletapi-4 and jakarta-watchdog-4.0, but I don't have
the karma. Is it a big deal to get added?
Will you apply some patches to jakarta-servletapi-4 code ?
Well, I wanted to apply a patch for a bug I
Well, I wanted to apply a patch for a bug I reported a while
back where GenericServlet.init() and destroy() send messages
(saying init and destroy) to log(). It's not a showstopper,
but it's very annoying. If someone else wants to remove the
two log() statments, that would be great.
Or do you
On Wed, 12 Jun 2002, Ian Darwin wrote:
For one thing I don't think a LOT of people actually specify the buffer size
(of course those who DO will jump in to prove me wrong, and those who
don't will remain silent :-)).
For another, memory is getting bigger quickly, and having sizes of things
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9164.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
[EMAIL PROTECTED] wrote:
jfclere 2002/06/12 09:47:05
Modified:.build.properties.sample build.xml
Log:
Arrange commons-logging... We have to use cvs until it gets released.
Thanks for fixing that :)
Remy
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For
On Wed, 12 Jun 2002, GOMEZ Henri wrote:
Has anyone 'volunteered' as release manager for jk1.2 ? If
someone does, he can decide on the 'mustfix' bugs for the release,
and if this is listed I'll fix it.
Hum, what's should do the release manager ?
Build the 'official' release, review the
GOMEZ Henri wrote:
No, I saw a problem here since servlet-api-4.0 is the OFFICIAL
servlet 2.3/jsp1.2 API and may not change without (wide) notice.
Yes, but there's a difference between changing the API (which
is the job of the servlet spec jsr team) and fixing bugs in the
implementation
Christopher,
You can send me the Watchdog patches and I'll look them over.
Thanks,
-rl
On Wed, 2002-06-12 at 12:01, Christopher K. St. John wrote:
GOMEZ Henri wrote:
No, I saw a problem here since servlet-api-4.0 is the OFFICIAL
servlet 2.3/jsp1.2 API and may not change without (wide)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9164.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Matt,
I recall there being a bug related to this in the
isapi_redirect.dll for Tomcat 3.3. For security, the dll
normalizes the URI before checking to see if it should be
forwarded to Tomcat. If the URI was shortened because
of this normalization, the query parameters would be lost.
This is
Hum, what's should do the release manager ?
Build the 'official' release, review the bugs and decide what
bugs must be
fixed, putting the release to a vote and making the announcements.
May be we could team-up with Larry ?
And of course, make sure the stars are in the right position and
all
hi,
= configure / make / make install is not possible.
i can't find any configure-script in the connector-source-file
jakarta-tomcat-connectors-4.0.2-01-src.tar.gz and so it's not possible
to compile and install any connectors from the source (without cvs)
thx for help
oliver scorp
--
To
GOMEZ Henri wrote:
I propose you to make a PROPOSAL for servletapi4 patch
to tomcat-dev list.
In the jakarta-servletapi-4 repository, the class:
javax.servlet.GenericServlet
has init() and destory() methods that call log(). While
not specifically prohibited in the 2.3 spec, it
Hi Henri,
I haven't been very active of late with Tomcat 3.3.x due
to being too busy with other things right now. I'm not sure
when I would find the time for JTC RM duties at this moment.
Cheers,
Larry
-Original Message-
From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
Sent:
Great, I'll try it! Thanks. I would really like to run
Tomcat 4.0.3 but i was having problems setting it up.
The console was reporting Java errors when I went to
hit the page. But this discussion is for the other
newsgroup ;-)
-Matt
--- Larry Isaacs [EMAIL PROTECTED] wrote:
Matt,
I recall
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7827.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Do we have two seperate TCs in the development process?
I see the v4.0.4-b3 release arouind 10th and 11th of May as
well as v4.1.3-b release around 28th and 29th of May.
What's going on?
Pae
[1] http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.4-b3/
[2]
On Wed, 12 Jun 2002, Pae Choi wrote:
Date: Wed, 12 Jun 2002 12:56:20 -0700
From: Pae Choi [EMAIL PROTECTED]
Reply-To: Tomcat Developers List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Cc: Tomcat Developers List [EMAIL PROTECTED]
Subject: Two TCs???
Do we have two
Craig,
Thank you for your reply as well as clarifying my previous inquiry.
Best,
Pae
- Original Message -
From: Craig R. McClanahan [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Cc: Tomcat Users List [EMAIL PROTECTED]
Sent: Wednesday, June 12, 2002 10:33 AM
Subject:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9813.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Christopher K. St. John wrote:
In the jakarta-servletapi-4 repository, the class:
javax.servlet.GenericServlet
has init() and destory() methods that call log(). While
not specifically prohibited in the 2.3 spec, it results
in unncessary output into logs. Also, it's annoying.
My
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Enviado el: 12 de junio de 2002 18:46
Can we just put it in the release notes, and focus on the
jni worker in jk2 ? ( i.e. people who use the JNI worker with
modjk1.1 should not upgrade ).
OK, i was only pointing to some problem i know
There is another question here. When log() is called no default log
level is assigned to it so there is no way to prevent log() messages
from cluttering the log files. What about a change to allow the setting
of the log level for the log() method in server.xml or web.xml (or even
giving it a
On Wed, 12 Jun 2002, Ignacio J. Ortega wrote:
Has anyone 'volunteered' as release manager for jk1.2 ? If
someone does, he can decide on the 'mustfix' bugs for the release,
and if this is listed I'll fix it.
The silence can be masked :)
Could we do some kind of collective RM for that
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9816.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
kinman 2002/06/12 13:19:32
Modified:jasper2/src/share/org/apache/jasper/compiler Generator.java
Log:
- The generated method should return a boolean, to indicate that the
rest of the page be skipped.
Revision ChangesPath
1.26 +21 -9
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Enviado el: 12 de junio de 2002 22:01
No, we need a benevolent worker :-)
Just realized i was falling in my habitual naiveness.. :)
The tasklist of the RM starts with collect open bugs, ok?
We have the bugs reported by the query below in
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9816.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6068.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
PROPOSAL: When Session Max reached, throw out oldest session
Currently tomcat ships with the maximum number of sessions set to
unlimited. They can expire by default after 30 minutes, however if
too many sessions are created within the 30 minutes, you can run out
of memory.
To prevent running
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9816.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
remm2002/06/12 14:29:49
Modified:.build.properties.sample
Log:
- Update to MX4J 1.1.
Revision ChangesPath
1.44 +5 -5 jakarta-tomcat-4.0/build.properties.sample
Index: build.properties.sample
kinman 2002/06/12 15:08:29
Modified:jasper2/src/share/org/apache/jasper/compiler Generator.java
Log:
- If the page attribute for jsp:include or jsp:forward contains a '?',
then the separator after the page should be '' instead of '?'.
Revision ChangesPath
1.27
As discussed with Kin-Man, the following patch (for Jasper2)
addresses two issues related to scripting variables exposed by
custom tags (via TagExtraInfo class or TLD):
ISSUE 1:
+++
According to the JSP spec, scripting variables with scope AT_BEGIN
or AT_END are supposed to be visible from
Thanks. I'll download an retest.
Bojan
On Thu, 2002-06-13 at 00:33, GOMEZ Henri wrote:
This should fix the problem reported by Bojan.
What about tagging jtc for jk_1_2_0 release ?
-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .)
PGP
remm2002/06/12 16:04:57
Modified:.build.properties.sample
Log:
- Add PureTLS.
Revision ChangesPath
1.45 +7 -1 jakarta-tomcat-4.0/build.properties.sample
Index: build.properties.sample
remm2002/06/12 16:05:24
Modified:catalina build.xml
Log:
- Add PureTLS.
Revision ChangesPath
1.122 +2 -0 jakarta-tomcat-4.0/catalina/build.xml
Index: build.xml
===
RCS file:
costin 2002/06/12 16:15:27
Modified:jasper2 build.xml
Log:
Build the jars during build, copy in deploy.
Revision ChangesPath
1.7 +31 -23jakarta-tomcat-jasper/jasper2/build.xml
Index: build.xml
costin 2002/06/12 16:17:36
Modified:jasper2/src/share/org/apache/jasper/compiler Generator.java
Log:
pageContext.getRequest() returns a ServletRequest, not HttpServletRequest.
Revision ChangesPath
1.28 +4 -4
costin 2002/06/12 16:18:50
Modified:jasper2/src/share/org/apache/jasper
EmbededServletOptions.java
Log:
Turn class debug info, they are quite usefull in debugging and don't
hurt anyone.
Revision ChangesPath
1.6 +4 -4
costin 2002/06/12 16:20:15
Modified:jasper2/src/share/org/apache/jasper JspC.java
Log:
A bit more verbose error message, from some reasons the stack trace
never shows up and is hard to guess what's going on.
BTW, it seems the classes are compiled automatically - that's a
nacho 2002/06/12 16:26:36
Modified:jk/native2/server/isapi isapi.dsp
jk/native2/server/apache2 mod_jk2.dsp
jk/native2/jni jkjni.dsp
Log:
* Added jk_user and jk_signal to the win32 build
Revision ChangesPath
1.16 +20 -12
Glenn Nielsen wrote:
I installed this and took a look at it. Looking much better. :-)
Here are some more suggestions for improvement.
1. Change the title to Tomcat Web Application Manager.
done
2. Move the Message: table to just below the page title.
done
3. Only enable the
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9677.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9722.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9700.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
remm2002/06/12 17:06:37
Modified:.RELEASE-NOTES-4.1.txt
Log:
- Update release notes.
Revision ChangesPath
1.9 +34 -1 jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt
Index: RELEASE-NOTES-4.1.txt
remm2002/06/12 17:10:14
Removed: .RELEASE-NOTES-4.0-B1.txt RELEASE-NOTES-4.0-B2.txt
RELEASE-NOTES-4.0-B3.txt RELEASE-NOTES-4.0-B4.txt
RELEASE-NOTES-4.0-B5.txt RELEASE-NOTES-4.0-B6.txt
Now that we can SEE all the contexts' display-names (thanks to Malcolm's
much-improved HTMLServlet), these two webapps should have display-name
elements (so should the examples, but this is a start).
--- webapps/admin/WEB-INF/web.xml.orig Tue May 7 12:33:44 2002
+++
remm2002/06/12 17:21:36
Modified:.build.xml tomcat.nsi
Log:
- The installer will now display the full version number of Tomcat, as defined in
the build.properties.
Revision ChangesPath
1.73 +3 -1 jakarta-tomcat-4.0/build.xml
Index:
remm2002/06/12 17:22:21
Modified:catalina build.xml
Log:
- Add Ant on the classpath (removes lots of errors when generating the
Javadocs).
Revision ChangesPath
1.123 +3 -0 jakarta-tomcat-4.0/catalina/build.xml
Index: build.xml
[EMAIL PROTECTED] wrote:
PROPOSAL: When Session Max reached, throw out oldest session
Currently tomcat ships with the maximum number of sessions set to
unlimited. They can expire by default after 30 minutes, however if
too many sessions are created within the 30 minutes, you can run out
On June 12, 2002 07:45 am, Arshad Mahmood wrote:
I am having a problem trying to use a custom factory with JNDI. I get an
exception froom org.apache.naming.factory.ResourceFactory. I have added
debug and it appears that my factory parameter is not being picked up
from the server.xml.
Can
There are few bugs in jspc, mostly related with the generation of the
class name and the mangling.
It seems CommandLineCtx and JspEngineContext are almost completely
duplicated.
I did a small change and turned JspCompilationContext into an
abstract class, with all the code from
Isn't the Java Groups JAR available as a separate JAR at www.javagroups.org
Put the JAR in your tomcat/common/lib and try it out.
Anand
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 12, 2002 5:31 PM
To: [EMAIL PROTECTED]
Subject: Small help
hi
I installed the linux-jdk1.3 and linux-ibm-jdk1.3.1
using ports in the FreeBSD. When i tried to run
tomcat4+with mentioned JVM machine gets hang...Below
is some of the parameter which i tried ..
Os Jdk TomcatRun/Or Not
FreeBSD Sun1.2 4xYes
FreeBSD
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6457.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
95 matches
Mail list logo
