A few weeks back I noticed this problem when I upgraded from 4.1.12 to
4.1.17. I wanted to track it down a little bit before reporting it, and now
I think I know where the problem is. I have isolated the problem to changes
made between CVS versions 1.12 and 1.14 of
Thanks for the patch. It seems to fix the problem on my machine. It seems
that since this is a known problem with 4.1.17, that build should be marked
as bad and not as the 'stable' release. I think other people will be having
this problem . . .
-Original Message-
From: [EMAIL PROTECTED]
I have been trying out 4.1.17 in my development environment and it is giving
me much grief. When I first start the server everything works fine, but
after hitting my webapp a few times (say 10 to 20 times) it starts returning
blank pages. I have tried turning on all the logging I can to no avail.
To: Tomcat Users List
Subject: RE: 4.1.17 Problems - Possibly Coyote Connector?
if you could, can you gander at the message thread with the subject Tomcat
4.1.x and SocketException
and see if this is perhaps a related issue?
-Original Message-
From: Matt Small [mailto:[EMAIL PROTECTED
at the message thread with the subject Tomcat
4.1.x and SocketException
and see if this is perhaps a related issue?
-Original Message-
From: Matt Small [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 2:45 PM
To: Tomcat (E-mail)
Subject: 4.1.17 Problems - Possibly Coyote
it in
bugzilla?
Thanks
Matt
-Original Message-
From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 11, 2002 4:12 PM
To: Matt Small
Cc: [EMAIL PROTECTED]
Subject: Tomcat 4.0.2 - Startup fails after moving xerces.xml from
/common/lib to /server/lib
In xerces 2.0.0 the SAX
Thanks for the clarification. As long as xerces 1.4 in /common/lib can
coexist with Xerces 2 in a webapp that seems ok.
Next time I'll try to be a little more verbose in my bug reports.
Matt
-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 11,
I just upgraded from Tomcat 3.3 to 4.0.1 and it looks like there has been a
behavior change in the Classloaders that is breaking me.
At runtime I dynamically generate, compile and then load classes. I compile
the classes into the /webapp/WEB-INF/classes directory so that I dont have
to worry
That makes sense, I actually first try to load the class, and if it fails I
then generate class and try loading again. Basically I dont want to have to
generate all the time because the overhead is so high.
Is this something you will fix in 4.0.2?
Matt
-Original Message-
From: Remy
.
In the meantime, the simplest way to add your class to Tomcat 3.3
is to put it in a jar and put that jar in the tomcat/lib/container
directory. This will get your class into the correct classloader.
Cheers,
Larry
-Original Message-
From: Matt Small [mailto:[EMAIL PROTECTED]]
Sent: Monday
Take a look at www.bitmechanic.com
-Original Message-
From: Alexandre Victoor [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 11, 2001 7:49 AM
To: [EMAIL PROTECTED]
Subject: Database pool
Hello,
This is perhaps off-topic, I am looking for an open-source database
connection pool.
I have my tomcat server set up with two contexts that share the same web-app
directory. I want to specify a different web.xml in each context though so
that different servlets are available from each context. Is there any way to
specify the web.xml file name or path from the context definition?
of web.xml is mandated by the Servlet 2.2 spec, so there
isn't supposed to be a way to do what you want. However,you are
welcome to try customizing org.apache.tomcat.facade.WebXmlReader
to make a choice somehow.
Cheers,
Larry
-Original Message-
From: Matt Small [mailto:[EMAIL PROTECTED
13 matches
Mail list logo
