Possible custom tag incompatibility between 4.1.27 and 4.0.3

[Ely Eshel <el...@acm.org>]

Hi!
I developed a custom tag on Tomcat 4.1.27 and tried to deploy it on 4.0.3.
I get the following error:
org.apache.jasper.JasperException: XML parsing error on file
/WEB-INF/tlds/testtaglib.tld: Internal Error: File
/javax/servlet/jsp/resources/web-jsptaglibrary_1_2.dtd not found

My web.xml entry is:
<taglib>
	<taglib-uri>/WEB-INF/tlds/testtaglib.tld</taglib-uri>
	<taglib-location>/WEB-INF/tlds/testtaglib.tld</taglib-location>
</taglib>

My testtaglib.tld file is:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE taglib
	PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.2//EN"
	"http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd">
<taglib>
	<tlib-version>1.0</tlib-version>
	<jsp-version>2.0</jsp-version>
	<short-name>testtaglibs</short-name>
	<uri>/WEB-INF/tlds/testtaglib.tld</uri>
	<tag>
	  <name>getWebServer</name>
	  <tag-class>
	     taglibs.testtaglib.GetWebServerTag
	  </tag-class>
	  <body-content>empty</body-content>
	</tag>
</taglib>

My taglib directive in the JSP is:
<%@ taglib prefix="testtag" uri="/WEB-INF/tlds/testtaglib.tld"%>

I am not sure that the problem is with Tomcat versions, but I cannot figure
out what else is wrong. I have no control over the 4.0.3 environment, so I
cannot experiment with it at all.
Thanks,
-- Ely



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

Garbage Collection issues

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

My Tomcat 4.1 (hosted on Linux) seems to have a problem in recent months
with crashing due to unavailable free RAM.  Specifically I get a
java.error.outOfMemory exception.  If check the RAM available
(Runtime.getRuntime().totalMemory()), I can see it ticking down through
the week.  If explicitly run garbage collection however my RAM totally
frees up and all is well (Runtime.getRuntime().gc();).

Why would this happen?  Surely this isn't due to a programming error on
my part, otherwise, the resources should automatically released whenever
the JRE performs periodic garbage collection. Isn't that correct?
Anyone have any theories as to what this may mean and what the best
solution would be?

Thanks.
Neal



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