Spam quarantine notifications fail to complete if it takes too long

Products

• Messaging Gateway

Issue/Introduction

The Spam Quarantine Notification scheduled task reports as having failed and not all end users are notified of messages waiting in the Messaging Gateway spam quarantine, after approximately 20-30 minutes.

Oct 03 2014 20:20:30 [BrightmailScheduler_Worker-28] [SpamNotificationTask]
ERROR - Notification poller error. A user could not be notified of new spam
messages. 
com.symantec.smg.controlcenter.internal.dataaccess.DataAccessException: An
unexpected database error has occurred. Please contact your system
administrator. ; nested exception is: 
com.mysql.jdbc.CommunicationsException: Communications link failure 
due to
underlying exception: 

** BEGIN NESTED EXCEPTION ** 

java.io.EOFException

MESSAGE: Can not read response from server. Expected to read 154 bytes, read 
41
bytes before connection was unexpectedly lost.

STACKTRACE:

java.io.EOFException: Can not read response from server. Expected to read 
154
bytes, read 41 bytes before connection was unexpectedly lost.
at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1997)
at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2464)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2916)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:885)

Cause

When the spam quarantine notification process takes too long to complete, usually due to rate limiting by the receiving server, the underlying database connection may time out resulting in a failure to complete the notification process.

Resolution

This issue was resolved with Messaging Gateway 10.5.4. Spam quarantine notifications now complete without encountering a network timeout.