This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


Apr 20, 2015, 10:05 AM
26 Posts

Scheduled Agents stop working at midnight

  • Category: Application Development
  • Platform: Windows
  • Release: 9.0.1
  • Role: Administrator,Developer
  • Tags:
  • Replies: 6

Hello All,

I have a cluster of outgoing SMTP Servers which has erratically connection problems with a single customer system. Because of this connection problems, outgoing Mail get dead, but can be maually released with the "Resend selected dead Messages to originally intended Recipient" action.

But because this connection Problems can happen also at night and on Weekends I have created a scheduled Agent who does the job every ten minutes.

The Agent is located in the Server Mailboxes (mail1.box to mail3.box), I have added it to the mailbox.ntf on both servers. It is scheduled "More than once a day", Run every 10 minutes. With "Choose server when enabled".

The Agent works well, does what expected, but stops working every midnight.

In the Logs I can see the last Amgr entry at 23:5x and then nothing more. If I do a "Tell amgr sched" on the server Console it tells me that no Agents are currently scheduled. If I open the Designer, the agents are still active. Clicking "Disable" and a few seconds later "Enable" makes them run again. Until Midnight.

Has anybody seen something like this before?

 

 

Apr 20, 2015, 12:46 PM
326 Posts
Suggestions

I would suggest putting the agent in a another db and have it reach out to all the mail*.box on the server.  My guess is compact of the mail.box(s) screws up the scheduled agent.

Apr 20, 2015, 3:05 PM
26 Posts
Thanks for the suggestion

I will give it a try and post tomorrow if it was successfull.

Apr 20, 2015, 4:06 PM
326 Posts
Just realized

At 1 am it does a re cache of scheduled agents against all .nsf   Since you put the agent in .box it does not see it.   My suggestion of moving it to a .nsf will work 

Apr 20, 2015, 7:04 PM
145 Posts
What does your Server Record look like for Agent Manager Settings?
Apr 21, 2015, 2:03 AM
6 Posts
workaround

this happened to me before, archiving agents stopped working after midnight and i found out it was some agent refresh cache of some sort that domino runs at around midnight and because of other problems we were having with the server at that time (db problems caused by backup), i just configured an event handler to restart amgr when it sees the error (comes up right after midnight, which was an indication for us that the agents will stop running). so essentially, i was auto restarting amgr after midnight until our domino problem was fixed. 

Apr 21, 2015, 11:51 AM
26 Posts
You're right Barry

I placed the Agent in a .nsf as suggested and problems were gone.

Also good was the question for the server record. In the "Server Tasks/Agent Manager"-Tab we have an entry "Refresh agent cache" with a Value of "00:00". It seems to me that it refreshes all scheduling and doesn't look at the .box Files.

Thank you all for your replies and suggestions.


This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal