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 would recommend changing the WIKI to read: > Step 2.5 : Move the objectstore: The <objectstorage> element is no > longer used. Instead move all of its <repository> elements into the > <repositories> section of the <mailstore> block. > > DK > > On Dec 12, 2007, at 12:19 AM, Stefano Bagnara wrote: > >> Dain Kaplan ha scritto: >>>> I also see a problem in your mailstore XML configuration: please take a >>>> look at the james original config.xml <mailstore> item. You should copy >>>> it as-is in your configuration file. The way you mixed the >>>> objectstorage >>>> inside the mailstore is not ok. >>> >>> >>> Ah, perhaps this is it. In the upgrade document, it only says: >>> >>> Step 2.5 : Move the objectstore >>> Move the objectstore config into the mailstore config. >>> >>> But perhaps I should have been more careful. The <objectstore> element >>> is no longer present in the default configuration file, I take it it no >>> longer exists at all, and the repositories within should be moved, not >>> the element itself? The upgrade instructions are slightly ambiguous, >>> perhaps the WIKI should be updated to more emphatically explain the >>> migration of these repositories? >> >> Use the whole mailstore configuration from 2.3.1 to be sure it is ok. >> Let us know if this fixes your issue. >> >> Yes, the upgrade document could be less ambiguous. Feel free to submit >> your proposed changes once you successfully get your upgrade to work. >> >> Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
