• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 2.7
    • 2.2.10
    • None

      We should put a protection-shield in place to do not allow indexing proceeding when trying to allocate array size that exceeds the VM limits as documented here and additional explanation here

      2008-07-18 02:00:00,199 WARN [confluence.importexport.impl.BackupJob] executeInternal No daily backup directory specified to store the backups. Taking no action!
      2008-07-18 06:38:09,139 ERROR [confluence.search.lucene.ConfluenceObjectToDocumentConverter] convert 
      java.lang.OutOfMemoryError: Requested array size exceeds VM limit
      2008-07-18 06:38:09,250 ERROR [search.lucene.extractor.MsPowerpointContentExtractor] processPOIFSReaderEvent Looks like an invalid size? 3061729207
      2008-07-18 06:49:45,905 ERROR [confluence.search.lucene.ConfluenceObjectToDocumentConverter] convert 
      java.lang.OutOfMemoryError: Requested array size exceeds VM limit
      2008-07-18 06:51:34,805 ERROR [confluence.search.lucene.ConfluenceObjectToDocumentConverter] convert 
      java.lang.OutOfMemoryError: Requested array size exceeds VM limit
      2008-07-18 06:51:34,854 ERROR [search.lucene.extractor.MsPowerpointContentExtractor] processPOIFSReaderEvent Looks like an invalid size? 1322484849
      2008-07-18 06:51:34,856 ERROR [search.lucene.extractor.MsPowerpointContentExtractor] processPOIFSReaderEvent Looks like an invalid size? 3698783899
      2008-07-18 07:07:49,585 ERROR [confluence.search.lucene.ConfluenceObjectToDocumentConverter] convert 
      java.lang.OutOfMemoryError: Requested array size exceeds VM limit
      

      Suggestion :

      • skip indexing of such attachments and log the name and result/size for reference

            [CONFSERVER-12509] Check array size exceeding VM limit during indexing

            Closing issue for now. If a regression is found, I will open a new bug and link it to this issue.

            Andrew Lynch (Inactive) added a comment - Closing issue for now. If a regression is found, I will open a new bug and link it to this issue.

            Reopened until related case has been resolved.

            Andrew Lynch (Inactive) added a comment - Reopened until related case has been resolved.

            There has already been a size limit for some time(the issue wasn't linked with the commit, so I can't track it down) plus the underlying request for such a large amount of memory should no longer occur.

            Andrew Lynch (Inactive) added a comment - There has already been a size limit for some time(the issue wasn't linked with the commit, so I can't track it down) plus the underlying request for such a large amount of memory should no longer occur.

              Unassigned Unassigned
              ivan@atlassian.com Ivan Benko [Atlassian]
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: