ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Spam quarantine notifications fail to complete if it takes too long


Article ID: 161823


Updated On:


Messaging Gateway


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. 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: 


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

STACKTRACE: Can not read response from server. Expected to read 
bytes, read 41 bytes before connection was unexpectedly lost.
at com.mysql.jdbc.MysqlIO.readFully(
at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(
at com.mysql.jdbc.MysqlIO.checkErrorPacket(
at com.mysql.jdbc.MysqlIO.checkErrorPacket(


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.


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