Re: [xwiki-users] Problem with HSQLDB Database please Help!!
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: On Tue, May 5, 2009 at 3:40 AM, Remi remi.pierr...@conseiltechno.comwrote: 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): tomcat2040 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 MySQLhttp://platform.xwiki.org/xwiki/bin/view/AdminGuide/InstallationMySQLyou 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-wikis-tp2434930p2440147.htmland http://n2.nabble.com/Hibernate-exception-when-trying-to-delete-attachment-tp2503343p2504053.html (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@xwiki.org http://lists.xwiki.org/mailman/listinfo/users -- View this message in context: http://n2.nabble.com/Problem-with-HSQLDB-Database-please-Help%21%21-tp2792184p2809260.html Sent from the XWiki- Users mailing list archive at Nabble.com. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Problem with HSQLDB Database please Help!!
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: On Tue, May 5, 2009 at 3:40 AM, Remi remi.pierr...@conseiltechno.comwrote: 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): tomcat2040 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 MySQLhttp://platform.xwiki.org/xwiki/bin/view/AdminGuide/InstallationMySQLyou 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-wikis-tp2434930p2440147.htmland http://n2.nabble.com/Hibernate-exception-when-trying-to-delete-attachment-tp2503343p2504053.html (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@xwiki.org http://lists.xwiki.org/mailman/listinfo/users -- View this message in context: http://n2.nabble.com/Problem-with-HSQLDB-Database-please-Help%21%21-tp2792184p2810276.html Sent from the XWiki- Users mailing list archive at Nabble.com. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Problem with HSQLDB Database please Help!!
Hi Remi, Remi wrote: 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? No. XWiki caches in memory a maximum number of documents that you can configure. 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? HSQLDB is not meant for production instances in any case. It is a convenience distribution for testing. In a near future we will write a warning message next to the standalone distributions (jetty + HSQLDB) download links to state this clear and avoid any confusion. For a production environment you will need to install XWiki in your own servlet container and configure it to use your own database. Please refer to http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Installation#HInstallingtheXWikiWARmanually (and http://platform.xwiki.org/xwiki/bin/view/AdminGuide/ in general). If you need, XWiki SAS (http://www.xwiki.com) can provide you hosting or consulting to get the best out of your XWiki installation. http://www.xwiki.com/xwiki/bin/view/Services/ Regards, Jerome. 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: On Tue, May 5, 2009 at 3:40 AM, Remi remi.pierr...@conseiltechno.comwrote: 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): tomcat2040 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 MySQLhttp://platform.xwiki.org/xwiki/bin/view/AdminGuide/InstallationMySQLyou 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-wikis-tp2434930p2440147.htmland http://n2.nabble.com/Hibernate-exception-when-trying-to-delete-attachment-tp2503343p2504053.html (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@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] Problem with HSQLDB Database please Help!!
Hi, 3 days ago, we took this following error at xwiki 1.8 startup. The install is the standalone Stable: xwiki-enterprise-installer-windows-1.8.2.exe with the hdsqldb database by default. We use xwiki since 2 or 3 months and the database is large of 82Mo. - I tried to use files of the database (replacing database folder) on another clean standalone install, and the problem is same. - I tried to use default database folder of clean install on my problematic install, and it works. - I tried to use save of my database folder (5-6 days old), and the problem is same. I 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. Please any help is welcome, thanks. HTTP ERROR: 500 Error number 3 in 0: Could not initialize main XWiki context Wrapped Exception: Error number 3001 in 3: Cannot load class com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager from param xwiki.store.migration.manager.class Wrapped Exception: 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 it. RequestURI=/xwiki/bin/view/Main/ Caused by: com.xpn.xwiki.XWikiException: Error number 3 in 0: Could not initialize main XWiki context Wrapped Exception: Error number 3001 in 3: Cannot load class com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager from param xwiki.store.migration.manager.class Wrapped Exception: 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 it. at com.xpn.xwiki.XWiki.getMainXWiki(XWiki.java:326) at com.xpn.xwiki.XWiki.getXWiki(XWiki.java:387)at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:135) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:115) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1124) at com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:145) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115) at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:111) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115) at com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115) at com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:295) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:361) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:324) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:535) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:865) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:538) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522) Wrapped Exception: com.xpn.xwiki.XWikiException: Error number 3001 in 3: Cannot load class com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager from
Re: [xwiki-users] Problem with HSQLDB Database please Help!!
On Tue, May 5, 2009 at 3:40 AM, Remi remi.pierr...@conseiltechno.comwrote: 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): tomcat2040 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 MySQLhttp://platform.xwiki.org/xwiki/bin/view/AdminGuide/InstallationMySQLyou 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-wikis-tp2434930p2440147.htmland http://n2.nabble.com/Hibernate-exception-when-trying-to-delete-attachment-tp2503343p2504053.html (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@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
