Hi ,
Sorry to bother you all but I have a problem when I changed my Tomcat 4.0 to 3.3
It seems that this problem has been resolved before, but I can't find the answer.
I have the exception :
Class not found: TOMCAT/JSP/.../myJsp.jsp
Status code:404 request:R( /mi0101_mnt +
Has anyone managed to get tomcat 3.3.1a to work with mod_jk2
and if so how ?
Thanks
David
--
This e-mail may contain confidential and/or privileged information. If you are not the
intended recipient (or have received this e-mail in error) please notify the sender
immediately and destroy
Has anybody ever pointed out that the EmbededTomcat.java of Tomcat
3.3.x is mispelled? Is this something that should be fixed? I can
submit a patch, if so. :)
Maybe at least the debug messages, since those are visible to the
users.
Actually, it looks like this misspelling has been carried
Hi,
I am having problems trying to configure TOMCAT 3.3 to work with IIS 4.0, via
isapi_redirect.dll
When I am doing an upload of a file larger than 100Mbytes I get an 'out of memory'
error.
I already tried to set the parameters cmd_line= -Xmx256m -Xss64k to the file
wrapper.properties.
If I
Now that we have mod_jk present on JTC, what about removing it from TC
3.3.2 CVS ?
Also is it planned to remove util and use only the one present in JTC ?
From build/gump it seems that util from JTC will be used but
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional
On Fri, 2002-09-13 at 19:46, Henri Gomez wrote:
Now that we have mod_jk present on JTC, what about removing it from TC
3.3.2 CVS ?
+1
Bojan
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
-Original Message-
From: Henri Gomez [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 13, 2002 5:47 AM
To: [EMAIL PROTECTED]
Subject: Tomcat 3.3 repository changes
Now that we have mod_jk present on JTC, what about removing
it from TC
3.3.2 CVS ?
Also is it planned to remove util
bug in Tomcat 3.3.
Hi,
If two requests enter ReloadInterceptor.contextMap()
simultaneously and both reload context, it causes
duplicate context reloading.
-- messages --
2002-08-19 16:15:16 - ContextManager: Removing context
DEFAULT:/examples
2002-08-19 16:15:16
Hi,
If two requests enter ReloadInterceptor.contextMap()
simultaneously and both reload context, it causes
duplicate context reloading.
-- messages --
2002-08-19 16:15:16 - ContextManager: Removing context
DEFAULT:/examples
2002-08-19 16:15:16 - ContextManager: Removing
As I tested, when context reloads in Tomcat 3.3.1,
e.g. caused by modification of servlet class, sessions
are lost. Is it true for all Tomcat 3.3.x? Is there
any switch in source code which can change this
behavior and maintain sessions through context
reloading?
Thanks for your help.
Hugh
I changed switch fullReload in ReloadInterceptor
from true to false, and sessions are maintained
through context reloading. (Of course, because the old
context remains.) Is there any disadvantage if I set
this way? Anyway fullReload=true is default setting.
Thanks.
Hugh
List [EMAIL PROTECTED]
Sent: Monday, August 12, 2002 5:50 AM
Subject: Question about Session in Tomcat 3.3 -- continued...
I changed switch fullReload in ReloadInterceptor
from true to false, and sessions are maintained
through context reloading. (Of course, because the old
context remains
/show_bug.cgi?id=5411
JSP session does not work with IE/IIS5/Tomcat 3.3
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|REOPENED|RESOLVED
On the java side ?
I think we should just use commons-logging, and the admin/
or manager/ or some other ( java-based code ) to control
the underlying logger ( which should probably default to log4j
when somebody has the time to do this ).
commons-logging seems a good way to hide log4j or
](. .)
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
-Original Message-
From: Bojan Smojver [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 30, 2002 12:40 AM
To: Tomcat Dev List
Subject: RE: logrotate and tomcat 3.3/4.0/4.1
This works
And surprise!!, 3.3 it's suppoussed to have another logrotate inside,
broken, but the code is there.. just need that someones have spare
cycles to fix it..
I started take a look a log stuff in 3.3.2 and will see how
to fix the logrotate support or better add log4j support ?
--
To unsubscribe,
Quoting GOMEZ Henri [EMAIL PROTECTED]:
Whaou.
Didn't now about copytruncate option of logrotate.
It has some downsides too. But it's documented in the manual page, so everyone
should know what to expect.
Under Linux there is truncate and ftruncate calls
but I wonder how it works
Hi to all,
Did there is plan to help implement logrotate
for Tomcat 3.3/4.0/4.1 ?
On production the logs could became very important
after weeks of use and should be cleanup.
The usual way under Unix is to use logrotate which
generally send a KILL -HUP/USR1 to the process which in
turn close
I don't really know much about log4j, so I can't comment on that particular
methodology, but I'd been looking at implementing a logrotate for tomcat on my
systems. I was thinking something like this for tomcat 3.3 (haven't looked at 4.x
yet):
/var/log/tomcat3/jasper-*.log /var/log/tomcat3
I don't really know much about log4j, so I can't comment on
that particular methodology, but I'd been looking at
implementing a logrotate for tomcat on my systems. I was
thinking something like this for tomcat 3.3 (haven't looked at
4.x yet):
/var/log/tomcat3/jasper-*.log /var/log/tomcat3
there is plan to help implement logrotate
for Tomcat 3.3/4.0/4.1 ?
On production the logs could became very important
after weeks of use and should be cleanup.
The usual way under Unix is to use logrotate which
generally send a KILL -HUP/USR1 to the process which in
turn close its open logs files
GOMEZ Henri [EMAIL PROTECTED] wrote:
Hi to all,
Did there is plan to help implement logrotate
for Tomcat 3.3/4.0/4.1 ?
On production the logs could became very important
after weeks of use and should be cleanup.
The usual way under Unix is to use logrotate which
generally send
that those are not open by the JVM process... Therefore the
best course of
action is doing like catalina does... Which already has a some-sort of
logrotate built in...
And surprise!!, 3.3 it's suppoussed to have another logrotate inside,
broken, but the code is there.. just need that
Ignacio J. Ortega [EMAIL PROTECTED] wrote:
that those are not open by the JVM process... Therefore the
best course of
action is doing like catalina does... Which already has a some-sort of
logrotate built in...
And surprise!!, 3.3 it's suppoussed to have another logrotate inside,
This works (TC 3.3.x):
/var/tomcat/logs/*.log {
copytruncate
weekly
rotate 52
compress
missingok
}
Bojan
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
/show_bug.cgi?id=5411
JSP session does not work with IE/IIS5/Tomcat 3.3
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|REOPENED|RESOLVED
/show_bug.cgi?id=5411
JSP session does not work with IE/IIS5/Tomcat 3.3
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
I build a shared library (mapserver) which functions i can use in java.
Using this library within a normal jdk1.4 works without problems.
Calling functions using Tomcat 3.3a works well too. No problems occur.
Using Tomcat 4.0.1/4.0.3 the server crashes with error messages attached
to this
I don't know if the Eclipse configuration allows you to
specify -Dprop=value in Tomcat's startup. If it does,
I think a lot of this can be done in Tomcat 3.3.1 using
parameter substitution. I have used in server.xml
Http10Connector port=${http.port} ... /
and included
Ok. Thanks Costin. What I'll keep in mind is that it is complex ... ;-)
-Vincent
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 08 February 2002 00:28
To: Tomcat Developers List
Subject: RE: Tomcat 3.3 - Cactus Issue
On Thu, 7 Feb 2002, Vincent Massol
On Fri, 8 Feb 2002, GOMEZ Henri wrote:
Date: Fri, 8 Feb 2002 09:31:44 +0100
From: GOMEZ Henri [EMAIL PROTECTED]
Reply-To: Tomcat Developers List [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Subject: RE: Tomcat 3.3 and 4.x tuning via command line
I don't know
I'm wondering whether we really need to build it in to Tomcat itself,
though. Can't you accomplish the same thing by using a little
Ant script
and run a filter or replace task? All this would require
is packaging
ant.jar along with Tomcat, or requiring users that need the facility to
download
On Fri, 8 Feb 2002, GOMEZ Henri wrote:
Date: Fri, 8 Feb 2002 18:10:57 +0100
From: GOMEZ Henri [EMAIL PROTECTED]
Reply-To: Tomcat Developers List [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Subject: RE: Tomcat 3.3 and 4.x tuning via command line
I'm wondering whether
On Fri, 8 Feb 2002, Craig R. McClanahan wrote:
target name=generate description=Generate customized server.xml
replace file=server.xml token=@port@ value=${port}
/target
/project
In your template server.xml, you'd have a Connector element like this:
Connector ...
There's a lot of power in what the replace task can do.
Here's a very
simple one that replaces the string @port@ with the port number
specified by the port property:
project name=Create server.xml default=generate
target name=generate description=Generate customized
server.xml
Hi to all,
You should all know that there is a very good Tomcat 3.3/4.0
plugin for the OSS IDE eclipse (www.eclipse.org), available
at http://www.sysdeo.com/eclipse/.
This plugin allow eclipse developper to launch Tomcat from
the IDE, stop, restart and configure many parameters like
tomcat_home
=8080
in the startup command to make server.xml runtime
configurable. Would this approach work for you?
If so, perhaps it would desirable to add this feature
to Tomcat 4.x.
Unfortunately the parameter substitution is broken
in Tomcat 3.3 so you would need 3.3.1 to try this
out.
Cheers,
Larry
the parameter substitution is broken
in Tomcat 3.3 so you would need 3.3.1 to try this
out.
Where could I take more information on these feature in
3.3.1 ?
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
]]
Sent: 05 February 2002 19:46
To: Tomcat Developers List
Subject: RE: Tomcat 3.3 - Cactus Issue
On Tue, 5 Feb 2002, Larry Isaacs wrote:
I looked for this and didn't find that there was any POST data
sent and none was read. I certainly could have missed something.
I don't completely
Costin,
See inline
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 05 February 2002 19:08
To: Tomcat Developers List
Subject: Re: Tomcat 3.3 - Cactus Issue
On Tue, 5 Feb 2002 [EMAIL PROTECTED] wrote:
Most of the time it happens when something
It is described in the Variable substitution section
near the top of the serverxml.html document.
http://jakarta.apache.org/tomcat/tomcat-3.3-doc/serverxml.html
Cheers,
Larry
-Original Message-
From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 07, 2002 7:53 AM
-
From: Vincent Massol [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 07, 2002 8:09 AM
To: 'Tomcat Developers List'
Subject: RE: Tomcat 3.3 - Cactus Issue
Sorry guys for not jumping in earlier.
Here is some more information on how Cactus works and what it does.
Background info
-Original Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: 07 February 2002 14:16
To: 'Tomcat Developers List'
Subject: RE: Tomcat 3.3 - Cactus Issue
For the testPostMethod test, can you point me to where in
Cactus, the POST data is added/generated and where
where POST data is
added as part of the client handling for this test?
Cheers,
Larry
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 07, 2002 10:15 AM
To: 'Tomcat Developers List'
Subject: RE: Tomcat 3.3 - Cactus Issue
-Original
(queryString.toString());
out.close();
-Vincent
-Original Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: 07 February 2002 15:43
To: Tomcat Developers List
Subject: RE: Tomcat 3.3 - Cactus Issue
Thanks for the info. However, I never found where
testPostMethod was using any
On Thu, 7 Feb 2002, GOMEZ Henri wrote:
Date: Thu, 7 Feb 2002 09:28:01 +0100
From: GOMEZ Henri [EMAIL PROTECTED]
Reply-To: Tomcat Developers List [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Subject: Tomcat 3.3 and 4.x tuning via command line
Hi to all,
You should all
On Thu, 7 Feb 2002, Vincent Massol wrote:
The particularity of testPostMethod is that it sends information both in
the URL (as parameters) and in the request BODY in POST form.
Thus, there is some POST data sent !
Ok, then what really matters is who reads the body and how.
Sorry for not
On Thu, 7 Feb 2002, Larry Isaacs wrote:
Date: Thu, 7 Feb 2002 07:40:21 -0500
From: Larry Isaacs [EMAIL PROTECTED]
Reply-To: Tomcat Developers List [EMAIL PROTECTED]
To: 'Tomcat Developers List' [EMAIL PROTECTED]
Subject: RE: Tomcat 3.3 and 4.x tuning via command line
I don't know
It appears, for example, that the only thing you can override about a
connector is which port it's on. What happens if you want to override,
say, the maximum number of connections that your connector will accept
(the maxProcessors parameter on Tomcat 4's HttpConnector)?
Right +1 for you here
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 07, 2002 12:06 PM
To: Tomcat Developers List
Subject: RE: Tomcat 3.3 - Cactus Issue
On Thu, 7 Feb 2002, Vincent Massol wrote:
The particularity of testPostMethod is that it sends
9:05 AM
Subject: RE: Tomcat 3.3 - Cactus Issue
On Thu, 7 Feb 2002, Vincent Massol wrote:
The particularity of testPostMethod is that it sends information both in
the URL (as parameters) and in the request BODY in POST form.
Thus, there is some POST data sent !
Ok, then what really
both in the URL _and_ in the body as POST data ?
Thanks a lot
-Vincent
-Original Message-
From: Bill Barker [mailto:[EMAIL PROTECTED]]
Sent: 07 February 2002 21:38
To: Tomcat Developers List
Subject: Re: Tomcat 3.3 - Cactus Issue
I've found an XP machine to try this on, and can
Many thanks for finding this. Not suprisingly Costin's
initial guess was correct. Fortunately I wasn't wrong
about one assumption, which was the reason for the failure
was that Tomcat 3.3 was too fast. Thanks again, to Costin.
I'll see about moving the yielding logic tonight and then
tag
On Thu, 7 Feb 2002, Vincent Massol wrote:
Are you saying that the logic in Tomcat is that prior to closing a
socket, all data is read first ?
No, tomcat will just try to flush it's input buffers.
We don't want to read all data - the servlet is supposed to
process the request and decide if it
See inline.
- Original Message -
From: Vincent Massol [EMAIL PROTECTED]
To: 'Tomcat Developers List' [EMAIL PROTECTED]
Sent: Thursday, February 07, 2002 1:57 PM
Subject: RE: Tomcat 3.3 - Cactus Issue
Hey thanks guys ! You're too fast for me ... I'm trying to catch up with
the emails
On Thu, 7 Feb 2002, Larry Isaacs wrote:
Many thanks for finding this. Not suprisingly Costin's
initial guess was correct. Fortunately I wasn't wrong
about one assumption, which was the reason for the failure
was that Tomcat 3.3 was too fast. Thanks again, to Costin.
Well, given
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 07 February 2002 22:47
To: Tomcat Developers List
Subject: RE: Tomcat 3.3 - Cactus Issue
On Thu, 7 Feb 2002, Larry Isaacs wrote:
Many thanks for finding this. Not suprisingly Costin's
initial guess was correct. Fortunately I wasn't
On Thu, 7 Feb 2002, Vincent Massol wrote:
Last thing I'd like to confirm : When data is sent over a socket, it
will fill the socket buffer (at the client side) and then sending of
data will block until the server side reads from the socket buffer ? If
The first part - I'm not sure. I expect
Hi Bill,
Here are the details of the problem with Tomcat 3.3 and Cactus.
Apparently, Cactus's sample test suite run against Tomcat 3.3 will
occasionally fail on the main Gump system (a 300Mhz system running
Linux) and reliably fails Vincent Massol's laptop (1Gig+ system
running Windows XP
with Tomcat 3.3 and Cactus.
Apparently, Cactus's sample test suite run against Tomcat 3.3 will
occasionally fail on the main Gump system (a 300Mhz system running
Linux) and reliably fails Vincent Massol's laptop (1Gig+ system
running Windows XP). The failure is the same for both
Comments below.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 05, 2002 12:45 PM
To: Tomcat Developers List
Subject: Re: Tomcat 3.3 - Cactus Issue
Hi Larry,
We had a similar problem long time ago - with the POST and the extra
On Tue, 5 Feb 2002 [EMAIL PROTECTED] wrote:
Most of the time it happens when something is still in the write
buffer ( i.e. unsent or unread ), and the remote side is closing
the connection.
I'll try again:
Assuming CLIENT sending data to SERVER. The exception happens when:
- server has
Vincent: is your test servlet reading the body i.e. calls
getParameters() if it's a url-encoded body, or read
the full stream ?
If not, I believe the current behavior is correct and shouldn't
be changed - it signals the CLIENT that whatever it posted
was not read, and that's a very
Larry,
See below.
-Original Message-
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: 05 February 2002 19:03
To: 'Tomcat Developers List'
Subject: RE: Tomcat 3.3 - Cactus Issue
Comments below.
[snip]
Let me know if that helps - and if not what's the easiest way
On Tue, 5 Feb 2002, Larry Isaacs wrote:
I looked for this and didn't find that there was any POST data
sent and none was read. I certainly could have missed something.
I don't completely understand everything that Cactus' controller
servlet does on the Tomcat side. However, I think I
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 05, 2002 2:46 PM
To: Tomcat Developers List
Subject: RE: Tomcat 3.3 - Cactus Issue
On Tue, 5 Feb 2002, Larry Isaacs wrote:
One question - with the sleep(), do you do an isAvailable
-
From: Larry Isaacs
Sent: Tue 2/5/2002 2:56 PM
To: 'Tomcat Developers List'
Cc:
Subject: RE: Tomcat 3.3 - Cactus Issue
-Original Message-
From: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 05, 2002 2:46 PM
To: Tomcat Developers
On Tue, 5 Feb 2002, Larry Isaacs wrote:
I tried adding a Thread.sleep(1) just before the call to
TcpConnection.shutdownInput() in Http10Interceptor.
A System.out.println() within shutdownInput's while
never prints during a successful Cactus run on Win2k.
Is there anything different I should
/show_bug.cgi?id=4600
Tomcat 3.3 redirect behavior differs from Tomcat 3.2
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
May i know when the production release for this fix is in schedule.
Thanks and Regards
Jayakumar
-Original Message-
From: Martin van den Bemt [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 31, 2002 2:25 PM
To: Tomcat Users List
Subject: RE: Tomcat 3.3 getRemoteHost always returns
See my reply on tomcat-user.
Cheers,
Larry
-Original Message-
From: Jayakumar Duraisamy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 31, 2002 3:04 PM
To: [EMAIL PROTECTED]
Subject: FW: Tomcat 3.3 getRemoteHost always returns localHost - Is
there any 3.3 production version
..., or perhaps a taglib TLD
file, would cause something like this.
Cheers,
Larry
-Original Message-
From: Renato [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 30, 2002 11:15 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Strange Tomcat 3.3 error
Hi all,
Sometimes, when I
Hi all,
Sometimes, when I start my Tomcat 3.3 + Apache ( nightly build 0 I have the
following error:
.
/web.xml - java.net.NoRouteToHostException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect
/show_bug.cgi?id=5411
JSP session does not work with IE/IIS5/Tomcat 3.3
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Hi ppl:
I'm running Apache 1.3.22 + Tomcat 3.3 + Cocoon 1.8.2 on a Solaris
x86 2.8 box (with Sun JDK 1.2), and I'm in trouble. When I thought all
was working ok I realized that with some applications my Tomcat
crashes!! This happens after receiving several errors (see attached
log). Any help
Medina wrote:
Hi ppl:
I'm running Apache 1.3.22 + Tomcat 3.3 + Cocoon 1.8.2 on a Solaris
x86 2.8 box (with Sun JDK 1.2), and I'm in trouble. When I thought all
was working ok I realized that with some applications my Tomcat
crashes!! This happens after receiving several errors (see attached
Hello.
I can't run Tomcat 3.3 with SSL on Red Hat Linux 7.0
I make key with keytool, then add
Http10Connector
port=8443
secure=true
keystore=/var/tomcat/conf/keystore
keypass=mynewpass
clientAuth=false /
in server.xml
Then I start tomcat. And he doesn't work!
--
Best
A denial-of-service vulnerability was recently discovered
affecting Tomcat 3.3 running on Windows systems. A special
HTTP request can cause the request to hang and never complete.
This prevents the thread handling the request from handling
any further requests until Tomcat is restarted. Other
I still plan to release the jakarta-tomcat HEAD as 3.3.1.
3.3a will be the original 3.3 source with just enough changes
to avoid the DOS problem. This is for those who require
a validated version of Tomcat 3.3 and can't just switch
to a new version. Hopefully the minimal changes will make
Sounds very good to me. Thanks.
Bojan
Larry Isaacs wrote:
I still plan to release the jakarta-tomcat HEAD as 3.3.1.
3.3a will be the original 3.3 source with just enough changes
to avoid the DOS problem. This is for those who require
a validated version of Tomcat 3.3 and can't just switch
to have for Tomcat 3.3
a faster release rate than it was for 3.2, since
everybody agree that 3.3.1 is just 3.3 + bug fixes
and that added features (SSLSessionID/STM) could
(should) be desactivated in default configuration.
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands
rather not leave Tomcat 3.3 with the
aux.jsp DOS problem for that duration. I propose to add
to the site an updated tomcat_util.jar and tomcat_modules.jar
that fix the problem based the changes used in Tomcat 3.3.1.
The updated source files would be made available as well
on the site. Following
things quickly is not my forte and the earliest I could
do a 3.3.1-beta1 would be the following weekend, i.e.
the weekend of the 20th.
In addition, I would rather not leave Tomcat 3.3 with the
aux.jsp DOS problem for that duration. I propose to add
to the site an updated tomcat_util.jar
[EMAIL PROTECTED] wrote:
So far the changes in 3.3 tree were only bug fixes and
what I've seen so far was pretty clear and simple -
I think the head of 3.3 is as good or better than 3.3.0.
There were a few new features as well (at least STM pooling and
SSLSessionID checks), but they should
it won't be possible to fetch the patched 3.3 from
CVS using a tag or branch, I'm reluctant to give it a normal
version number. 3.3a seems like a reasonable alternative.
I'll provide full tar.gzs and zips in addition to jars to update
an existing Tomcat 3.3 installation.
Cheers,
Larry
-Original
- Original Message -
From: Bojan Smojver [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Wednesday, January 09, 2002 5:26 PM
Subject: Re: Dealing with the Tomcat 3.3 aux.jsp DOS problem and a Tomcat
3. 3.1 release
[EMAIL PROTECTED] wrote:
So far the changes
Larry Isaacs wrote:
Since it won't be possible to fetch the patched 3.3 from
CVS using a tag or branch, I'm reluctant to give it a normal
version number. 3.3a seems like a reasonable alternative.
I'll provide full tar.gzs and zips in addition to jars to update
an existing Tomcat 3.3
Hi all,
What happened to methods getRemoteAddr, getServerName, getServletPath in
the Request class for Tomcat 3.3 ?
I had an Interceptor written for Tomcat 3.2 that uses these methods within
the Request. How can I access internal servlet information from Request int
Tomcat 3.3 ?
Thanks
Just found it... they change names... ( silly me :)) )
On Wed Dec 19 11:54:57 2001, Renato [EMAIL PROTECTED]
escreveu :
Hi all,
What happened to methods getRemoteAddr, getServerName, getServletPath in
the Request class for Tomcat 3.3 ?
I had an Interceptor written for Tomcat 3.2
Message -
From: Renato [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, December 18, 2001 6:27 PM
Subject: Re: Tomcat 3.3 deployment - last minute problem
Hi all,
I'm investigating this problem and may found something. The html that is
pushed to my browser
to dig
through the code.
- Original Message -
From: Renato [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, December 18, 2001 6:27 PM
Subject: Re: Tomcat 3.3 deployment - last minute problem
Hi all,
I'm investigating this problem and may found something
Hi Bill,
Thanks for the help.
I found out the problem. It was jikes. I was using jikes in the
JspInterceptor and somewhat it wasn't working.
Now, I will upgrade all my user base to Tomcat 3.3 :))
Renato.
On Tue, 18 Dec 2001 14:29:24 -0800, Bill Barker [EMAIL PROTECTED]
escreveu
/show_bug.cgi?id=5353
Characters with accents not displayed correctly in Tomcat 3.3
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|REOPENED|RESOLVED
As I tested, Tomcat 3.3 runs much faster than 3.2.3
(for both JSP and Servlet requests). What changes are
the main factors of this performance improvement? Thanks.
__
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your
Hi,
This is what I'm using:
%@ page contentType=text/html; charset=ISO-8859-1 %
I saw the servlet generated in the work directory and it actually write the
response.setContentType(text/html;charset=ISO-8859-1)
( default type in server.xml is set to ISO-8859-1 too )
How can I know the
Hi all,
I have one last problem that prevents me from upgrading a big user base
from Tomcat 3.2.4 to Tomcat 3.3 ( which will be the last nightly build ).
*** HTML pages with latin characters don't display correctly on Linux ***
( JSP file with: )
Ex: páéíóú/p
I'm not quite sure if it's
On Fri, 14 Dec 2001, Renato wrote:
*** HTML pages with latin characters don't display correctly on Linux ***
( JSP file with: )
Ex: páéíóú/p
It's maybe a problem with the locale variables on my Linux, which I don't
quite understand ( tried LC_ALL, LANG, LC_CTYPE and it didn't work ) or
in Tomcat 3.3
Dear Tomcat 3.3 committers,
The atached two patches resolve character corruption problems when
Tomcat 3.3 lists directories or displays an error message in
non-ISO-8859-1 environments.
And I created Japanese resource bundles for Tomcat 3.3 according to
Henri Gomez's advice (Note
/show_bug.cgi?id=5411
JSP session does not work with IE/IIS5/Tomcat 3.3
Summary: JSP session does not work with IE/IIS5/Tomcat 3.3
Product: Tomcat 3
Version: 3.3 Final
Platform: PC
URL: http://www.warf.ws/admin/
OS/Version: Windows NT/2K
/show_bug.cgi?id=5353
Characters with accents not displayed correctly in Tomcat 3.3
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
1 - 100 of 370 matches
Mail list logo
