D
darrel
We've been building a CMS system that spits out XML files everytime the site
menu is updated. These XML files are then used by the front-end.
About once a week, one of these files gets half-written. The writing of the
file just ends halfway through, thereby leaving in invalid XML file which
throws an error in our application.
We're at a total and complete loss as to why this happens. Any theories?
Could it be Norton? It's a function that writes the XML file...could these
be getting interuppted somehow?
The only solution thus far that I've come up with is to write the XML file,
then open the XML file. If invalid, write again. Repeat as needed or until I
time it out (after so many checks) and then throw an error. Hardly ideal.
-Darrel
menu is updated. These XML files are then used by the front-end.
About once a week, one of these files gets half-written. The writing of the
file just ends halfway through, thereby leaving in invalid XML file which
throws an error in our application.
We're at a total and complete loss as to why this happens. Any theories?
Could it be Norton? It's a function that writes the XML file...could these
be getting interuppted somehow?
The only solution thus far that I've come up with is to write the XML file,
then open the XML file. If invalid, write again. Repeat as needed or until I
time it out (after so many checks) and then throw an error. Hardly ideal.
-Darrel