4 Dec
2008
4 Dec
'08
3:36 p.m.
Hi All
I am having a problem uploading a xar file. I get "Java Heap Space, Out
of memory exception" (full message below).
I've downloaded the latest version of XWiki for windows xp (beginner's
version with HSQLDB & Jetty).
In my start_xwiki.bat I have set "set JAVA_OPTS=-Xmx1600m -Xms512m".
1.6gb is the maximum as xwiki would not start if I go over this.
I don't think I have CATALINA.bat any ware so I din not find where to
set CATALINA_OPTS.
I have changed file upload size to 133MB by going to
http://localhost:8080/xwiki/bin/edit/XWiki/XWikiPreferences?editor=objec
t and changing Maximum Upload Size:.
The .xar file is 90MB downloaded as backup from
http://patternlanguagenetwork.myxwiki.org/xwiki/bin/view/Main/WebHome.
I do not know what version this runs on since it is on one of the xwiki
farm things :-).
I have Win XP with 3.5gb memory available.
Has anyone had this error recently?
Regards
Ajdin Brandic
Here is the full error message:
A problem occured while trying to service your request. Please contact
the support if this happens again.
Detailed information:
Error number 11014 in 11: Java Heap Space, Out of memory
exception
Wrapped Exception: null
com.xpn.xwiki.XWikiException: Error number 11014 in 11: Java Heap Space,
Out of memory exception
Wrapped Exception: null
at
com.xpn.xwiki.plugin.fileupload.FileUploadPlugin.getFileItemData(FileUpl
oadPlugin.java:297)
at com.xpn.xwiki.web.UploadAction.action(UploadAction.java:78)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:215)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:115)
at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestPr
ocessor.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.doPost(ActionServlet.java:432)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:616)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web
ApplicationHandler.java:830)
at
com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(Conversion
Filter.java:94)
at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web
ApplicationHandler.java:821)
at
com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestor
erFilter.java:287)
at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web
ApplicationHandler.java:821)
at
com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodi
ngFilter.java:112)
at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web
ApplicationHandler.java:821)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationH
andler.java:471)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1565)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationCon
text.java:633)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1517)
at org.mortbay.http.HttpServer.service(HttpServer.java:954)
at
org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:983)
at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244
)
at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Wrapped Exception:
java.lang.OutOfMemoryError
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(Unknown Source)
at
com.xpn.xwiki.plugin.fileupload.FileUploadPlugin.getFileItemData(FileUpl
oadPlugin.java:293)
at com.xpn.xwiki.web.UploadAction.action(UploadAction.java:78)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:215)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:115)
at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestPr
ocessor.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.doPost(ActionServlet.java:432)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:616)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web
ApplicationHandler.java:830)
at
com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(Conversion
Filter.java:94)
at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web
ApplicationHandler.java:821)
at
com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestor
erFilter.java:287)
at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web
ApplicationHandler.java:821)
at
com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodi
ngFilter.java:112)
at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(Web
ApplicationHandler.java:821)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationH
andler.java:471)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1565)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationCon
text.java:633)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1517)
at org.mortbay.http.HttpServer.service(HttpServer.java:954)
at
org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:983)
at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244
)
at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
--------------------------------------------------------
NOTICE
This message and any files transmitted with it is intended for the addressee only and may
contain information that is confidential or privileged. Unauthorised use is strictly
prohibited. If you are not the addressee, you should not read, copy, disclose or otherwise
use this message, except for the purpose of delivery to the addressee.
Any views or opinions expressed within this e-mail are those of the author and do not
necessarily represent those of Coventry University.
5 Dec
5 Dec
10:13 a.m.
Ajdin Brandic wrote:
This is a major design flaw of the current attachment storage model. As
stated in a previous mail, handling attachment consumes about 27 time
the size of the attachment, so 90M * 27 ~= 2.5G. This needs to be fixed
ASAP. In the meantime, you can either increase the heap size to more
than 2.5G, or request an sql dump from the myxwiki farm admins.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
10:23 a.m.
Sergiu
Xwiki would not start with heap size more than 1.6gb, I've attempted
this.
I'll try the other option you've suggested although I do not know how to
load sql dump into HSQLDB? I've you have any suggestions please advise.
I searched web for 2 days looking for answers to this question and all I
found was JAVA_OPTS and CATALINA_OPTS suggestions. I have not seen any
ware your comment on "handling attachment consumes about 27 time the
size of the attachment". It was probably some ware out there but I
missed it.
Maybe you should include it on the Import/Export page
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/ImportExport
Thank you for your response, at least I know where the issue is.
Ajdin
-----Original Message-----
From: users-bounces(a)xwiki.org [mailto:users-bounces@xwiki.org] On Behalf
Of Sergiu Dumitriu
Sent: 05 December 2008 10:14
To: XWiki Users
Subject: Re: [xwiki-users] Java Heap Space, Out of memory exception
Ajdin Brandic wrote:
This is a major design flaw of the current attachment storage model. As
stated in a previous mail, handling attachment consumes about 27 time
the size of the attachment, so 90M * 27 ~= 2.5G. This needs to be fixed
ASAP. In the meantime, you can either increase the heap size to more
than 2.5G, or request an sql dump from the myxwiki farm admins.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
--------------------------------------------------------
NOTICE
This message and any files transmitted with it is intended for the addressee only and may
contain information that is confidential or privileged. Unauthorised use is strictly
prohibited. If you are not the addressee, you should not read, copy, disclose or otherwise
use this message, except for the purpose of delivery to the addressee.
Any views or opinions expressed within this e-mail are those of the author and do not
necessarily represent those of Coventry University.
10:43 a.m.
Hi
I am still learning about xwiki (how to code velocity, code/add plug-in
etc) so wanted some real data.
I will install mysql and ask for sql dump as Sergiu suggested.
I will add a few notes as Comments to Import/Export and Download pages!!
Many thanks!
Ajdin
-----Original Message-----
From: users-bounces(a)xwiki.org [mailto:users-bounces@xwiki.org] On Behalf
Of Vincent Massol
Sent: 05 December 2008 10:30
To: XWiki Users
Subject: Re: [xwiki-users] Java Heap Space, Out of memory exception
On Dec 5, 2008, at 11:23 AM, Ajdin Brandic wrote:
One warning: You should definitely not use HSQLDB for anything more than
demo purpose. It's not a production database.
Thanks
-Vincent
I searched web for 2 days looking for answers to this question and all
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
--------------------------------------------------------
NOTICE
This message and any files transmitted with it is intended for the addressee only and may
contain information that is confidential or privileged. Unauthorised use is strictly
prohibited. If you are not the addressee, you should not read, copy, disclose or otherwise
use this message, except for the purpose of delivery to the addressee.
Any views or opinions expressed within this e-mail are those of the author and do not
necessarily represent those of Coventry University.
10:50 a.m.
An alternative is to export the pages in chunks. Install the
ImportExport application, which allows to select which pages to export,
and only select a few pages at a time, keeping the size of the
attachments smaller. Then, import each archive one by one.
The best option, however, is to install mysql and import the sql dump.
Ajdin Brandic wrote:
That mail was pretty old. Only the conclusion is relevant to this topic,
the huge memory requirement.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
11 Jun
11 Jun
12:21 p.m.
Dear all,
sorry for replying to an old post, but just want to emphasise the problems
the import/export actions still have.
At this moment I cannot do a proper export from Xwiki Enterprise 2.1.
Also I am unable to do any export with the ImportExportApplication.
I would just like to put all those problems on a list here, and hope anyone
will have a fix:
- export from Xwiki 2.1 fails: file export stops around 65,2 MB, then no
error.
At import there are no files visible in Xwiki 2.3.1 : no error! After some
time I found the exported XAR to be an invalid ZIP archive.
While changing JVM options on the appserver, once it happened somehow that I
could see a list from the files. After importing i notices stuff not
working, it appeared files were missing.
- ImpotExportApllication by Ludovic Dubois according to the page should be
included in Xwiki. I did not find it in 1.9, 2.1 or 2.3. After installing I
can select a space, but I don't see anyh content so I cannot make any
export.
So, while having gathered the resources to do so, I am UNABLE to do an
export and I cannot migrate the software from the application!
I have managed to do this before, since a previous export file was 79 MB in
size and somehow I got that.
So does anyone know how to get the normal export working?
And please, please, please can you gives this trouble around import/export a
lot attention?
From what I see I still need a JVM from around 2048m to
be able to import.
I think this kind of trouble really does not make Xwiki
Enterprise ready and
it costs us so much time.
If you need any more info please let me know.
Any help is appreciated.
--
View this message in context:
http://xwiki.475771.n2.nabble.com/Java-Heap-Space-Out-of-memory-exception-t…
Sent from the XWiki- Users mailing list archive at Nabble.com.
12:37 p.m.
On Fri, Jun 11, 2010 at 14:21, Vincent Gerris <v.j.gerris(a)hhs.nl> wrote:
Quick answer for your immediate need: you should try
http://code.xwiki.org/xwiki/bin/view/Snippets/LargeWikiExportSnippet
(first script). That's probably the existing tool that takes the less
memory when exporting.
Now about standard export yes it's really not good regarding memory
consumption but someone has to work on it...
--
Thomas Mortagne
4:02 p.m.
Dear Thomas,
Thank you for your quick reply.
I finally managed to do a proper export by enlarging the heap space to
around 2 GB.
To my big surprise after that the import did not work, complaining about
the 10 MB limit ?!?
That said, I have no problem attaching a 65 mb file, but 180 mb was too
big, even when i had set upload_maxsize to 200000000 or something.
So crap!!
I did a database exp/imp on Oracle.
After that I found out the after app check do not work on Oracle (sigh).
Well, fotunately I noticed a lot of bugfixes, so in overall I am still
happy with it.
Now on to performance tuning, because a lot of wins lie there too!
How would have to work on that import export?
Should I report in Jira?
I think when functionality is present, it should work.
If not, it is better to disable it, or have only space exports or
something.
This is up to now one of the weak spots of Xwiki.
thanks again, have a nice weekend!
Kind regards,
Vincent
On Fri, 2010-06-11 at 05:38 -0700, tmortagne [via XWiki] wrote:
--
Met vriendelijke groet,
Vincent Gerris (SL 2.34)
De Haagse Hogeschool
Dienst ICT
V.J.Gerris(a)hhs.nl
Tel: 070 445 7468
--
View this message in context:
http://xwiki.475771.n2.nabble.com/Java-Heap-Space-Out-of-memory-exception-t…
Sent from the XWiki- Users mailing list archive at Nabble.com.
5402
days inactive
5956
days old
8 comments
5 participants
participants (5)
-
Ajdin Brandic -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Gerris -
Vincent Massol