Stefano Bagnara ha scritto: > Dain Kaplan ha scritto: >> Fixing the object store repository configuration format did not resolve >> the issue (i think), though James crashes with the message (this >> happened sporadically with 2.3.1 before fixing the configuration too): >> >> Exception in thread "CompilerThread1" java.lang.OutOfMemoryError: >> requested 32756 bytes for ChunkPool::allocate. Out of swap space? >> >> too often to really test anything. I saw in another thread that it is >> recommended to NOT adjust the min/max memory for the JVM, though we are >> doing it. Such settings worked fine with 2.2.0, should I be changing >> them? Before I added the setting to 2.3.1 it shut down on me for too >> little memory as well. The server is running 1.5.0_12-b04. There is >> also plenty of free space all around. > > what Xmx and Xms parameters are you using? Are you telling that an Xmx > that worked fine in 2.2.0 is making your 2.3.1 to run outofmemory (with > a different error than the swap space one?)? > > I read about the error above very often in this list > (ChunkPool::allocate). Each time I suggest to not use an Xmx too big for > the machine and to upgrade the jvm to the latest available. IIRC I never > received a feedback about the solution. > > Stefano
I forgot to tell that usually the "out of swap space" in the CompilerThread is caused by JVM hotspot bugs. You can try with newer or older JVM or you can try using the "-client" to skip most hotspot code that may hit the bug. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
