mturk 2002/07/14 06:30:04
Modified:jk/java/org/apache/jk/apr AprImpl.java
Log:
Added Apache Software License prolog
Revision ChangesPath
1.25 +60 -1 jakarta-tomcat-connectors/jk/java/org/apache/jk/apr/AprImpl.java
Index: AprImpl.java
mturk 2002/07/14 06:32:13
Modified:jk/java/org/apache/jk/apr TomcatStarter.java
Log:
Added Apache Software License prolog.
Check if TomcatStarter was called with the stop param.
If called that way sleep for 5 seconds to allow the server shutdown,
and then call the clear the
mturk 2002/07/14 06:33:56
Modified:jk/native2/common jk_worker_jni.c
Log:
Remove the destroying of the jvm from native code,
the TomcatStarter will do that on Java side.
Revision ChangesPath
1.27 +1 -2
mturk 2002/07/14 06:36:03
Modified:jk/native2/common jk_channel_jni.c
Log:
Remove the jvm detaching from channel ajp to the service.
Revision ChangesPath
1.33 +7 -3 jakarta-tomcat-connectors/jk/native2/common/jk_channel_jni.c
Index: jk_channel_jni.c
mturk 2002/07/14 06:37:28
Modified:jk/native2/server/apache2 jk_service_apache2.c
Log:
Move the jvm detaching to the service afterRequest.
That way we are sure that the detaching is in the same thread.
Revision ChangesPath
1.28 +8 -1
mturk 2002/07/14 06:39:13
Modified:jk/native2/server/isapi jk_isapi_plugin.c
Log:
Remove the hack for unloading the jvm. Now its done on the Java side.
Check for threadPool config value to be at least 10 or higher.
Revision ChangesPath
1.39 +9 -8
mturk 2002/07/14 06:41:36
Modified:jk/native2/server/isapi jk_iis_thread_pool.c
Log:
Detach the jvm when the thread receives the shudown signal.
There is a substantial performance gain using this approach.
Revision ChangesPath
1.2 +10 -1
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2002-07-14/jakarta-tomcat-4.0.html
Buildfile: build.xml
deploy-prepare:
deploy-static:
deploy:
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=9749.
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=9749.
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=10789.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I recently started out trying to build Tomcat 4.1 from sources and found
that
the process was quite painful. While doing my homework, I found a few
bulid
problems and that BUILDING.txt, build.xml and build.properties.sample
could be
improved on a few points:
(Patches are sent separately. Sorry
This is the revised BUILDING.txt that I propose:
Building The Tomcat 4.1 Servlet/JSP Container
=
This subproject contains the source code Tomcat 4.1, a server that implements
the Servlet 2.3 and JSP 1.2 Specifications from Java Software. In order to
These are the patches to build.xml and build.properties.sample that I propose:
=
--- build.xml.orig Thu Jun 13 02:21:36 2002
+++ build.xml Mon Jul 15 00:22:28 2002
@@ -24,7 +24,7 @@
property name=jasper.build
Not acked.
-- Forwarded Message
From: Chanaka Samarajeewa [EMAIL PROTECTED]
Date: Fri, 12 Jul 2002 18:45:32 -0600
To: [EMAIL PROTECTED]
Subject: bad link
Hi, the source download links for tomcat 4.0.3, 4.beta are broken.
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=10796.
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=10796.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I ran into the same problem (NullPointerException on xml to html
transformation) The Java XML Pack (summer 02) contains Xalan 2.2 or 2.3
(don't remember) but that version of Xalan has a known transformation
bug. Download Xalan 2.4.D1 from http://xml.apache.org/xalan-j/index.html
and drop the
I remember seeing a bug sometime back on deployed
applications not persisting across Tomcat restarts.
Has this been fixed?
The deployed app is copied into CATALINA_HOME/work
which is not loaded up by Tomcat- so how does Tomcat
find the context again? Is server.xml modified?
I haven't been able
Finally go the deploy ant task to work- cleared up a
lot of my misunderstanding. I found two bugs (or are
they mistakes on my part??) though:
1. The only path accepted by the ant deploy task is a
URL type (see sample below)
target name=deploy description=Deploy web
application
20 matches
Mail list logo
