Details
-
Bug
-
Resolution: Fixed
-
Major
-
5.0-milestone-1
Description
The problem is that com.xpn.xwiki.store.XWikiHibernateStore.deleteXWikiDoc(XWikiDocument, XWikiContext) calls com.xpn.xwiki.store.XWikiHibernateAttachmentStore.deleteXWikiAttachment(XWikiAttachment, boolean, XWikiContext, boolean) in the same session, and this one wrongly calls loadAttachmentContent. So it tries to load all the attachments in memory in the current session, just to delete them. But to delete something from the session it's enough to have a "stub" with the same identifier, the actual content isn't needed.
Attachments
Issue Links
- depends on
-
XWIKI-13902 Rewrite entities to/fromXML methods based on Filter framework
- Closed
- is duplicated by
-
XWIKI-7040 Unable to delete document when sum of attachments in size is greater than max_allowed_packet
- Closed
-
XWIKI-9989 Delete a page with a attachment bigger than the Database file size ends up in a timeout error
- Closed
-
XWIKI-10611 When a document is deleted, even with filesystem attachments enabled, the content of the attachments is stored in the database.
- Closed
-
XWIKI-14284 delete/move page with big attachment failed
- Closed
- is related to
-
XWIKI-9046 Renaming a document holding a lot of revisions can lead to an OutOfMemory exception
- Closed
-
XWIKI-16782 Deleting or exporting a document containing a very large attachment takes a lot of memory
- Closed
- relates to
-
XWIKI-10611 When a document is deleted, even with filesystem attachments enabled, the content of the attachments is stored in the database.
- Closed
-
XWIKI-13934 Store deleted documents with the same structure as the curent documents
- Open