> I assume the Xms value is set to the same value as Xmx? > If not, at least earlier jdks tendered to through outofmemory > during heap resize.
I will give this a shot. Thanks. > The changes in Xmx values, did they had any impact on the duration > of the servers "good state" under load? Nope. This (along with the lack of memory growth over time) leads me to believe that it's not a normal memory leak, but more a poorly handled error case somewhere that sends us into a tailspin which eventually results in the OOME. (I've done a good bit of monitoring of the heap and things grow and shrink over time, and then seemingly out of the blue we'll see an OOME.) > How much memory does your machine have? 4G (currently each of the 5 tomcats has Xmx=256M, apache runs on the same machine) > I also assume you run 32 bit? yes > Your instances are all on the same machine? Why? Because that's the machine that we've got available right now ;) > Btw, can you reproduce the error in testing environment? > Could it be that you simply have a memory leak? For all my efforts I cannot reproduce the error on a staging machine. Though I wish I could... --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
