08/19/2021 21:19:27.911 ERROR (ApprovalInboxProcessorServiceProvider) [com.aveksa.server.email.mailboxmonitor.ApprovalInboxProcessorServiceProvider] FAILED method=emailArrived subTask=handleUnexpectedException ElmID=7372, User=1234, auth=com.aveksa.server.authorization.XXAuthorization@64e54b11, workItem=Id=9999:WPDS:1 JobId=9999 Name=Second Level Approval Reference=888 State=3 Category=Change Request Approval AssignedTo=999 
java.lang.NullPointerException

08/19/2021 21:19:27.913 ERROR (ApprovalInboxProcessorServiceProvider) [com.aveksa.server.email.mailboxmonitor.ApprovalInboxProcessorServiceProvider] Error determining if message was machine-generated. Defaulting to false and continuing.  elm=7777, msg=Could not get Envelope debug info for message.Could not get Content Type.Could not get Filename.Could not determin MIME Type---------------------------
javax.mail.MessageRemovedException

08/18/2021 11:48:19.560 ERROR (ApprovalInboxProcessorServiceProvider) [org.hibernate.internal.SessionImpl] HHH000346: Error during managed flush [could not execute statement]
08/18/2021 11:48:19.560 WARN  (ApprovalInboxProcessorServiceProvider) [com.aveksa.server.email.mailboxmonitor.ApprovalInboxProcessorServiceProvider] Received a message whose Message-Id Header already exists in the DB.  This ususally means another thread or appserver has already processed this email.  msg=EmailLogMessage{messageData='Received: from server.com (10.10.10.10) by

• RSA Identity Governance & Lifecycle 7.2.1
• RSA Identity Governance & Lifecycle 7.5.0
• SecurID Governance & Lifecycle 7.5.2

This issue is resolved in the following versions which locks the record when processing incoming approval emails on multiple nodes in a cluster:

• RSA Identity Governance & Lifecycle 7.2.1 P08
• RSA Identity Governance & Lifecycle 7.5.0 P05
• SecurID Governance & Lifecycle 7.5.2 P01

Note that the "Processing Result Status " of "General Failure Processing Reply" may occur for multiple reasons some of which are expected in normal operations.  If you have this email status without the specific error messages mentioned you do not have this issue.

Note that this message does not always indicate a failure.  Email messages may be processed correctly on the other node of the cluster even if these error messages are generated.