Let me point out that install task only takes the url of the webapps you
want to copy.
As a result, it would try to refer to your original location in your
case /home/delprete/samples/build ,where you may
have delete the war.
Check if you still have the war (or war content ) in
the outofmemory error.
saurabh
[EMAIL PROTECTED] 01/04/03 01:12AM
On Fri, 3 Jan 2003, Saurabh Arora wrote:
Date: Fri, 03 Jan 2003 02:33:17 -0700
From: Saurabh Arora [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: Memory Usage and Garbage
Just wanted to know, does the current implementation of tomcat 4.1.18
also has the same problem of keeping the jsp's
in memory. or it was only present in 4.0.4
saurabh
[EMAIL PROTECTED] 01/03/03 02:26PM
Hi Craig,
please see intermixed.
On 2 Jan 2003 at 18:18, Craig R. McClanahan wrote:
I would like to know that can we use JAXP 1.2 XML parser with tomcat
4.1.17 (by replacing common\endorsed. The release notes point out use of
JAXP 1.1 parser.
I would also like to know why is JAXP 1.2 XML parser is not bundled
with tomcat 4.1.17.
with regards
saurabh
--
To unsubscribe,
I am using 1.4.1 , can i put JAXP 1.2 jars in the common\endorsed
[EMAIL PROTECTED] 12/19/02 12:17PM
Saurabh Arora [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
I would like to know that can we use JAXP 1.2 XML parser with tomcat
4.1.17 (by r
Since you seem to using it in a production system, why donot you precompile the JSP's
into classes using ant's jspc and javac task.
In this way, you can remove runtime compilation, and then see if the problem is with
your application or javac.
saurabh
[EMAIL PROTECTED] 12/17/02 06:15AM
We had also faced a similar problem in a project. We are currently working on a
prototype for loading
a specific version of xerces.jar (which is compatible with our application) , using
the InternalclassLoader.
You can try to write your own code for the same, write your own classloader,
of Xerces.jar
in the ClassLoader HOWTO is wrong.
Why are we forcing users to use only the common\lib \ xerces implementations.
Saurabh arora
--
To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
be filtering the org.apache.xerces package.
It means the documentation that , Application can use specific version of Xerces.jar
in the ClassLoader HOWTO is wrong.
Why are we forcing users to use only the common\lib \ xerces implementations.
Saurabh arora
--
To unsubscribe, e-mail
