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



Reply
LinkBack (4) Thread Tools Display Modes
Manually restarting a single Messaging Agent
 
  4 links from elsewhere to this Post. Click to view. #1 (permalink)  
Old 11-28-2008, 09:20 AM
Otto's Avatar
Proprietor
 
Join Date: Nov 2008
Location: Atlanta, GA
Posts: 2,033
Blog Entries: 14
Default Manually restarting a single Messaging Agent

I've been requesting this feature for ages now (within the console), but in lieu of that being available at this point in time, here's a rather involved process to accomplish this functionality. RIM has 'documented' this process in two KB articles, but neither are in response to hung threads and the 60-minute self-recovery. This process will allow you to bypass the Controller restarts (all users impacted) and focus only on those who are impacted by the hung thread.

From the Controller log, this is an identified hung thread for MAGT_01:



Searching in the Controller log above the hung thread entry, you can find the Windows PID (Process ID) for the impacted agent:



In Task Manager, with the option for the PID being displayed, locate the ID that matches the one identified in the Controller log:



The Controller service will spawn a new Agent process immediately after the ailing process has been ended:

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.
Reply With Quote
Sponsored Links
  #2 (permalink)  
Old 01-11-2009, 08:30 PM
hdawg's Avatar
Proprietor
 
Join Date: Nov 2008
Posts: 2,257
Blog Entries: 147
Default

This is secretly one of my favorite things ever. I don't think you'd ever see this as a recommended procedure by anyone from RIM or really any other vendor as a solution ... but it is cool, super simple, and works!
__________________
http://blog.port3101.org/hdawg/
Reply With Quote
  #3 (permalink)  
Old 01-11-2009, 10:53 PM
d_fisher's Avatar
BES Guru
 
Join Date: Dec 2008
Location: Columbus, OH
Posts: 247
Default

You can also save time by simply terminating the process via command line (even remotely). Use the native Windows command taskkill or pskill that is part of Sysinternals suite.
Reply With Quote
  #4 (permalink)  
Old 05-27-2009, 12:09 AM
BES Administrator
 
Join Date: Feb 2009
Location: I come from a land down under where beer does flow and men chunder
Posts: 42
Default

Hmm, I'm running 4.1.6 BES for GroupWise & the Controller log doesn't show the process ID of the agent.

Last edited by devans; 05-27-2009 at 03:36 AM.
Reply With Quote
  #5 (permalink)  
Old 05-27-2009, 05:12 AM
Abe Abe is offline
Super Moderator
 
Join Date: Dec 2008
Location: Germany
Posts: 598
Default

Quote:
Originally Posted by devans View Post
Hmm, I'm running 4.1.6 BES for GroupWise & the Controller log doesn't show the process ID of the agent.

This is Exchange specific. I am not sure about Groupwise BES, but as far as I know Groupwise works different.
__________________


Last edited by Abe; 05-27-2009 at 05:35 AM.
Reply With Quote
  #6 (permalink)  
Old 05-27-2009, 09:43 AM
hdawg's Avatar
Proprietor
 
Join Date: Nov 2008
Posts: 2,257
Blog Entries: 147
Default

IIRC GroupWise uses a single messaging agent ...
__________________
http://blog.port3101.org/hdawg/
Reply With Quote
  #7 (permalink)  
Old 05-27-2009, 12:21 PM
RadHaz75's Avatar
BES Expert
 
Join Date: May 2009
Location: Philadelphia, PA
Posts: 98
Default

why do you get the process id from the controller log? you already have the messaging agent log open so why not just search up for "process id"?
__________________
Two months ago, I saw a provocative movie on cable TV. It was called The Net, with that girl from the bus.
Reply With Quote
  #8 (permalink)  
Old 05-27-2009, 12:22 PM
hdawg's Avatar
Proprietor
 
Join Date: Nov 2008
Posts: 2,257
Blog Entries: 147
Default

CTRL log is prettier?
__________________
http://blog.port3101.org/hdawg/
Reply With Quote
  #9 (permalink)  
Old 05-28-2009, 10:22 PM
BES Administrator
 
Join Date: Feb 2009
Location: I come from a land down under where beer does flow and men chunder
Posts: 42
Default

I worked out the PID does not appear in the Controller log until the Controller requests the agent is restarted (after the worker threads have been blocked for 6 health checks).

Abe, as hdawg stated, the BES for GroupWise uses one messaging agent. Therefore in a BES for GroupWise environment the PID is not required & the Admin could just end the BlackBerry Agent.exe process.
Reply With Quote
Reply

Bookmarks

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/scripts-tools-hints-tricks/24-manually-restarting-single-messaging-agent.html
Posted By For Type Date
Blocked Worker Threads This thread Refback 10-18-2011 07:52 AM
Monitoring hung threads - BlackBerryForums.com : Your Number One BlackBerry Community This thread Refback 01-21-2010 07:35 PM
Re: [Bes-admins] Moving Users to a new Store on Exchange 2003 This thread Refback 10-18-2009 04:53 PM
Messaging Agent Instances - Question on Restart Procedure - BlackBerryForums.com : Your Number One BlackBerry Community This thread Pingback 06-10-2009 10:07 AM

Similar Threads
Thread Thread Starter Forum Replies Last Post
BlackBerry Messaging Agent 1 failed to start. Error code 5305 gmilne67 Port 3101: The BES Admin Bar & Grill 5 02-10-2010 01:51 AM
KB04772 - Mailbox move repeatedly detected in the BlackBerry Messaging Agent log hdawg Featured BlackBerry KB Articles 0 08-23-2009 09:05 PM
KB17896 - Increased log size seen in the messaging agent logs caused by invalid ... hdawg Featured BlackBerry KB Articles 0 07-22-2009 04:23 PM
KB15207 - Controller missing heartbeats for the Messaging Agent ... hdawg Featured BlackBerry KB Articles 0 06-16-2009 11:42 AM
KB10988 - Messages are lost after BlackBerry Messaging Agent login (GroupWise) Si Featured BlackBerry KB Articles 0 02-16-2009 04:26 AM


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


 

SEO by vBSEO 3.3.2 PL2