When importing a collection (9 pst files total, using the emailchemy integration), I had 52,000 attachments import successfully, but also approx 14,000 attachments that did not import with this error message below showing up in the reports:
Ignoring attachment for C:\[local file path]epadd_emailchemy_tmp5339691712502667397\talks_and_writing.pst\Outlook Data File\Top of Outlook data file\Talks and Writing.mbox Message #6: java.lang.NullPointerException
at edu.stanford.muse.email.EmailFetcherThread.handleAttachments(EmailFetcherThread.java:836)
at edu.stanford.muse.email.EmailFetcherThread.processMessagePart(EmailFetcherThread.java:810)
at edu.stanford.muse.email.EmailFetcherThread.processMessagePart(EmailFetcherThread.java:791)
at edu.stanford.muse.email.EmailFetcherThread.fetchAndIndexMessages(EmailFetcherThread.java:1398)
at edu.stanford.muse.email.EmailFetcherThread.run(EmailFetcherThread.java:1633)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Steps to reproduce the behavior:
- Import one or more .pst files into the appraisal module
- After a successful import, check on the reports from the browse screen in the appraisal module
I can't tell from this error message if this is a problem with ePADD, the email attachments, our version of Java, or something else. But a colleague with more experience with Java suggested that this may be a low-level bug in the code.
- Windows 11
- Chrome browser
- ePADD 11.1
- Java SE Development Kit 11.0.18 [as per my IT department -- I do not have access to this information]
When importing a collection (9 pst files total, using the emailchemy integration), I had 52,000 attachments import successfully, but also approx 14,000 attachments that did not import with this error message below showing up in the reports:
Steps to reproduce the behavior:
I can't tell from this error message if this is a problem with ePADD, the email attachments, our version of Java, or something else. But a colleague with more experience with Java suggested that this may be a low-level bug in the code.