Message flow suffers severe latency or ceases due to GWGlobalPollThread::ThreadProc -- Unexpected event signaled (-1) being recorded in the log files

Article ID: KB36118

Type: Support Content

Last Modified: 07-14-2014


Product(s) Affected:

  • BlackBerry Enterprise Server for Novell GroupWise
  • BlackBerry Enterprise Server for Novell GroupWise
  • JI 724081
The following log line starts being recorded repeatedly in the MAGT logs:

[40000] (06/10 17:31:38.045):{0xED4} GWGlobalPollThread::ThreadProc -- Unexpected event signaled (-1).

This log line is recorded multiple times per second and eventually becomes the sole log entry until a Message Agent restart occurs. The repeated logging of this log line can potentially cause excessively large MAGT logs, each file may reach the default limit of 512MB before a new log file is created, these files will eventually be created every few minutes that risks consuming all available disk space until a Message Agent restart. While it appears the Message Agent will continue processing messages when this incident is occurring, all the logging eventually consists solely by the GWGlobalPollThread::ThreadProc entries and message flow ceases.

This is a previously reported issue that is being investigated by our development team. No resolution time frame is currently available.

Restart the BlackBerry Controller Service to reinitialize the BlackBerry Message Agent.

CollapseAdditional Information

This incident has only been seen when there has been an connection interruption to the Microsoft SQL server hosting the configuration database. Under certain conditions the polling thread does not recover and the Message Agent will exhibit the symptoms referenced above.


By downloading, accessing or otherwise using the Knowledge Base documents you agree:

   (a) that the terms of use for the documents found at apply to your use or reference to these documents; and

   (b) not to copy, distribute, disclose or reproduce, in full or in part any of the documents without the express written consent of RIM.

Visit the BlackBerry Technical Solution Center at