Dowson_Jim(a)emc.com wrote:
An MS Word document.
The error also happened with a 6.5 MB zip file - so the xwiki limit of
10MB may not be the issue (although documents larger than the alleged
1MB MySQL limit have been successfully uploaded).
Thus, the problem may arise from the amount of memory available for
Java. What servlet container are you using? I've seen this error here
running Tomcat. You can increase this amount by passing this parameter
"-Xmx256m -Xms256m" (in this case 256Mb will be the new amount of
available memory) at startup time.
So, you have to shutdown your servlet container, modify some script to
startup.sh, catalina.sh or whatever your are using to launch Tomcat, to
add this paramenters to CATALINA_OPTS or JAVA_OPTS. I have not a clear
idea about what is the right variable to be modified. Any feedback will
be really welcome.
Here is the script I am using here to start Tomcat:
mire:/home/webmaster/bin # cat start_tomcat6
#!/bin/sh
export CATALINA_HOME=/usr/share/tomcat-6.0.10
export JAVA_HOME=/usr/share/java/jre-1.6.0_01
export JRE_HOME=/usr/share/java/jre-1.6.0_01
export CATALINA_OPTS="-Xmx512m -Xms512m"
export JAVA_OPTS="-Xmx512m -Xms512m"
$CATALINA_HOME/bin/startup.sh
As per your question about the need of restarting XWiki so that the new
configuration values become effective. Yes, this is required. xwiki.cfg
is read at deployment time. So if you have any utility that allow you to
restart just one application, you are a lucky person :-) If you have not
it, just restart the servlet container.
I am sure there are people out there with a much more in depth knowledge
about this issue. But this has helped me. I hope it could be useful for
you as well.
Greetings,
--
Ricardo RodrÃguez
Your EPEC Network ICT Team