Well, I did set the check for updates interval to 10h. But I also noticed
delays when doing things like searching with lucene for the first time which
loads a bunch of stuff into memory. My first hunch was that weblogic has it's
own classloader or does it's own memory management or something.
Dan Adams
Principal Software Engineer
Interactive Factory
p: 617.235.5857
- Original Message -
From: Howard Lewis Ship [EMAIL PROTECTED]
To: Tapestry users users@tapestry.apache.org
Sent: Thursday, October 30, 2008 9:21:14 PM (GMT-0500) America/New_York
Subject: Re: Anyone using weblogic?
I bet it is about scanning the classpath for component classes. I
don't know if there's a way to speed that up.
On Thu, Oct 30, 2008 at 12:45 PM, Dan Adams [EMAIL PROTECTED] wrote:
One thing I've noticed about weblogic is that the startup time when deploying
the application is insanely long and this is not true of when run in Jetty.
Anyone run into this or gotten around it?
Dan Adams
Principal Software Engineer
Interactive Factory
p: 617.235.5857
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
-
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]