6 May
2009
6 May
'09
12:05 p.m.
Thanks,
I resolve my problem increasing limit size of java with the -Xmxsizem
parameter!
it was by default on -Xmx300m, and i need -Xmx600m.
In order to understand...i would like to know what is really loaded in
memory?
Xwiki need to load all the database in memory? all the pages with join
files? i thought one of interest of a database is to don't load all
information? Our base is still pretty small today, it means in one year we
will need 8Go of RAM? or we must change for Mysql?
Thank you for your help
Remi wrote:
Thank you for your answer, but i need explanations.
(0) Restart your container. And relaunch: What is the container? how? the
java ? uninstalling and reinstalling it?
(1) how to do? where can i manage theses settings?
Niels Mayer wrote:
--
View this message in context:
http://n2.nabble.com/Problem-with-HSQLDB-Database-please-Help%21%21-tp27921…
Sent from the XWiki- Users mailing list archive at Nabble.com.
On Tue, May 5, 2009 at 3:40 AM, Remi
<remi.pierrard(a)conseiltechno.com>wrote;wrote:
see in error message several lines with
"Cannot create
PoolableConnectionFactory (Out of Memory)" or "Caused by:
java.sql.SQLException: Out of Memory", but i need real help to
understand
and fix my problem.
(0) Restart your container. And relaunch. Check to see if this error is
still there:
Wrapped Exception: com.xpn.xwiki.XWikiException:
Error number 0 in 3:
Exception while hibernate execute Wrapped Exception: Could not create a
DBCP
pool. There is an error in the hibernate configuration file, please
review
If so, beg for additional assistance on list... (Does this error arise
from
an out of memory condition or indicate version mismatch between db and
software?).
Independently of that, eliminate out of memory error from possibilities:
(1) Increase the memory on your java process. I've been running a vhosted
1.8 system happily for over a month now, nonstop, with the following
settings (YMMV, I'm running two large apps in tomcat):
tomcat 2040 0.5 60.2 1835160 1230408 ? Sl Apr03 267:28
/usr/java/default/bin/java -server -Xms160m -Xmx1024m -XX:PermSize=160m
-XX:MaxPermSize=320m -Djavax.servlet.request.encoding=UTF-8
-Dfile.encoding=UTF-8 -DjavaEncoding=UTF-8 -Djava.awt.headless=true ...
Note the gargantuan 1.2g process size... but it just keeps running... It
always eventually reaches it's 1.2g (-Xmx1024m) limit but doesn't give
out
of memory errors.
(2) Check on additional customizations as needed. Increase fixed limits
in
your SQL connector, or in the db it itself? For example with
MySQL<http://platform.xwiki.org/xwiki/bin/view/AdminGuide/InstallationMy…
need to increase: "-- max_allowed_packet=32M" ...
(3) Look into logs more carefully, and run some of the queries that are
failing directly into your database. Potentially related, issues with
large
attachments:
http://n2.nabble.com/Bug-%3A-unable-to-delete-attached-files-in-virtual-wik…
http://n2.nabble.com/Hibernate-exception-when-trying-to-delete-attachment-t…
(4) Consult
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Performances
for additional tips on Process size, turning off Monitoring, changing
cache
size, etc.
Niels
http://nielsmayer.com
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users