[Building Sakai] Delayed Announcement Email Notification

[Matthew Jones]

Right, it looks like every startup, the init() method tries first unschedule
the job, then reschedule it to run forever every
"SCHEDULED_INVOCATION_RUNNER_DEFAULT_INTERVAL" (which is defined as 600
seconds, so 10 minutes). On the systems I'm looking at it's setup correctly.

I'm not sure what cases could cause the try/catch to fail though and cause
a SchedulerException.

On Thu, Oct 13, 2011 at 4:03 PM, Chris Ribble <cribble at uwindsor.ca> wrote:

> After checking the logs and I only have one instance of that error and it
> was 3 days before I started trying to run the quartz job. That seems really
> odd.
>
> If I am reading your first sentence correctly, I shouldn't have to setup
> the Quartz job? ScheduledInvocationManager should run on its own?
>
>
>
> From:        Matthew Jones <jonespm at umich.edu>
> To:        Chris Ribble <cribble at uwindsor.ca>
> Cc:        sakai-dev at collab.sakaiproject.org
> Date:        10/13/2011 03:57 PM
> Subject:        Re: [Building Sakai] Delayed Announcement Email
> Notification
> Sent by:        jonespm at gmail.com
> ------------------------------
>
>
>
> It looks like that should schedule itself in the init method otherwise
> throw an error. All of the issues that you describe look to be fixed. Do you
> see this error "failed to schedule" in the logs?
>
>
> ./scheduler-component-shared/src/java/org/sakaiproject/component/app/scheduler/ScheduledInvocationManagerImpl.java
>                  public void init() {
>                                  LOG.info("init()");
>                       try {
>                           registerScheduledInvocationRunner();
>                        } catch (SchedulerException e) {
>                           LOG.error("failed to schedule
> ScheduledInvocationRunner job", e);
>                        }
>                     }
>
>
>
> On Thu, Oct 13, 2011 at 3:32 PM, Chris Ribble <*cribble at uwindsor.ca*<cribble at uwindsor.ca>>
> wrote:
> Hi everyone,
>
> In our 2.7.1 instance we have noticed that when setting an announcement to
> be hidden until a later date and selecting the email notification to go out,
> nothing is sent upon the un-hide of the announcement. I have searched for
> some documentation or a JIRA ticket about this issue and found some
> information but I can't quite get it to work. So far, I have figured out
> that I need to get the ScheduledInvocationRunner quartz job to run on a
> regular basis. I set that up by adding the job in the job scheduler tool on
> the admin workspace and then setting a Cron trigger for every 5 minutes. I
> waited for a while and nothing ever happened. I ran the job and my email was
> sent but any subsequent emails were not mailed out. I "somehow" finally got
> the job to run on a regular basis and everything was working fine. I decided
> to restart the instance to see what would happen and when it came back up
> the ScheduledInvocationRunner was not running. I need it to auto start when
> the instance comes back online.
>
> Am I headed in the right direction with this? Is there anything special I
> need to do to get this working properly?
>
> Thanks
> Chris
>
> Chris Ribble
> LMS Application Developer
> Information Technology Services
> University of Windsor
> _______________________________________________
> sakai-dev mailing list*
> **sakai-dev at collab.sakaiproject.org* <sakai-dev at collab.sakaiproject.org>*
> **http://collab.sakaiproject.org/mailman/listinfo/sakai-dev*<http://collab.sakaiproject.org/mailman/listinfo/sakai-dev>
>
> TO UNSUBSCRIBE: send email to *
> sakai-dev-unsubscribe at collab.sakaiproject.org*<sakai-dev-unsubscribe at collab.sakaiproject.org>with a subject of "unsubscribe"
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20111013/a1d9b6c0/attachment.html