XOPUS gets timeout on default-config.xml

  • 1 reply.
  • This is not yet resolved.
  • This question was started by Harold.
  • Last post by Sjoerd Visscher.
Harold
member
September 23rd 2008
Hi all,

we have XOPUS deployed on an Oracle Application Server with a webcache and a reverse proxy in front of it. When I try to open a document, XOPUS gets a timeout on default-config.xml, which is loaded from the webcache, but downloading the file directly in the browser is very fast.
Does anybody have an idea why this might happen? Is XOPUS trying to parse the default-config.xml file, which results in the timeout? When the file is in the browser cache opening the document is very fast.
Is it an option to deploy XOPUS on the reverse proxy, to increase speed?

regards,

Harold
Sjoerd Visscher
Xopus Team
September 23rd 2008
There is a difference between loading xml files by Xopus and by the browser: other http headers are sent. You could check f.e. with Fiddler if that could be the problem.

To be clear: default-config.xml is the first xml file that Xopus loads, so whenever there are problems with loading xml files, it will show up when loading default-config.xml.

React

HTML will be shown as HTML code.
Linebreaks and Links starting with http:// are automatically resolved