I'm pretty busy these days so I can't works on JK2 as I want to.
Some ideas/reflexions.
JK2 is very similar to JK, from the tomcat point of vue, since the
same ajp13 protocol is used, and may be in such case we could see JK2
too similar to JK to see users switch to JK2 (for instance we're still
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=25977.
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=25977.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
[EMAIL PROTECTED] wrote:
amyroh 2004/01/07 21:32:25
Modified:catalina/src/share/org/apache/catalina/core
StandardHost.java
catalina/src/share/org/apache/catalina/mbeans
MBeanFactory.java
Log:
Fix bugzilla 25878 - Add
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=25878.
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=25948.
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=25948.
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=25948.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
remm2004/01/08 03:11:33
Modified:util/java/org/apache/tomcat/util/http/mapper Mapper.java
Log:
- Cosmetic changes.
- Remove useless check for null.
- Use static on the inner classes.
Revision ChangesPath
1.33 +6 -8
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=25127.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
remm2004/01/08 03:09:03
Modified:webapps/manager/WEB-INF/classes/org/apache/catalina/manager
ManagerServlet.java
Log:
- Undeploy should be called with the displayed path to be able to work on
the root context.
- Bug 25948.
- Submitted by Peter
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=25948.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi,
Since I've started few months ago all the C++ fuzziness (I did posted even
some source to Costin back then),
my intention wasn't to CPP-ize the existing code, but rather to move that
'dead' code on some new tracks.
What I'm looking since then is some kind of different approach to the
Mladen Turk a crit :
Hi,
Since I've started few months ago all the C++ fuzziness (I did posted even
some source to Costin back then),
my intention wasn't to CPP-ize the existing code, but rather to move that
'dead' code on some new tracks.
What I'm looking since then is some kind of different
-Original Message-
From: Henri Gomez [mailto:[EMAIL PROTECTED]
I agree with you that this would be JK3, rather then JK2 on
steroids
:-), and it would require a different perspective.
I'm in favor of _usability_ over performance in that new approach.
JavaGroups or
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=25980.
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=25981.
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=25981.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hate to quote myself, but...
As I said, the performance isn't a priority here, but rather
usability.
I'm sure that TC guys will be open here, and we will see
(perhaps even in
5.1) the 'open TC API', that could be directly used, or
seamlessly integrated from the native side.
I would
remm2004/01/08 05:08:13
Modified:http11/src/java/org/apache/coyote/http11
Http11Processor.java
Log:
- Report an exception which occurred during a low level flush.
Revision ChangesPath
1.93 +1 -0
remm2004/01/08 05:09:04
Modified:catalina/src/share/org/apache/coyote/tomcat5
OutputBuffer.java
Log:
- Throw a wrapped IOE when an exception occurs during a low level flush.
Revision ChangesPath
1.7 +6 -0
remm2004/01/08 05:09:39
Modified:coyote/src/java/org/apache/coyote/tomcat4 OutputBuffer.java
Log:
- Port patch to 4.1.x.
Revision ChangesPath
1.12 +6 -0
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat4/OutputBuffer.java
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=4663.
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=25980.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
remm2004/01/08 05:56:36
Modified:util/java/org/apache/tomcat/util/threads ThreadPool.java
Log:
- Some suggestions that were sent by Dave Dice. Jean François assured me
he did test this, so since this looks harmless to me (and won't hurt performance
either), I'm willing
respected sir,
I have a problem in configuration of TOMCAT4.1.29 ...
I am working on win98
jdk1.3.1_09
there is a problem while run JSP file ..
syntax error message is desplay when I run startup.bat file
so, please give your suggession
ronak
-
Do you
From: Ronak Patel
respected sir,
I have a problem in configuration of TOMCAT4.1.29 ...
I am working on win98
jdk1.3.1_09
First of all I would suggest that you move to some NT-based platform, but
only after resolving the cause of a problem.
there is a problem while run JSP file
Hi,
I have found recently that current TomCat 5 uses different
encoding for POST and GET parameters. I was quite surprised,
because all bugs opened for this issue are just closed as invalid
without an explanation.
But after a long searching I found the discussion about bug 23929 at
Martin Kuba wrote:
Hi,
I have found recently that current TomCat 5 uses different
encoding for POST and GET parameters. I was quite surprised,
because all bugs opened for this issue are just closed as invalid
without an explanation.
But after a long searching I found the discussion about bug
remm2004/01/08 06:55:57
Modified:webapps/docs proxy-howto.xml
Log:
- No className is needed anymore.
Revision ChangesPath
1.6 +3 -4 jakarta-tomcat-catalina/webapps/docs/proxy-howto.xml
Index: proxy-howto.xml
Remy Maucherat wrote:
Using different encoding for GET and POST parameters by default
is counter-intuitive and breaks the Principle of least astonishment.
If it is kept that way, the same bug will be reported again and again.
-1.
The attribute, now that it actually exists, is well documented.
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=24545.
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=25981.
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=25981.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
The major mistake in jk2 is the 2 in the name. It was an error to
fork ( even if it was easier to code and move it ) instead of improving
mod_jk and adding/fixing.
In JNI mode and from configuration perspective - as well as ability to
use non-tcp-socket communation - jk2 is way ahead. As code
From: Costin Manolache
So my suggestion ( deja vue ? ) is to use evolution :-). A change in
the OO model ( if needed ) or fixing/improving the current one is not
as big change as it seems - it's mostly in initialization code.
How about 'revolution'? On the other hand how does the evolution
Remy Maucherat wrote:
[EMAIL PROTECTED] wrote:
amyroh 2004/01/07 21:32:25
Modified:catalina/src/share/org/apache/catalina/core
StandardHost.java
catalina/src/share/org/apache/catalina/mbeans
MBeanFactory.java
Log:
Fix
Amy Roh wrote:
Remy Maucherat wrote:
[EMAIL PROTECTED] wrote:
amyroh 2004/01/07 21:32:25
Modified:catalina/src/share/org/apache/catalina/core
StandardHost.java
catalina/src/share/org/apache/catalina/mbeans
Mark Woon wrote:
Hi all,
I'm reposting this in the hopes that someone will responsd.
I have a custom Realm implementation that extends
org.apache.catalina.realm.RealmBase. It used to work in 4.x, but in
5.0.16, I'm getting the following exception on startup:
21:17:29,719 ERROR RealmBase:1092 -
I'm re-forwarding this message to the list for (hopefully) discussion.
I sent this the first time as 5.0 was going final, so people where very
busy. I get very regular personal questions about this topic as people
cull the list archives and find me. Also, I think I've seen two more
bugs 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=24308.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I agree that the current connectors (jk and jk2) are fairly stable and
done because they just work. The hardest part in using them is that
there is a lot of duplicated setup between the Java/Tomcat side and the
webserver configuration just to get things working. Then, when you add
a new webapp
remm2004/01/08 14:50:32
Modified:coyote/src/java/org/apache/coyote/tomcat4
CoyoteConnector.java
Log:
- For the TC 4.1 branch, use the same default as in TC 4.1.27.
Revision ChangesPath
1.29 +5 -5
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=24308.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
When JMX is enabled, in the jk2.properties file, and configured to use
the MX4J JRMP interal adapter, a rmi registry is created and bound to
the default port of 1099. If there is another application using that
port and bind expection is thrown and the adaptor is never enabled.
A configuration
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=10563.
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=14077.
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=26006.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
The option mx.jrmpPort is used for registering the JRMPAdaptor to the
NamingService, by setting the PROVIDER_URL. When the NamingService is
regeristered it creates the rmi registry whiCh defaults to 1099.
The code below will show what I mean about setting the port on the rmi
registry. 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=11909.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Amy Roh wrote:
Mark Woon wrote:
I've taken a look at the source, and as far as I can tell, it's because
the container is null. What is responsible for providing the Realm the
container it's in? Is there some new bit of configuration I need to do
in Tomcat 5? I'm also surprised that
fhanik 2004/01/08 18:50:54
Modified:modules/cluster/src/share/org/apache/catalina/cluster/mcast
McastService.java
modules/cluster/src/share/org/apache/catalina/cluster/tcp
ReplicationListener.java SimpleTcpCluster.java
fhanik 2004/01/08 18:53:08
Modified:modules/cluster/src/share/org/apache/catalina/cluster/tcp
ReplicationListener.java
Log:
removed println
Revision ChangesPath
1.9 +4 -4
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=26010.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Mladen Turk wrote:
From: Costin Manolache
So my suggestion ( deja vue ? ) is to use evolution :-). A change in
the OO model ( if needed ) or fixing/improving the current one is not
as big change as it seems - it's mostly in initialization code.
How about 'revolution'? On the other hand how does
55 matches
Mail list logo
