Sorry again Sergiu,
Thanks for pointing out the perm gen.
I fixed the problem by adding the following command line switches:
-XX:MaxPermSize=128M -XX:+CMSClassUnloadingEnabled
-XX:+CMSPermGenSweepingEnabled
I also set my heap size bzck down to 512M.
Thanks,
Neil
On 10 Jul 2011 08:13, "Neil Crow" <crowneil(a)gmail.com> wrote:
Sorry Dumitriu,
You are absolutely correct.
I was typing from my memory and not looking at the screen.
It is permgen.
In process explorer (sysinternals) I was seeing the java process,
underneath
the service exe process had 2Gb allocated.
Neil.
On 9 Jul 2011 17:56, "Sergiu Dumitriu" <sergiu(a)xwiki.com> wrote:
On 07/08/2011 01:29 PM, Neil Crow wrote:
> Hi,
>
> I recently set up a new XWiki instance, on a windows server, hosted in
Jetty
> with the Database on Oracle 11g.
> After starting the server there was a "blank wiki shell", I was prompted
to
>> install the Enterprise xar which I did.
>>
>> It seemed to install correctly, I could create a user and log in etc.
>>
>> But I keep on experiencing heap size errors.
>>
>> I reached the point where I had allocated 2Gb memory, and it is still
>> freezing up with heap errors.
>> Has anyone experienced the same and managed to solve it, or got any
ideas
> on
>>> how to isolate the problem?
>>>
>>> My configs are as follows:
>>> Java 6 64 bit
>>> Windows 2000 Server
>>> Jetty 7
>>> Wrapped as a service with apache-commons-daemon (procrun).
>>
>> Are you sure it is heap memory, and not PermGen?
>>
>> Are you sure the memory setting is taken into account, or is it passed
>> to the wrong script that doesn't forward it to the Jetty process?
>> Normally 500M should be enough for running XWiki without problems.