As usual, whenever I post a question I seem to almost immediately find
some more information.
I'm looking into these posts, which will hopefully give me some
direction. If anybody has other posts that may offer more information,
I'm all ears.
pageId=2669
Thanks,
Josh
Message
From: Gormley, Josh
Sent: Thursday, September 14, 2006 12:08 PM
To: users (AT) tomcat (DOT) apache.org
Subject: undeploy doesn't completely remove classes from memory
Hello,
I've got a problem with several of the Struts apps that I'm deploying to
Tomcat 5.5.17. If I redeploy the app by dropping in a new war file, I
almost always have to restart tomcat in order to see the updated classes
take affect. I've read that this could be caused by threads being left
open and not garbage collected properly or by using Singletons, or
several other things, but I'm having a hard time tracking down the root
of the problem.
What's the best way to get to the root of this problem? Are there any
known issues with Struts, Hibernate, SQLjdbc that could be causing this?
I've tried JProfiler, but I'm having a hard time seeing orphaned object
instances after an undeploy. I would much appreciate any suggestions
that you might have.
Thanks,
Josh Gormley
Server config:
Redhat
Tomcat 5.5.17
JRE 1.4.2 with the necessary classes to allow it to work with Tomcat 5.5
App info
Struts
Hibernate
SQLjdbc
Segment from server.xml:
<Host name="www.xyz.com"
appBase="webapps/xyz"
unpackWARs="true"
autoDeploy="true"
xmlValidation="false"

>
<Context path="" docBase="" debug="0" >
<Resource name="jdbc" scope="Shareable"
type="javax.sql.DataSource" />
<ResourceParams name="jdbc">