Keith Wannamaker wrote:
The numbers were suspect because I was running 3.3 under
JBuilder but 4.0 externally, I'd imagine. I set up clean
tomcat trees and ran them outside of any test environment
and I get these numbers: (100 rqs/10 concurrent cx)
TC 4.0.6 | TC 3.3.2
On Thu, 24 Oct 2002, Remy Maucherat wrote:
| ... as well as the Catalina and CatalinaService classes. The idea is to
| remove the *Service, and have only one set of classes (which would still
| handle all use cases). There has been a number of random method
| additions which make the whole thing
Hi!
In recent days i don't get jasper compiler error messages anymore, instead
i see nothing from the point the processing of the page produces errors.
But i don't know what i have missconfigured because i often change tomcat
versions. How can i get these error messages.
Many thanks in
remm2002/11/08 03:32:37
Modified:catalina/src/share/org/apache/catalina/mbeans
MBeanUtils.java
Log:
- Fix bug creating and editing a resource link. Since name is part of the MBean
name, it cannot be changed without removing the object.
Revision
remm2002/11/08 03:32:51
Modified:webapps/admin/WEB-INF/classes/org/apache/webapp/admin/resources
SaveResourceLinkAction.java
Log:
- Fix bug creating and editing a resource link. Since name is part of the MBean
name, it cannot be changed without
Hi,
Probably shuld, but I hate to STWF ;).
In 4.0 the /app/WEB-INF/classes/ were mapped to the /app/servlet/
In 4.1 I need explicitly to put the
servlet-mapping
servlet-nameinvoker/servlet-name
url-pattern/servlet/*/url-pattern
/servlet-mapping
So that can work.
Is
remm2002/11/08 03:48:46
Modified:webapps/admin/WEB-INF/classes/org/apache/webapp/admin/resources
SaveResourceLinkAction.java
Log:
- Port fix.
- Fix resource link edition and creation.
Revision ChangesPath
1.6 +4 -9
remm2002/11/08 03:49:29
Modified:catalina/src/share/org/apache/catalina/mbeans
MBeanUtils.java
Log:
- Port fix.
- Fix resource link edition and creation.
Revision ChangesPath
1.45 +5 -8
I have to disagree with this, jspc is a pre compiler, not a webapp
packager.
John
I agree that JSPC needs to be simplified and that the webapp
mode should be retained. But the webapp mode should allow
for a war file to be generated which is self contained
including the precompiled JSP
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=14386.
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=14386.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Mladen Turk wrote:
Hi,
Probably shuld, but I hate to STWF ;).
In 4.0 the /app/WEB-INF/classes/ were mapped to the /app/servlet/
In 4.1 I need explicitly to put the
invoker
/servlet/*
So that can work.
Is this correct behaviour for 4.1 or I'm I missing something?
The
I was wondering if people have been testing Jasper 2 from Tomcat 5 with
flushing disabled. If testing is ok (Watchdog is, but from my experience
it's not enough ;-) ), I would be willing to port it to the 4.1.x
branch. I have yet to see a problem using the latest Tomcat 5 code (I
think it's a
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=13519.
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=14377.
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=14372.
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=14367.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Remy Maucherat wrote:
I was wondering if people have been testing Jasper 2 from Tomcat 5 with
flushing disabled. If testing is ok (Watchdog is, but from my experience
it's not enough ;-) ), I would be willing to port it to the 4.1.x
branch. I have yet to see a problem using the latest Tomcat 5
jean-frederic clere wrote:
Remy Maucherat wrote:
I was wondering if people have been testing Jasper 2 from Tomcat 5
with flushing disabled. If testing is ok (Watchdog is, but from my
experience it's not enough ;-) ), I would be willing to port it to the
4.1.x branch. I have yet to see a
hgomez 2002/11/08 06:33:04
Modified:catalina/docs/dev/xdocs/images jakarta-logo.gif
Log:
Use latest jakarta logo
Revision ChangesPath
1.2 +77 -50
jakarta-tomcat-4.0/catalina/docs/dev/xdocs/images/jakarta-logo.gif
Binary file
--
To
hgomez 2002/11/08 06:33:32
Modified:webapps/tomcat-docs/images jakarta-logo.gif
Log:
Use latest jakarta logo
Revision ChangesPath
1.2 +77 -50jakarta-tomcat-4.0/webapps/tomcat-docs/images/jakarta-logo.gif
Binary file
--
To unsubscribe, e-mail:
remm2002/11/08 06:56:44
Modified:jasper2/src/share/org/apache/jasper/runtime Tag:
tomcat_4_branch PageContextImpl.java
Log:
- Port revised non flushing patch.
- It appears not to be causing problems during my testing. If it does, the patch
should be
remm2002/11/08 06:58:39
Modified:.RELEASE-NOTES-4.1.txt
Log:
- Document changes over 4.1.14.
Revision ChangesPath
1.28 +38 -1 jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt
Index: RELEASE-NOTES-4.1.txt
I´ve done it and the problem continues: I´ve included the self-signed and
intermedia certificates in cacerts (
perhaps it´s a problem with the java environment?
what files is necesary to configure in order to obtain client-cert
authentication?
Thanks a lot for the interest.
- Original
remm2002/11/08 07:26:50
Modified:.build.xml
Log:
- Ooops, about 600K of classes were duplicated in the binary distributions.
Revision ChangesPath
1.58 +0 -3 jakarta-tomcat-5/build.xml
Index: build.xml
Can somebody help, i think the adding simply the removed Code from
SSLServerSocketFactory help's, but that is not the answer.
Mit freundlichen Grüssen
i.A. Torsten Fohrer
**
* DCSI AG* Tel.: +49 7131 155 88-0 *
*
I've encountere da case where, in addition to extra PATH information, I also need some
extra environment variables. It would be nice to be able to set these in the local
environment of the tomcat.exe process as I do with the extra path. Is 'tomcat.exe'
part of the Tomcat project, or is it a
peter lin wrote:
On a related note to flushing. I've discovered a bug, but don't want to
file one until I know for sure it's not a duplicate of the other flush
bugs already in bugzilla.
The bug is the following:
if a page throws an exception and an errorPage directive is set, the
resulting
Found the error, the socketFactory isn't set in CoyoteConnecter, for the
CoyoteProtocoll Handler
Here is a diff
Index: CoyoteConnector.java
===
RCS file:
/home/cvspublic/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/
thanks remy for the information that helps. What if I decide to buffer
the response myself in a response wrapper? Does catalina try to call
clearBuffer, reset, resetBuffer, flush or flushBuffer in the event a
request is passed to my errorpage? Also, does the status code change
and the
Remy Maucherat wrote:
jean-frederic clere wrote:
Remy Maucherat wrote:
I was wondering if people have been testing Jasper 2 from Tomcat 5
with flushing disabled. If testing is ok (Watchdog is, but from my
experience it's not enough ;-) ), I would be willing to port it to the
4.1.x branch.
Torsten Fohrer wrote:
Found the error, the socketFactory isn't set in CoyoteConnecter, for the
CoyoteProtocoll Handler
I'm sorry, but what exactly doesn't work ? SSL works very well with
4.1.12+. Your patch doesn't make sense (and I can't understand your
first message, which doesn't help
peter lin wrote:
thanks remy for the information that helps. What if I decide to buffer
the response myself in a response wrapper? Does catalina try to call
clearBuffer, reset, resetBuffer, flush or flushBuffer in the event a
request is passed to my errorpage? Also, does the status code
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=14391.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
thanks again for the information. I will go with setting the buffer
then.
peter
Remy Maucherat wrote:
peter lin wrote:
thanks remy for the information that helps. What if I decide to buffer
the response myself in a response wrapper? Does catalina try to call
clearBuffer, reset,
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=14391.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
We are having a problem with Catalina 4.1.12 (I believe we also had issues with
previous versions, but can't say for sure) with respect to how POSTed requests are
handled if the transfer encoding is chunked. It seems that request parameters in the
content are not processed in this case.
Moisés Serrano Martínez wrote:
I´ve done it and the problem continues: I´ve included the self-signed and
intermedia certificates in cacerts (
perhaps it´s a problem with the java environment?
what files is necesary to configure in order to obtain client-cert
authentication?
The only thing I am
Adrian Sampaleanu wrote:
We are having a problem with Catalina 4.1.12 (I believe we also had
issues with previous versions, but can't say for sure) with respect to
how POSTed requests are handled if the transfer encoding is chunked.
It seems that request parameters in the content are not
In o.a.c.loader.WebAppClassLoader.java, realFile.toURI() isn't known by
SDK 1.3.1 ..
/**
* Get URL.
*/
protected URL getURI(File file)
throws MalformedURLException {
File realFile = file;
try {
realFile = realFile.getCanonicalFile();
The problem is that with some MIDP implementations, even if you set the
content-length, the implementation, or possibly some gateway, can change the request
to chunked. I believe they would do this in order to control the flow of data the
mobile network. In our case this does, in fact, happen.
Remy Maucherat wrote:
Adrian Sampaleanu wrote:
We are having a problem with Catalina 4.1.12 (I believe we also had
issues with previous versions, but can't say for sure) with respect
to how POSTed requests are handled if the transfer encoding is
chunked. It seems that request parameters 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=14391.
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=14391.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
In section 9.5 describing the POST method, there is a paragraph:
POST requests MUST obey the message transmission requirements set out
in section 8.2
but scanning through 8.2, I don't see a limitation of POSTed requests not being
allowed to be sent through chunking as Ryan also pointed out.
I have yesterday and today migrate a system to 4.1.14, from 4.0.4 tomcat
with own patches. After some work with migrating the patches, and finally
testing there.
It seems that tomcat doesn't start/creates the SSL ServerSocket.
after some search in the cvs tree, i see that the CoyoteConnector
Remy, I don't even know if 4.1.x and 5.0 share the bug or not;
I haven't tested it, though I suspect they do. I do know 4.0.6
has the bug.
I'm not sure what interpretation you are questioning -- if it
is the placement or nature of the fix, sure, I said someone may
want to tweak the location and
Very good eyes Bill, I agree. The correct fix would have to
incorporate both the context name and the constraint URI.
Keith
| -Original Message-
| From: Bill Barker [mailto:wbarker;wilshire.com]
| Sent: Friday, November 08, 2002 2:11 AM
| To: Tomcat Developers List
| Subject: Re: auth
Keith Wannamaker wrote:
Remy, I don't even know if 4.1.x and 5.0 share the bug or not;
I haven't tested it, though I suspect they do. I do know 4.0.6
has the bug.
I'm not sure what interpretation you are questioning -- if it
is the placement or nature of the fix, sure, I said someone may
want
thanks a lot.
I´ll try it this weekend
- Original Message -
From: jean-frederic clere [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Friday, November 08, 2002 5:59 PM
Subject: Re: Client-cert authentication.
Moisés Serrano Martínez wrote:
I´ve done it and the
luehe 2002/11/08 11:11:26
Modified:jasper2/src/share/org/apache/jasper/runtime
PageContextImpl.java
Log:
Made enumeration of ValidationMessage[] returned by TLV's validate()
method more robust by also considering the case where a
ValidationMessage
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=14367.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
luehe 2002/11/08 11:42:56
Modified:jasper2/src/share/org/apache/jasper/compiler Generator.java
JspDocumentParser.java Node.java Parser.java
Validator.java
jasper2/src/share/org/apache/jasper/resources
kinman 2002/11/08 11:55:47
Modified:jasper2/src/share/org/apache/jasper/compiler Generator.java
JspDocumentParser.java Node.java PageInfo.java
TagConstants.java Validator.java
jasper2/src/share/org/apache/jasper/resources
Glenn Nielsen wrote:
Remy Maucherat wrote:
[...]
I agree that JSPC needs to be simplified and that the webapp mode should
be retained. But the webapp mode should allow for a war file to be
generated
which is self contained including the precompiled JSP classses. And for
the
generated war to
Costin Manolache wrote:
Hans Bergsten wrote:
Removing the CLI and keeping the basic functionality seems like
a good idea.
CLI as in ...? Sorry, I'm not familar with this acronym.
Command line interface. jspc.sh, main() and the argument processing.
Ah, I should have known ;-)
Just use
Here is another set of JSP 2.0 API changes and clarifications, based on
feedback from various sources. Please let me know if there are any
questions or concerns.
jsr152/src/share/javax/servlet/jsp/JspContext.java
- Clarified that removeAttribute( name ) removes from all scopes
- Clarified
Jonathan Eric Miller wrote:
I have a patch as well which I submitted back in June. I haven't received a
response either.
Well I guess you and I are the only ones using SSL to connect to our
directory servers...
It would be nice if someone reviewed our patches, merged and commited
them, or
kinman 2002/11/08 13:30:21
Modified:jsr152/src/share/dtd jsp_2_0.xsd jspxml.dtd jspxml.xsd
web-jsptaglibrary_2_0.xsd
jsr152/src/share/javax/servlet/jsp JspContext.java
jsr152/src/share/javax/servlet/jsp/tagext PageData.java
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=12413.
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=14405.
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=14405.
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=14405.
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=14405.
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=14405.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
65 matches
Mail list logo
