Welcome to Port3101.org : Your BES Connection Mark forums read | View Forum Leaders
Port3101.org : Your BES Connection

LinkBack (1) Thread Tools Display Modes
  1 links from elsewhere to this Post. Click to view. #1 (permalink)  
Old 04-24-2012, 04:25 PM
BES Activated
Join Date: Apr 2010
Posts: 2

My primary BES (5.0.2) seems to blow up around 1:30 - 5:00 am every day. In the MAGT log file i have the exact same thing for two users (the below log entry). Not able to figure out what is happening...any thoughts would be appreciated.

Everything works fine, not getting any complaints from either user. Just have no idea what is happening.

0181] (04/24 02:01:52.962):{0x10BC} Performing system health check (BlackBerry Mailbox Agent 1 - BESX Version
[30509] (04/24 02:01:52.962):{0x10BC} Current health score, Health=0x000000000200140F, Mask=0x000000000200150F
[30038] (04/24 02:01:52.962):{0x10BC} Worker Thread: *** No Response *** Thread Id=0x1E1C, Handle=0x1c2c, WaitCount=1, WorkingTime=10 min, LastActivity=10 min, Event: CHECK_EMS_MESSAGES, User: [email protected], Server: Exchange, Activity: Starting CDO helper
[30472] (04/24 02:01:52.962):{0x10BC} Minimum WaitCount amongst hung threads is (1), below warning threshold
[50020] (04/24 02:01:52.963):{0x10BC} Amongst threads that are hung, maximum WaitCount=1
[40360] (04/24 02:01:52.963):{0x10BC} [BIPPa] Health: QSize=0, intMap=147
Reply With Quote
Sponsored Links
  #2 (permalink)  
Old 06-02-2012, 09:43 PM
BES Administrator
Join Date: Aug 2010
Location: Here & There
Posts: 32

"No Response" threads are threads that are taking a long time to work on something for a specific user. In most cases, hung threads automatically release but in some cases they don't. The Controller performs a health check every 10 minutes and you'll see "Hung Threads" entries in the CTRL log if there are hung threads on a specific messaging agent. The wait count is important because after the 6th wait count, the Controller will restart the messaging agent. When this happens, users on the messaging agent will experience latency due to mailbox rescans. This may be a couple minutes to 15-20 minutes depending on the number of users on the messaging agent.

In your log line above, the activity is "starting CDO helper". CDO is used for calendaring from the device back to the mailbox. Are your users experiencing calendar sync issues from the device back to the mailbox? Are you using the latest version of CDO.dll?

There could be a variety of reasons that can cause hung threads - high latency between the BES and mail server, large mailbox size, large attachments, etc. Are you running maintenance on mailboxes or the mail server in the middle of the night?
Reply With Quote

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

LinkBacks (?)
LinkBack to this Thread: http://www.port3101.org/port-3101-bes-admin-bar-grill/2640-event-check_ems_messages.html
Posted By For Type Date
Port3101.org : Your BES Connection This thread Refback 10-23-2012 02:39 PM

Similar Threads
Thread Thread Starter Forum Replies Last Post
Event ID 41206 Source DevMgmtConnector Pelvir Port 3101: The BES Admin Bar & Grill 9 04-29-2010 01:31 PM
Event id 1639 omar.jonguitud Port 3101: The BES Admin Bar & Grill 3 10-18-2009 05:26 PM
KB04433 - Event log levels hdawg Featured BlackBerry KB Articles 0 06-16-2009 11:22 AM
Event ID 566 on DC from BESADMIN knottyrope Port 3101: The BES Admin Bar & Grill 5 02-06-2009 05:04 PM

All times are GMT -4. The time now is 08:29 AM.
Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2019, vBulletin Solutions, Inc.


SEO by vBSEO 3.3.2 PL2