XSLT timeout
Here should go questions about transforming XML with XSLT and FOP.
-
- Posts: 24
- Joined: Thu Apr 27, 2006 5:39 pm
XSLT timeout
Using Saxon EE for XSLT transformation of a very large document, where each "record" in the XML is output to a file on disk, the XSLT process fails with a timeout error. Is there a way to increase the time limit?
-
- Posts: 2879
- Joined: Tue May 17, 2005 4:01 pm
Re: XSLT timeout
Hi,
Could you please provide the full error message?
Are all the resources involved in the transformation in the local file system, or are there some remote files involved?
Timeout errors usually appear when a remote resource is unavailable, so it may not have anything to do with the size of the file, but its availability.
If it's indeed a remote resource timeout, you can adjust the timeout value in Options > Preferences, Network Connection Settings > HTTP(S)/WebDAV, "Read timout (seconds)". Avoid using more than 60, as it can increase delays when there is a real problem.
Regards,
Adrian
Could you please provide the full error message?
Are all the resources involved in the transformation in the local file system, or are there some remote files involved?
Timeout errors usually appear when a remote resource is unavailable, so it may not have anything to do with the size of the file, but its availability.
If it's indeed a remote resource timeout, you can adjust the timeout value in Options > Preferences, Network Connection Settings > HTTP(S)/WebDAV, "Read timout (seconds)". Avoid using more than 60, as it can increase delays when there is a real problem.
Regards,
Adrian
Adrian Buza
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
-
- Posts: 24
- Joined: Thu Apr 27, 2006 5:39 pm
Re: XSLT timeout
Adrian,
Thank you very much for the suggestions. Yes, the large XML document I was processing was located on a network drive. As you suggested, I moved the whole process to local disk. But I didn't actually try this again in oXygen. Instead I used Saxon at the command line, which worked fine. Doing so allowed me to continue using oXygen while the transformation was running, which took about 19 hours.
Thanks,
Greg
Thank you very much for the suggestions. Yes, the large XML document I was processing was located on a network drive. As you suggested, I moved the whole process to local disk. But I didn't actually try this again in oXygen. Instead I used Saxon at the command line, which worked fine. Doing so allowed me to continue using oXygen while the transformation was running, which took about 19 hours.
Thanks,
Greg
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service