Hi Shaun, I don't quite understand the issue, I've added some questions below: On 12/22/2010 6:24 PM, McDonald, Shaun wrote:
Hello All,
Recently, an Oxygen Author user has been experiencing rather large chunks of XML data being removed from documents on save.
Aside from troubleshooting this particular issue, a larger issue arose given a particular scenario.
Let’s say the following parameters are in place:
1. Half our users are on Win XP, the other Win 7, 2. Half us Author v11.2, the other v12, 3. Windows Paging file initial and max values vary.
You mean the paging in the operating system? or Oxygen as a Java application also has some startup paramaters for memory consumption. Are you talking about these parameters?
SCENARIO
1. User checks out an XML file from a CMS repository (via an Oxygen Author plug-in) and edits the document, but
So your plugin handles the check out and creates a temporary file on disk. You probably use System.getProperty("java.io.tmpdir") for this. Is this correct?
2. User gets interrupted with an unrelated task requiring one or more other apps. * The app(s) use a large amount of memory and write to Windows temp,
Files written to the temporary directory are not deleted by default by Windows as far as I know. Do your users have some kind of automated process which removes files from the temporary directory? If you have such cases you can always make your temporary files in another place like System.getProperty("user.home").
3. Memory is overtaxed and the Paging File is written to.
AFAK the Windows swap files have nothing in common with the Windows temporary files directory (in which applications keep temporary files necessary while they are executed).
4. User returns to Author to check in the XML.
And probably there is no more temporary file on disk at this stage? From your original explanation I thought that only parts of the XML were missing on save. Even if Windows deletes temporary files on its own it will most probably not truncate them.
Obviously, we have validation gates to reject ill-formed/invalid XML. But, theoretically, we would like to know exactly what might be checked in given the scenario, and
1.Memory and paging are maxed out already when a user makes an edit to some other document, and
1.Oxygen Backup and Automatic Save Preferences are off,
2.Backup Preferences are on,
3.Automatic Save is on and set to a low value
4.Both 2 and 3 are on.
So in the "Editor / Open/Save" Preferences page you have: 1) "Make backup copy on save" checkbox is CHECKED. 2) "Enable automatic save" checkbox is also CHECKED. The (1) checkbox only applies to local opened files so it probably has no influence in your case (you probably have a custom protocol plugin set up). Maybe the (2) could be a problem if for example while you are checking out a file in the temporary files directory Oxygen makes an automatic save of the current opened file (and the file names are the same?). Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com