Check array size exceeding VM limit during indexing

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • 2.7
    • Affects Version/s: 2.2.10
    • Component/s: 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

            Assignee:
            Unassigned
            Reporter:
            Ivan Benko [Atlassian]
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: