Michael Ralston <michael <at> ralston.id.au> writes:

> 
> On Wednesday 07 December 2005 18:12, Kubiak, Thomas wrote:
> > Hello community.
> >
> > We are using Lenya running on Tomcat 5.5.9. Server is a Windows 2003 Server
> > machine.
> >
> > Sometimes it happens, that the Tomcat service locks the content files
> > (index_??.xml) within our publication so that they cannot be deleted.
> > Therefor when users try to modify those contents using the lenya editor the
> > cannot save their changes.
> >
> > As long as tomcat is running these files cannot be deleted even when I try
> > to do it directly on the filesystem of the server.
> >
> > Does anybody have an idea what causes this problem ? Any solutions ? Please
> > help me.
> >
> 
> I have also had this problem with running lenya with Jetty on a windows host. 
> It was due to javax.xml.parsers.DocumentBuilder not closing a file when it 
> was finished with it. The object is eventually garbage collected and the file 
> closed, but not soon enough as other side effects occur. In my instance I was 
> getting an exception when I tried to deactivate a page, the document could 
> not be deleted from the live tree.
> 
> I provided a patch to lenya 1.2 in October, if this is also your problem I 
> can 
> forward you the patch. If it isn't your problem, the patch might give you an 
> idea of how to solve your problem.
> 
> Michael Ralston
> 


Hi,
I am getting a similar issue (Lenya 1.2.4 on Window 2000 Server on Jetty -
default install and default publication). I am randomly not able to delete
documents. If do deactivate them, and they don't show in the Live site, but the
status in Site tab shows they are active. Subsequently, the delete option is
also inactive. I have once deleted the files and modified the xml file on the
filesystem, but am looking for a more graceful method to delete my documents.
Thanks.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to