Hi all.
The description concerning the setting of MySQL is old.
I hope the description that corresponds to version 5.x. :-D
Kazuki Aranami
-
To unsubscribe, e-mail: [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://issues.apache.org/bugzilla/show_bug.cgi?id=39834.
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://issues.apache.org/bugzilla/show_bug.cgi?id=40305.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Rainer Jung wrote:
Jim Jagielski schrieb:
In a nutshell, there are many cases where Apache httpd and
Tomcat are separated by a firewall, and, as such, there
isn't a one-to-one direct connection. The firewall
will close a connection but one side doesn't
know about it.
I would call this
I still don't have a consistent idea what happened around the firewall:
- silently dropping is not expected apart from a deny rule, but deny
will not be the rule that had been applied to the apache-tomcat connection.
- only shutting down one side of an established (!) connection seems broken
-
Rainer Jung wrote:
I still don't have a consistent idea what happened around the firewall:
It is a very simple:
1. There are firewalls that will cut the connection
between mod_jk and Tomcat without sending FIN.
You can not do anything with that, cause they
simply exist, and I don't
Here my impressions of the situation from an serveradmin perspective.
On Wed, 2006-08-23 at 17:08 +0200, Rainer Jung wrote:
I still don't have a consistent idea what happened around the firewall:
- silently dropping is not expected apart from a deny rule, but deny
will not be the rule that
Klaus Wagner schrieb:
Here my impressions of the situation from an serveradmin perspective.
On Wed, 2006-08-23 at 17:08 +0200, Rainer Jung wrote:
I still don't have a consistent idea what happened around the firewall:
- silently dropping is not expected apart from a deny rule, but deny
Hi Mladen,
Mladen Turk schrieb:
Rainer Jung wrote:
I still don't have a consistent idea what happened around the firewall:
It is a very simple:
I don't think so, because no one was able to give the details. From a
simple perspective everything is clear, but only the details will give
an
having mod_jk rely on the AJP packet from Tomcat to close a socket or
not, is like saying the IE browser can't close the socket unless Apache
httpd says so.
The patch the Jim provided, gives us the functionality of turning off
the keep alive from the clients (httpd in this case) perspective.
Author: rjung
Date: Wed Aug 23 10:22:00 2006
New Revision: 434087
URL: http://svn.apache.org/viewvc?rev=434087view=rev
Log:
Change default log level from debug/undefined to info.
Modified:
tomcat/connectors/trunk/jk/native/apache-1.3/mod_jk.c
Author: rjung
Date: Wed Aug 23 10:26:01 2006
New Revision: 434089
URL: http://svn.apache.org/viewvc?rev=434089view=rev
Log:
Fix typo in debug message.
Modified:
tomcat/connectors/trunk/jk/native/apache-1.3/mod_jk.c
tomcat/connectors/trunk/jk/native/apache-2.0/mod_jk.c
Modified:
Author: rjung
Date: Wed Aug 23 10:40:03 2006
New Revision: 434096
URL: http://svn.apache.org/viewvc?rev=434096view=rev
Log:
Addon for r434087 (default log level)
Modified:
tomcat/connectors/trunk/jk/native/common/jk_global.h
Modified: tomcat/connectors/trunk/jk/native/common/jk_global.h
Author: rjung
Date: Wed Aug 23 10:42:15 2006
New Revision: 434098
URL: http://svn.apache.org/viewvc?rev=434098view=rev
Log:
Correct placement of comment.
Modified:
tomcat/connectors/trunk/jk/native/common/jk_service.h
Modified: tomcat/connectors/trunk/jk/native/common/jk_service.h
URL:
Author: rjung
Date: Wed Aug 23 11:11:13 2006
New Revision: 434110
URL: http://svn.apache.org/viewvc?rev=434110view=rev
Log:
Make constant naming more consistent, separate defaults from values.
Modified:
tomcat/connectors/trunk/jk/native/common/jk_lb_worker.c
Author: rjung
Date: Wed Aug 23 11:26:56 2006
New Revision: 434119
URL: http://svn.apache.org/viewvc?rev=434119view=rev
Log:
Change note names and symbols to make them more consistent.
Add a note with the worker type. More notes are to come.
Documentation of the notes is still missing but
Author: rjung
Date: Wed Aug 23 11:45:30 2006
New Revision: 434122
URL: http://svn.apache.org/viewvc?rev=434122view=rev
Log:
Fix r434110.
Modified:
tomcat/connectors/trunk/jk/native/common/jk_lb_worker.h
Modified: tomcat/connectors/trunk/jk/native/common/jk_lb_worker.h
URL:
Jean-Frederic, Bill, Remy,
I didn't get any response to this, but would really like to hear your
thoughts on this issue of parameters within URL path segments, which
tomcat current does not allow. Can you give me any feedback?
Thanks!
James
On Aug 21, 2006, at 8:42 PM, James Berry wrote:
Author: rjung
Date: Wed Aug 23 12:17:14 2006
New Revision: 434128
URL: http://svn.apache.org/viewvc?rev=434128view=rev
Log:
Add another server hook add_log_items to be able to return textual
result tokens to include in server logging.
We will use this in the load balancer to return names of used
Mladen Turk schrieb:
The patch the Jim provided, gives us the functionality of turning off
the keep alive from the clients (httpd in this case) perspective.
I do not agree, although its a hack and easy fix for
the problem itself.
I would prefer the more useful 3 param connections/pool
Author: rjung
Date: Wed Aug 23 12:39:12 2006
New Revision: 434138
URL: http://svn.apache.org/viewvc?rev=434138view=rev
Log:
iAnd another fix for r434110.
Modified:
tomcat/connectors/trunk/jk/native/common/jk_status.c
Modified: tomcat/connectors/trunk/jk/native/common/jk_status.c
URL:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40306.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Author: rjung
Date: Wed Aug 23 12:51:31 2006
New Revision: 434141
URL: http://svn.apache.org/viewvc?rev=434141view=rev
Log:
New features for jk_status:
- When a request updates data, the response does a meta redirect
to the list view, so that a following browser refresh by the user does
not
Hi,
It's not only in the 4.1.31 release, it's even in the latest stable
5.5.17. Let's change it in the next releases of 4.x and 5.x, starting
with 5.5.18 which should happen any day now.
I think the advice was decent (and based on empirical evidence IIRC)
when originally issued, but that was
Yoav Shapira wrote:
Hi,
It's not only in the 4.1.31 release, it's even in the latest stable
5.5.17. Let's change it in the next releases of 4.x and 5.x, starting
with 5.5.18 which should happen any day now.
I think the advice was decent (and based on empirical evidence IIRC)
when
Hi Jean-Frederic,
On Aug 23, 2006, at 1:24 PM, Jean-frederic Clere wrote:
James Berry wrote:
Jean-Frederic, Bill, Remy,
I didn't get any response to this, but would really like to hear
your thoughts on this issue of parameters within URL path
segments, which tomcat current does not
Rainer Jung wrote:
Mladen Turk schrieb:
The patch the Jim provided, gives us the functionality of turning off
the keep alive from the clients (httpd in this case) perspective.
I do not agree, although its a hack and easy fix for
the problem itself.
I would prefer the more
Author: rjung
Date: Wed Aug 23 14:02:24 2006
New Revision: 434177
URL: http://svn.apache.org/viewvc?rev=434177view=rev
Log:
Cleanup of the code structure of the service method.
Adding TACE, JK_LOG_NULL_PARAMS and do the same null pointer
checks in all service methods.
95% of the diff log comes
Hi,
It's one reason we moved Announcement (httpd's short summary, similar
to the tomcat RELEASE-NOTES) out of the project tree and tarball, and
host those directly in /dist/httpd/ - they can be fixed/amended after
the release without rerolling.
I don't mind doing the same with Tomcat. We can
James Berry wrote:
My response is that the tomcat should be completely blind to
parameters. Basically, to Tomcat's perspective, they don't exist.
There is nothing any more special about this;biz=bar than
this,biz=bar or this-biz-bar.
But, of course, your access control does call out a
Author: rjung
Date: Wed Aug 23 14:15:03 2006
New Revision: 434185
URL: http://svn.apache.org/viewvc?rev=434185view=rev
Log:
Remove obsolete parameter from get_most_suitable_worker().
Modified:
tomcat/connectors/trunk/jk/native/common/jk_lb_worker.c
Modified:
Hi William,
On Aug 23, 2006, at 2:05 PM, William A. Rowe, Jr. wrote:
James Berry wrote:
My response is that the tomcat should be completely blind to
parameters. Basically, to Tomcat's perspective, they don't exist.
There is nothing any more special about this;biz=bar than
this,biz=bar or
Author: rjung
Date: Wed Aug 23 14:30:15 2006
New Revision: 434189
URL: http://svn.apache.org/viewvc?rev=434189view=rev
Log:
Moving getting the session id out of get_most_suitable_worker
into the service method. Doing it once is enough.
Also so minor cleanups.
Modified:
James Berry wrote:
Because Tomcat and Apache are blind to parameters, the connector -should-
reject them. When Tomcat/Apache are able to treat your this;biz=bar
example the same as this for the purpose of access control, then they
can be enabled in an opaque manner that lets the application
On Aug 23, 2006, at 2:22 PM, James Berry wrote:
Tomcat should be blind to the very existence of parameters
because it
doesn't place any meaning on them.
Perhaps I should clarify that when I say tomcat should be blind to
parameters, perhaps I really should have said Tomcat should not be
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40307.
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://issues.apache.org/bugzilla/show_bug.cgi?id=40307.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
On Aug 23, 2006, at 2:40 PM, William A. Rowe, Jr. wrote:
James Berry wrote:
Because Tomcat and Apache are blind to parameters, the connector -
should-
reject them. When Tomcat/Apache are able to treat your
this;biz=bar
example the same as this for the purpose of access control,
then
James Berry wrote:
On Aug 23, 2006, at 2:40 PM, William A. Rowe, Jr. wrote:
James Berry wrote:
So maybe this is the crux of it. Why/where is it that this;biz=bar
cannot be treated the same for the purposes of access control as this?
The URL spec says that these are equally valid, and
Hi Bill,
On Aug 23, 2006, at 3:35 PM, William A. Rowe, Jr. wrote:
James Berry wrote:
What I'm saying is that they should not be treated independently or
differently. They should be treated not as metadata, but as part
of the
segment.
To be 100% clear; this is what Apache httpd does
Author: markt
Date: Wed Aug 23 16:47:06 2006
New Revision: 434252
URL: http://svn.apache.org/viewvc?rev=434252view=rev
Log:
Update the release notes.
Modified:
tomcat/container/branches/tc4.1.x/RELEASE-NOTES-4.1.txt
Modified: tomcat/container/branches/tc4.1.x/RELEASE-NOTES-4.1.txt
URL:
Author: markt
Date: Wed Aug 23 16:50:40 2006
New Revision: 434253
URL: http://svn.apache.org/viewvc?rev=434253view=rev
Log:
Remove old file.
Removed:
tomcat/container/branches/tc4.1.x/BUGS.txt
-
To unsubscribe, e-mail:
All,
This vote passed (thanks to those that voted) but with the help of
Simon Kitching on the commons-dev list bug 40252 has been fully
resolved. Therefore I do not intend to go further with this release
but to go to 4.1.34. This also allows the RELEASE-NOTES changes raised
earlier today to be
Cool, I was about to ask that we include the RELEASE-NOTES changes in
the next 4.1 cut. Thanks, and +1,
Yoav
On 8/23/06, Mark Thomas [EMAIL PROTECTED] wrote:
All,
This vote passed (thanks to those that voted) but with the help of
Simon Kitching on the commons-dev list bug 40252 has been
Modified:
tomcat/container/branches/tc4.1.x/catalina/src/share/org/apache/naming/resources/ResourceAttributes.java
URL:
http://svn.apache.org/viewvc/tomcat/container/branches/tc4.1.x/catalina/src/share/org/apache/naming/resources/ResourceAttributes.java?rev=434283r1=434282r2=434283view=diff
Author: markt
Date: Wed Aug 23 19:01:40 2006
New Revision: 434285
URL: http://svn.apache.org/viewvc?rev=434285view=rev
Log:
Fix javadoc warnings
Modified:
tomcat/jasper/branches/tc4.1.x/build.xml
Modified: tomcat/jasper/branches/tc4.1.x/build.xml
URL:
Author: markt
Date: Wed Aug 23 19:33:33 2006
New Revision: 434291
URL: http://svn.apache.org/viewvc?rev=434291view=rev
Log:
Prevent Javadoc warnings when building with Java 5
Modified:
tomcat/container/branches/tc4.1.x/catalina/build.xml
Modified:
Author: markt
Date: Wed Aug 23 19:45:02 2006
New Revision: 434292
URL: http://svn.apache.org/viewvc?rev=434292view=rev
Log:
Final fix for bug 40252 - upgrade to commons-logging 1.1
Modified:
tomcat/container/branches/tc4.1.x/RELEASE-NOTES-4.1.txt
48 matches
Mail list logo