Slow startup with James 2.1a1 CVS build

[Eric Weidner <es...@pumavision.net>]

Setup info:
Red Hat 7.3
JDK 1.4.1-rc
DB repositorys on MySQL 4.0.2

I've been running a CVS version of James 2.1a1 from about August 1 for a 
while.  A few days ago I upgraded to the latest CVS again.  The startup 
time for James has increased by about 5X +.  It still starts ok and runs 
fine, it just takes forever.  I did move from MySQL 3.23.51 to 4.0.2 at 
the same time if that might have something to do with it.

Is there a reason for this?  Maybe a problem in startup?

Thanks,

Eric



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: Slow startup with James 2.1a1 CVS build

["Noel J. Bergman" <no...@devtech.com>]

Eric,

I noticed a major slowdown at startup, too.  I'm not sure where to attribute
the delay.  Perhaps to Phoenix.  That is my best guess at the moment, based
solely upon when I start James, and when the James logs start getting
written.  Once the James logs start getting written, things move along
rather quickly, which is why I'm leaning towards Phoenix.

Perhaps one of the Avalon Phoenix guys can give us a clue.

	--- Noel


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>