According to a post i read, the number is in bytes. So for 200 mb, you would need to add 000000 so 200000000. Does that work for you? Because I did set the value on that, but still get: XWiki heeft standaard een limiet van ongeveer 10Mb voor ingeschrevenen bestanden. Deze limiet kan worden gewijzigd met de upload_maxsize parameter. Check de FAQ voor meer informatie. (which says there is a 10mb linit in Dutch). Did anyone get this working? -- View this message in context: http://n2.nabble.com/Changed-upload-maxsize-but-still-can-t-attach-larger-th... Sent from the XWiki- Users mailing list archive at Nabble.com.

Hi Vincent, I was able to attach 30mb files by editing the parameter but I seem to remember I had to reset the wiki engine for it to take effect. I remember a 500 error message unless I passed a parameter to Jetty when starting -Dorg.mortbay.jetty.Request.maxFormContentSize=9999999 Also if you use Mysql, you will have to change the maximum packet size, something I don't know anything about because I don't use Mysql. I also remember running into other limitations around 30mb. Of course these errors look much different than what you are seeing, just letting you know what to expect. Thanks, Caleb James DeLisle Vincent Gerris wrote:

According to a post i read, the number is in bytes. So for 200 mb, you would need to add 000000 so 200000000.

Does that work for you? Because I did set the value on that, but still get: XWiki heeft standaard een limiet van ongeveer 10Mb voor ingeschrevenen bestanden. Deze limiet kan worden gewijzigd met de upload_maxsize parameter. Check de FAQ voor meer informatie.

(which says there is a 10mb linit in Dutch). Did anyone get this working?

Hi Vincent, On Thu, Feb 18, 2010 at 2:40 PM, Vincent Gerris <[email protected]> wrote:

Thanks for your quick reply. For me 100000000 did not work (nor 200000000). I am trying to import a 75,4 MB import with no luck.

Right now we have an issue with how attachments are handled. IIRC you'll need around attachmentSize*30 of RAM allocated to XWiki in order for the attachment to upload fine. You can try using this script if you can't allocate that much memory (it will create a XAR on the filesystem): http://code.xwiki.org/xwiki/bin/view/Snippets/LargeXARImportScriptSnippet Guillaume

So I go to: http://localhost:8888/ictwiki/bin/admin/XWiki/XWikiPreferences Then press change class, update the number with the value and still get that dumb 10MB error. I use Oracle XE as a database. After a change to 99000000 I still get that error. So it seems like a bug too me. I guess Iĺl make a post on Jira again :).

-- View this message in context: http://n2.nabble.com/Changed-upload-maxsize-but-still-can-t-attach-larger-th... Sent from the XWiki- Users mailing list archive at Nabble.com. _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users

-- Guillaume Lerouge Product Manager - XWiki SAS Skype: wikibc Twitter: glerouge http://guillaumelerouge.com/

Hello Vincent, Yes, resetting tomcat is what I was talking about. Jetty is an alternative to tomcat so you can disregard that advice. If you are importing an XAR file I recommend the code snippet as I have tried to do large imports for a while and I ended up writing a custom XMLRPC importer. I remember trying to import a large file not only was troublesome uploading the attachment but doing the actual import took a long time and was prone to failure. Thanks, Caleb James DeLisle Vincent Gerris wrote:

hi Caleb James,

As my previous post shows, it does not work for me. I use Oracle XE, I have encountered no 500 errors. I do not know where to try that Jetty setting.

I also restarted the complete Xwiki instance by restarting Tomcat, do you mean that by resetting the engine?

Well, I just see the post from Guillaume now. The tomcat java only has 128MB now, so I will try to enlarge that and otherwise use that codesnippet (if i figured out how).

How large of an attachment are you trying to upload? I changed that value in /bin/edit/XWiki/XWikiPreferences?editor=object That same message can also be shown if there is not enough memory available so changing -Xmx might also help. Caleb andre.j wrote:

Hello,

I still have this problem too. I have changed the value of this property with no change. I´m using Tomcat with MySQL. Is there still a fix or solution for that ?

Greetings André

I have never been able to upload a file larger than 30MB. The problem is the file is saved as a base64 string for RCS version storage which consumes a large amount of memory. Caleb andre.j wrote:

Hello,

thanks for the fast answer. Our users would upload a 50MB .pdf file. So I changed the value and nothing happens. I just added the JAVA_OPTS variable with -Xmx300m and the problem is still alive.

I have updated my xwiki system to version 2.4 and now there is no upload_maxsize variable. Is this right ?!

Thanks André