On 10/15/2012 08:50 AM, Paul Libbrecht wrote:

Le 15 oct. 2012 à 14:47, Vincent Massol a écrit :

"Caused by: java.sql.SQLException: Out of Memory"

Try increasing the memory you give to java.

And... migrating to MySQL, Derby, or some other DB which is not memory based!!


The problem is that you're still using the default HSQLDB database, with the default configuration, which is optimized for small trial usages. All the data is kept in memory for fast access, so the memory that is allocated to the process needs to get larger as you add more data to the wiki.

First step to get your wiki started is to increase the memory: in start_xwiki.bat, search for a line similar to:

set XWIKI_OPTS=-Xmx512m -XX:MaxPermSize=128m

Change the -Xmx value to something bigger, like 1024m, and restart XWiki.

Second step is to either switch to a different database engine, or to configure HSQLDB to use a cached table mode, where it loads only a small portion of the database in memory.

On Oct 15, 2012, at 2:44 PM, Higginson Ian (WIRRAL PCT) <ian.higgin...@nhs.net> 

I feel really stupid for not attaching the log, haha! I've pasted what I get 
when we try to access the wiki; nothing has been changed AFAIK since the last 
time it worked:


Problem accessing /xwiki/bin/view/Main/. Reason:
org.apache.commons.dbcp.SQLNestedException: Cannot create 
PoolableConnectionFactory (Out of Memory)

-----Original Message-----
From: users-boun...@xwiki.org [mailto:users-boun...@xwiki.org] On Behalf Of 
Paul Libbrecht
Sent: 15 October 2012 13:39
To: XWiki Users
Subject: Re: [xwiki-users] Retrieving data


error 500 means internal error.
It could really be just about anything.

Some parts of the log are needed I think.


Le 15 oct. 2012 à 14:17, Higginson Ian (WIRRAL PCT) a écrit :


After a few successful months using XWiki it's finally decided to die on me 
(error 500, etc.) and I can't seem to get it back up and running. Is there any 
way I can extract the attachments that I had in the wiki manually at all?

Many thanks,

Sergiu Dumitriu
users mailing list

Reply via email to