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=7826.
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=7827.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I'll build rpm for Apache 2.0.35 and see if I've
got the same problem
-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .)
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
-Original
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=7759.
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=7829.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi,
I have played a little with mod_jk2 and I have missed a feature: To get a path
relative to the server root.
For example in jk_workerEnv.c:
+++
if( configFile == NULL ) {
wEnv-config-setPropertyString( env, wEnv-config,
config.file,
On Mon, 2002-04-08 at 18:12, GOMEZ Henri wrote:
I'll build rpm for Apache 2.0.35 and see if I've
got the same problem
Thanks!
Bojan
PS. BTW, this was on RedHat, so it'll be the proper test.
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
Hi JF
It would be nice to have /usr/local/apache/conf/jk2.properties
when httpd is
configured to be in /usr/local/apache (instead of
/conf/jk2.properties in the
son processes...).
My first idea is to add makeRoot() in jk_ws_service_t. But I
have the problem
that apache needs a pool (not a
GOMEZ Henri wrote:
Hi JF
It would be nice to have /usr/local/apache/conf/jk2.properties
when httpd is
configured to be in /usr/local/apache (instead of
/conf/jk2.properties in the
son processes...).
My first idea is to add makeRoot() in jk_ws_service_t. But I
have the problem
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=7827.
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=7829.
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=7759.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Why not just use a char * which will be initialised by
mod_jk for AP1.3/2.0 and later for IIS/iPlanet ;)
Ok... But where should we stored it? Like a property server.root in
jk_workerEnv_t?
Yes
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
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=7831.
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=7831.
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=7831.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2002-04-08/jakarta-tomcat.html
Buildfile: build.xml
detect:
msg.jdk12:
[echo] Detected JDK1.2
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=7759.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi,
Sorry if this is a little off-topic
I'm presentently trying to modifiy the mod_webapp source so that concurrent warp
requests can be supported on NT. To do this, I'm implementing a pool of sockets per
warp connection and each time a warp request is made a socket is acquired from 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=7759.
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=7690.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
[EMAIL PROTECTED] wrote:
Hi,
Sorry if this is a little off-topic
That is not off-topic!
I'm presentently trying to modifiy the mod_webapp source so that concurrent
warp requests can be supported on NT. To do this, I'm implementing a pool
of sockets per warp connection and
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
My understanding (so far) is that an apr pool essentially makes memory cleanup
a bit easier by cleaning up all datastructures associated with it when it is
destroyed. This removes the need to cleanup all datastructures individually
and makes memory
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=7026.
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=7759.
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=7026.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
GOMEZ Henri wrote:
Why not just use a char * which will be initialised by
mod_jk for AP1.3/2.0 and later for IIS/iPlanet ;)
Ok... But where should we stored it? Like a property server.root in
jk_workerEnv_t?
Yes
Storing it in jk_config but how to get it back?
Will not it be more easy to
Ok... But where should we stored it? Like a property
server.root in
jk_workerEnv_t?
Yes
Storing it in jk_config but how to get it back?
Will not it be more easy to add a char* server_root to jk_workerEnv_t?
The simpler, the better.
Not that I proposed initially something like this ;)
On Mon, 8 Apr 2002, jean-frederic clere wrote:
It would be nice to have /usr/local/apache/conf/jk2.properties when httpd is
configured to be in /usr/local/apache (instead of /conf/jk2.properties in the
son processes...).
My first idea is to add makeRoot() in jk_ws_service_t. But I have
On Mon, 8 Apr 2002 [EMAIL PROTECTED] wrote:
My first idea is to add makeRoot() in jk_ws_service_t. But I have the problem
that apache needs a pool (not a jk_pool) to call ap_server_root_relative().
Where could I get the pool?
Actually, that would be a good idea too ( adding another
craigmcc02/04/08 10:46:08
Modified:catalina/src/share/org/apache/catalina/servlets
LocalStrings.properties ManagerServlet.java
webapps/manager manager.xml
webapps/manager/WEB-INF web.xml
Log:
Implement a lookup mechanism to
craigmcc02/04/08 11:02:07
Modified:webapps/tomcat-docs manager-howto.xml
Log:
Update the Manager HOW-TO docs for the new /roles command.
Revision ChangesPath
1.13 +55 -0 jakarta-tomcat-4.0/webapps/tomcat-docs/manager-howto.xml
Index: manager-howto.xml
costin 02/04/08 11:47:53
Added: jk/native2/common jk_pool_apr.c
Removed: jk/native2/server/apache2 jk_pool_apr.c
Log:
Moved jk_pool_apr to common - it's not specific to apache2 ( but can be used
with any other server, if apr is enabled ).
If a server has 'native' pool,
costin 02/04/08 12:17:35
Modified:jk/native2/jni jk_jni_aprImpl.c
Added: jk/native2/common jk_shm.c
Log:
Initial ( and mostly untested ) shared memory code.
It'll work only if APR is enabled ( like all 'advanced' features ).
I also added some minimal code to
costin 02/04/08 12:44:28
Modified:.build.xml
Log:
Few simplifications:
- use the binary version of common-logging. It is trivial to override this
to build-from-source version ( for Gump ), but new users should have minimal
pain.
- call ant in j-t-c/util, don't
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=7850.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hola a todos:
Finally Bug#2342 got to itch me :)), i'm almost done against
j-t-c/native/jk code (tested in 5.0, i need some 4.0 testers, any
volunteers?) , but to my surprise one the features that we make heavy
use of, JNI connector, does not work with j-t-c against 3.3.X , anyone
has tested
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=7850.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
costin 02/04/08 13:00:37
Modified:.build.xml
Log:
Forgot one jar, resources.
XXX Must fix the bugs that prevent putting the whole tomcat_util.jar in common,
check that all utils are 'safe', and move them. Same for common-logging.
Revision ChangesPath
Hi Costin,
I'm curious as to the reason to have connectors_util.jar instead
of just using the tomcat-utils.jar built by j-t-c/util?
Cheers,
Larry
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Mon 4/8/2002 4:00 PM
To: [EMAIL PROTECTED]
Cc:
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=7852.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
My assumption was that future native work would be only in
j-t-c. Once I found time to do my own testing to try to verify
there aren't any regressions, I was going to start removing
native code from j-t. Is this still a good idea?
Cheers,
Larry
-Original Message-
From: Ignacio J.
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=7852.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On Mon, 8 Apr 2002, Larry Isaacs wrote:
Hi Costin,
I'm curious as to the reason to have connectors_util.jar instead
of just using the tomcat-utils.jar built by j-t-c/util?
We have 2 'sets' of utils - one in j-t-c/util, one in j-t.
We also have 2 lib dirs - lib/common and lib/container.
kinman 02/04/08 14:47:30
Modified:jasper2/src/share/org/apache/jasper/compiler Validator.java
Log:
- Make sure that visiBody is called for nodes that may have a body.
Revision ChangesPath
1.2 +10 -3
remm02/04/08 15:03:09
Modified:coyote/src/java/org/apache/coyote Request.java
Log:
- It seems that remoteHost and remoteAddr shouldn't be recycled after each
request, as the connection may last for more than one request/response
(and it would be the responsability of
remm02/04/08 15:29:14
Modified:util/java/org/apache/tomcat/util/handler TcHandlerCtx.java
Log:
- Add type attribute to the handler context (as an int).
Revision ChangesPath
1.2 +32 -1
costin 02/04/08 15:46:58
Modified:coyote/src/java/org/apache/coyote ActionCode.java
Log:
Add the 2 callbacks that are typically needed - one to compute the remote host
and the other for ssl attributes.
Both are expensive and should be done on-demand
Revision Changes
costin 02/04/08 15:49:52
Modified:coyote/src/java/org/apache/coyote Constants.java
InputBuffer.java OutputBuffer.java
Log:
Increase the number of notes per request/response.
Add some comments on Output/InputBuffer.
There are 2 problems:
- they
costin 02/04/08 15:56:22
Modified:coyote/src/java/org/apache/coyote Request.java Response.java
Log:
Allow Request to send callbacks - for lazy-evaluated attributes, and hopefully
to request more data.
Pass the Response/Request as the second param to Action - this allows
costin 02/04/08 15:57:36
Modified:coyote/src/java/org/apache/coyote/tomcat3
Tomcat3Request.java
Log:
Pass the request for lazy attributes to the protocol.
That's used for stuff that is not allways needed ( remote host ) and expensive
to compute.
costin 02/04/08 15:58:40
Modified:jk/java/org/apache/jk/common HandlerRequest.java
Log:
Associate the Request/Response with each other
Revision ChangesPath
1.10 +2 -0
jakarta-tomcat-connectors/jk/java/org/apache/jk/common/HandlerRequest.java
Index:
costin 02/04/08 15:49:52
Modified:coyote/src/java/org/apache/coyote Constants.java
InputBuffer.java OutputBuffer.java
Log:
Increase the number of notes per request/response.
Add some comments on Output/InputBuffer.
There are 2 problems:
-
costin 02/04/08 15:59:37
Modified:jk/java/org/apache/jk/server JkCoyoteHandler.java
Log:
More impl.
Now it kind-of-works ( something is broken in headers, but close )
Revision ChangesPath
1.4 +142 -14
costin 02/04/08 16:07:11
Modified:coyote/src/java/org/apache/coyote Response.java
Log:
sendHeaders() must send the notification - that's what the javadoc says :-)
Now jk adapter works fine.
Revision ChangesPath
1.10 +1 -1
On Mon, 8 Apr 2002, Remy Maucherat wrote:
I'd like those two to stay the way they are. They're not related to the
hooks or actions. I/O should be handled as a special case IMO; faster +
simpler. (could you remove the comments ?)
Ok, but at least add a second parameter ( Request, Response,
costin 02/04/08 16:47:04
Modified:coyote/src/java/org/apache/coyote/tomcat3
CoyoteInterceptor2.java Tomcat3Request.java
Log:
Add the callback for SSL info
Revision ChangesPath
1.3 +26 -0
costin 02/04/08 16:48:22
Modified:http11/src/java/org/apache/coyote/http11
Http11Processor.java
Log:
Add support for the delayed-evaluation of ssl and remote host attributes.
( incomplete )
Revision ChangesPath
1.15 +34 -12
costin 02/04/08 16:49:18
Modified:http11/src/java/org/apache/coyote/http11 Http11Protocol.java
Log:
Set the SSLSupport and socket into the processor, so it can use them in the
hook
Revision ChangesPath
1.4 +12 -30
costin 02/04/08 16:46:32
Modified:coyote/src/java/org/apache/coyote InputBuffer.java
OutputBuffer.java
Log:
Revert the comment
Revision ChangesPath
1.4 +0 -3
manveen 02/04/08 17:06:11
jakarta-tomcat-4.0/webapps/admin/valve - New directory
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
manveen 02/04/08 17:06:45
Added: webapps/admin/valve accessLogValve.jsp
Log:
Added JSP For Access Log Valve.
Revision ChangesPath
1.1 jakarta-tomcat-4.0/webapps/admin/valve/accessLogValve.jsp
Index: accessLogValve.jsp
It's not so much having one util jar, but understanding the differences
between jakarta-tomcat-connectors' tomcat-util.jar and connectors_util.jar.
If they are the same, then I would prefer to use a single name.
Cheers,
Larry
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
63 matches
Mail list logo
