Hivemind 1.1.1 is a must have for Tapestry 4.0. Anytime Tomcat detects a
changed .class file or .jar, it will discard a classloader that loaded
the app (provided reloadable is set to true). Hivemind 1.1 prevents
classloader from being unloaded. This is fixed in 1.1.1.
You should also use Tomcat 5.5.15. It finally fixes its classloader
handling of commons-logging + log4j.
Serge
Mike Snare wrote:
Unfortunately, the SVN version would be out of the question as our app
is production. It's not a huge deal since we won't be disabling the
cache during deployment, it's just a minor annoyance during
development.
I will take a look at using 1.1.1, though.
Thanks,
-Mike
On 3/21/06, James Carman <[EMAIL PROTECTED]> wrote:
I am not sure if it's the cause of it or not, as I'm not really familiar
with what Tapestry is doing "under the covers" (it's hard enough figuring
out all of the cool stuff HiveMind does). But, the details of the memory
leak can be found here:
http://issues.apache.org/jira/browse/HIVEMIND-161
I don't know if you need to use the current SVN version of Tapestry 4, as
Howard mentioned that there would need to be a Tapestry 4.0.1 to take
advantage of the memory leak fix. Jesse/Howard?
-----Original Message-----
From: Mike Snare [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 21, 2006 1:38 PM
To: Tapestry users
Subject: Re: Memory leak?
4.0, 1.1.
Was the memory leak in relation to this? The only major fix I was
aware of for 1.1.1 was the performance issue for threaded services.
-Mike
On 3/21/06, James Carman <[EMAIL PROTECTED]> wrote:
What version of Tapestry are you using? If it's 4.0, what version of
HiveMind are you using? There was a known memory leak in 1.1 which was
fixed in 1.1.1.
-----Original Message-----
From: Mike Snare [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 21, 2006 1:30 PM
To: Tapestry users
Subject: Memory leak?
I'm pretty sure there's a memory leak in tapestry because the memory
usage climbs and climbs when caching is disabled.
I understand that in a production environment you probably wouldn't
want caching disabled, but it seems tapestry should throw out whatever
it's creating if it's not going to use them. I don't think this is
happening.
-Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
