Re: Problem with AJP 1.3 Connector

[Sven Köhler <sk...@upb.de>]

> Thanks for that response. This is the typcial client setup what we have. Now the worse part of this is, Apache is just doing a request management. All the actual process is done in Tomcat only. Can you please let me know how do we switch on the incremental garbage collector on??


If you're using Linux, you surely have a startup-script for tomcat, 
don't you?

the command
   export JAVA_OPTS="-Xmx256m -Xincgc"
before calling catalina.sh is a good way to do it. you should already 
have rised the max heapsize of the java-vm with the -Xmx option.

If you're using Windows, you have to dive into the registry, and add the 
parameters to the tomcat-service.



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4)

[neal <ne...@yahoo.com>]

Hmm ... I'm wondering how this is going to affect the x-platform-ness of my
application now.

I'm developing on a windows platform and deploying to linux, wherein my
paths actually *should* start with a "/".


UUugh.


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4)

[neal <ne...@yahoo.com>]

Hmm ... it appears that for some F***'ed up reason, that the URL created by
using his.getClass().getResource() is no longer acceptable for TRAX when
using Tomcat 4.1.18, as compared to Tomcat 4.0.4.

The problem is that the URI begins with a "/". If I remove that leading "/"
suddenly the URLs are acceptable in Tomcat 4.1.18.

Why would Tomcat be involving itself in such issues?  Only thing I can think
of is that maybe the conditions for this Apache Exception were redefined in
4.1.18:

org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI

Neal

-----Original Message-----
From: neal [mailto:nealcabage@yahoo.com]
Sent: Saturday, March 01, 2003 11:02 AM
To: Tomcat Users List
Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4)


I ported my app from Tomcat 4.0.4 (Windows) to Tomcat 4.1.18 (Windows) and
now it doesn't work!  It appears that I have a problem now with parsing my
conf.xml file in my initServlet.

I noticed that the new Tomcat has an "endorsed" directory with a different
copy of Xerces in it.  Is this somehow related?

Here's the error:
javax.xml.transform.TransformerException:
org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI


Thanks.
Neal


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4)

[neal <ne...@yahoo.com>]

I ported my app from Tomcat 4.0.4 (Windows) to Tomcat 4.1.18 (Windows) and
now it doesn't work!  It appears that I have a problem now with parsing my
conf.xml file in my initServlet.

I noticed that the new Tomcat has an "endorsed" directory with a different
copy of Xerces in it.  Is this somehow related?

Here's the error:
javax.xml.transform.TransformerException:
org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI


Thanks.
Neal


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org