I did set up an xWiki in a separate network with no internet connection for a limited user group. So far everything looks good. However, I noticed that the server tries to call several xWiki reps and logs timeout errors. Furthermore, I noticed that when you open the xWiki homepage from within the network (i.e. with no internet connection), the loading times are incredibly long although the network connection is good. If you call the homepage from outside the network (NAT) on a pc with a working internet connection, everything is working perfect.
If I’d need to make a guess I’d say that there are several internet links in the background which take some time to timeout and thus prevent the whole page from loading (just a guess). This does note seem to be a browser issue as I tried it with IE and Firefox.
So basically I have two questions:
1.:Is there something hidden in the default xWiki homepage which is trying to access internet links and thus causing my problem?
2.: Is there a way I can prevent the xWiki server from ‘‘calling home’’ (ie look for updates of extensions etc)?
Thanks a lot in advance, I appreciate your support!
Best regards,
Morten
I noticed that the server tries to call several xWiki reps and logs timeout errors
This one is XWiki trying to get details on the extensions it could find in the classpath at startup but it’s running on the background and should not have any kind of impact on the performances. If you don’t plan to install any extension in XWiki you should disable the extension repositories in xwiki.properties to avoid it trying to access something that won’t work (and produce nasty error log). See http://extensions.xwiki.org/xwiki/bin/view/Extension/Extension%20Module/Repositories/ (at the end).
Furthermore, I noticed that when you open the xWiki homepage from within the network (i.e. with no internet connection), the loading times are incredibly long although the network connection is good
You are not talking about the first load, right ? You get that every time you try to load the home page, even after a while ?
Is it only the home page ? Is it any better if you edit the home page and remove the whole content ?
The only external thing I can think of in the default home page is the iframe which get a video from Youtube but that should be asynchronous and not block the loading I think.
Something that might help figure out where exactly is the issue is to enable debug information using ?debug=true in the URL and look at the loading tree on the bottom of the page. See http://dev.xwiki.org/xwiki/bin/view/Community/Debugging#HDebugmode for more details. Not that this covers only the server side, the you can use the browser dev tools to see if the issue come from a blocking js/css resource.