On 29/08/2012 13:34, Bob Lannoy wrote: > Hi Francesco, > > I'm still somewhat worried about the notification system. > I just had the case where the notification was not sent. > It was in the "tasks" tab. In the debug log I saw the notificationJob > waking up and sleeping again several times without picking up the > task. > > It looks like the problem I had before where it kept sending the > notification even if the status = SENT, although now it's the other > way around. > When I tried to reproduce the problem, it sent out the notification. > > Is there some sort of caching mechanism that could cause this > behaviour (i.e. not seeing tasks or thinking the task wasn't excuted)? > I'm sorry that I do not possess more detailed info on this. > best regards
Hi Bob, there is no particular caching involved in the notification system: it's only basically the NotificationJob class running every 2 minutes, picking up NotificationTasks with 'executed' == 0. (this was actually the change since SYNCOPE-54). Don't worry about reporting your issues here: having people testing new features in their implementation is a great thing for OSS projects like as Syncope ;-) Regards. > On 29 August 2012 10:14, Francesco Chicchiriccò <[email protected]> wrote: >> On 29/08/2012 10:09, Bob Lannoy wrote: >>> Hi Francesco, >>> >>> strangely enough, in my case it only works when I put it on "ALL". >>> For NONE, SUMMARY and FAILURES it keeps sending mails. >> Added your report as comment to SYNCOPE-192. >> >>> On 29 August 2012 10:02, Francesco Chicchiriccò <[email protected]> wrote: >>>> Hi Bob, >>>> I've just been able to reproduce this problem with a fresh overlay >>>> generated from 1.0.0-incubating archetype. >>>> >>>> If you instead set the trace level to anything but NONE everything works >>>> fine. >>>> I've opened SYNCOPE-192 for this. >>>> >>>> Thanks for reporting. >>>> Regards. -- Francesco Chicchiriccò ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member http://people.apache.org/~ilgrosso/
