4 May
2011
4 May
'11
7:35 p.m.
On 05/04/2011 06:44 PM, andyp wrote:
Hi Sergiu,
Unfortunately this doesn't work for me. With the below entry in my
jboss-web.xml, the Virtual Machine JBoss is on hangs within 7 minutes and I
have to reboot the VM. Also at no point am I able to connect to the default
JBoss page (http://localhost:8080). To see the full startup log, please
find the attached -
http://xwiki.475771.n2.nabble.com/file/n6331582/jboss_startup_error.txt
jboss_startup_error.txt .
<class-loading java2ClassLoadingCompliance="false">
<loader-repository>
org.xwiki:archive=xwiki.war
<loader-repository-config>java2ParentDelegation=false</loader-repository-config>
</loader-repository>
</class-loading>
<1 Min:
http://xwiki.475771.n2.nabble.com/file/n6331582/Selection_078.png
<2 Mins:
http://xwiki.475771.n2.nabble.com/file/n6331582/Selection_079.png
7 Mins (flat-lined):
http://xwiki.475771.n2.nabble.com/file/n6331582/Selection_082.png
Right, I forgot to mention that I had to increase the memory limits a
lot to get it to work.
In bin\run.conf.bat (if you're on windows) you should search for the
line setting Xms and MaxPermSize, and replace it with:
set "JAVA_OPTS=-Xms512M -Xmx2048M -XX:MaxPermSize=512M"
As reported before, the only way I can get JBoss to
complete it's startup
and not crash the machine is by using the following entry in jboss-web.xml.
However, XWiki does still not start under this config.
<loader-repository>
org.xwiki:archive=xwiki.war
</loader-repository>
This is wrong, the server manages to start up because the jboss-web.xml
file is invalid, so it won't even try to start xwiki.war
Actually, since there is no real class conflict, the classloader
configuration is not important, you can remove that part completely.
Many thanks,
Andy
--
Sergiu Dumitriu
http://purl.org/net/sergiu/