Geoff Howard wrote:
This is odd, as it would seem logically that restarting the webapp should reset all memory usage. There is of course some state which is persisted between startups but I'm most suspicious that this is a container issue.
- John, do you also use Tomcat? Which version do you both use?
4.1.12
A colleague with the same problem has 4.1.18.
- For a trial, do you get the same behavior deployed on Jetty? (either the bundled version or the full version from mortbay.org)
We haven't deployed it with Jetty, but the same colleague has the problem when it's deployed with JBoss/Tomcat.
- Are there any symptomatic errors in cocoon's or tomcat's logs?
Haven't noticed anything systematic. Usually I notice that Cocoon/Tomcat is getting very slow, and it ends with a 503 and java.lang.OutOfMemoryError.
- How do you restart?
Via Ant:
<target name="redeploy" depends="undeploy, deploy"/>
<target name="start.tomcat" depends="init">
<taskdef name="starttomcat" classname="com.oreilly.javaxp.tomcat.tasks.StartTomcatTask">
<classpath>
<path location="tomcat-tasks.jar"/>
</classpath>
</taskdef>
<starttomcat
testURL="http://${host}:${port}";
catalinaHome="${catalina.home}"
timeout="20000"/>
</target>
<target name="undeploy" depends="start.tomcat">
<taskdef name="remove" classname="org.apache.catalina.ant.RemoveTask">
<classpath>
<path location="${catalina.home}/server/lib/catalina-ant.jar"/>
</classpath>
</taskdef>
<remove
url="${url.manager}"
username="${manager.login}"
password="${manager.password}"
path="/${webapp.name}"/>
</target><target name="deploy" depends="start.tomcat">
<taskdef name="install" classname="org.apache.catalina.ant.InstallTask">
<classpath>
<path location="${catalina.home}/server/lib/catalina-ant.jar"/>
</classpath>
</taskdef>
<taskdef name="deploy" classname="org.apache.catalina.ant.DeployTask">
<classpath>
<path location="${catalina.home}/server/lib/catalina-ant.jar"/>
</classpath>
</taskdef>
<pathconvert dirsep="/" property="fullDir">
<path>
<pathelement location="${webapp.home}"/>
</path>
</pathconvert>
<echo>
deploy webapps directory:
jar:file://${fullDir}!/
</echo>
<install
url="${url.manager}"
username="${manager.login}"
password="${manager.password}"
path="/${webapp.name}"
war="jar:file://${fullDir}!/"/>
</target>- Which Cocoon blocks do you have installed?
Not sure exactly what the question means, but here's the list of jars from the Cocoon dist that we pack into our webapp:
<lib dir="${lib}/cocoon-2.1.3">
<include name="batik-all-1.5.jar"/>
<include name="avalon-framework-4.1.4.jar"/>
<include name="cocoon-2.1.3.jar"/>
<include name="commons-*.jar"/>
<exclude name="commons-logging-1.0.3.jar" />
<include name="excalibur-*.jar"/>
<exclude name="excalibur-logger-1.0.1.jar" />
<include name="fop-*.jar"/>
<include name="cocoon-fop-block.jar"/>
<include name="jakarta-regexp-1.3.jar"/>
<include name="pizza-1.1.jar"/>
<include name="resolver-20030708.jar"/>
<include name="util.concurrent-1.3.2.jar"/>
<include name="jisp-2.5.1.jar"/>
<include name="jdtcore-2.1.0.jar"/>
</lib>Hope the information helps. It's not really a major annoyance for us -- as I said, it only shows up when we redeploy frequently.
John
-- --------------------------------------------------------- Jentro Technologies GmbH John L. Webber, Software Development ---------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
