DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=38060>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38060 Summary: Windows File Locking Issues Product: Lenya Version: 1.2.4 Platform: PC OS/Version: Windows XP Status: NEW Severity: major Priority: P2 Component: Workflow AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] Alot of programmers neglect to close files when programming in Java. I guess they assume the garbage collector will eventually clean up these files and they don't have to worry about them. This causes problems with Java running on Windows operating systems, as they make certain demands about open files, eg not allowed to delete them etc. These bugs are quite hard to track down as it can be intermittent, the garbage collector MIGHT close the file and there won't be a problem... then again it might not. This problem manifests itself in lenya in various places. The bug isn't actually in lenya but in some of the xml processing infrastructure which it depends on. I propose rather than waiting for the developers of cocoon etc to fix these problems, we fix the lenya code to take care of opening the files and then we know somebody else isn't going to leave the file open and cause a problem. The patch attached fixes one particular instance of this problem, when deactivating a page on windows, a file needs to be deleted but it has been left open by a documentParser object. I'm sure these file open bugs are causing problems elsewhere in lenya, I have seen a few things on the mailing list which I am sure is caused by the same sort of thing. I haven't experienced them myself as yet. In particular I'm not running Lenya on windows anymore so I don't know if I will be useful in tracking down further bugs. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
