Database isn't updated with Synchronisation task state

[we...@dj-wasabi.nl]

Hi,

We have an Syncope instance running which has several Synchronisation 
Tasks. Some of them are running fine and I can see the logentries in the 
database (TaskExec). I can see in the syncope-console in the histtory 
that there are jobs executed.
But we have also several tasks which are running, but they do not update 
the database (TaskExec). We checked it by setting the loglevel to debug 
and see a lot of logging in core-connid.log logfile. Some of the 
synchronisation tasks do only update the database when the 
synchronisation went into error.

We are running Syncope 1.1.5 and use MySQL as database.
Any suggestions for solving this issue?

Kind regards,
Werner

Re: Database isn't updated with Synchronisation task state

[we...@dj-wasabi.nl]

Hi,

Thank you for making time to answer my e-mail.

I do have set the "Synchronization trace level" to "FAILURES". So I only 
have to set it to "SUMMARY" and I would see also the success jobs?
What about the others:
- Create trace level
- Update trace level
- Delete trace level

These are set to "FAILURES" as wel, so also set these to "SUMMARY"? What 
do they update?

Kind regards,
Werner


On 2015-04-16 12:41, Francesco Chicchiriccò wrote:
> On 15/04/2015 10:18, werner@dj-wasabi.nl wrote:
>> Hi,
>> 
>> We have an Syncope instance running which has several Synchronisation 
>> Tasks. Some of them are running fine and I can see the logentries in 
>> the database (TaskExec). I can see in the syncope-console in the 
>> histtory that there are jobs executed.
>> But we have also several tasks which are running, but they do not 
>> update the database (TaskExec). We checked it by setting the loglevel 
>> to debug and see a lot of logging in core-connid.log logfile.
> 
> You probably need to create a new log appender for quartz, and to set
> such appender to DEBUG (in the logback.xml file, since you are on
> 1.1.X).
> 
>> Some of the synchronisation tasks do only update the database when the 
>> synchronisation went into error.
> 
> This probably depends on the settings that you put on the specific
> resource under the "Synchronization trace level" entry.
> 
>> We are running Syncope 1.1.5 and use MySQL as database.
>> Any suggestions for solving this issue?
> 
> There is plan to enhance the control over running Quartz jobs as per
> SYNCOPE-660 [1].
> 
> HTH
> Regards.
> 
> [1] https://issues.apache.org/jira/browse/SYNCOPE-660

Re: Database isn't updated with Synchronisation task state

[Francesco Chicchiriccò <il...@apache.org>]

On 15/04/2015 10:18, werner@dj-wasabi.nl wrote:
> Hi,
>
> We have an Syncope instance running which has several Synchronisation 
> Tasks. Some of them are running fine and I can see the logentries in 
> the database (TaskExec). I can see in the syncope-console in the 
> histtory that there are jobs executed.
> But we have also several tasks which are running, but they do not 
> update the database (TaskExec). We checked it by setting the loglevel 
> to debug and see a lot of logging in core-connid.log logfile.

You probably need to create a new log appender for quartz, and to set 
such appender to DEBUG (in the logback.xml file, since you are on 1.1.X).

> Some of the synchronisation tasks do only update the database when the 
> synchronisation went into error.

This probably depends on the settings that you put on the specific 
resource under the "Synchronization trace level" entry.

> We are running Syncope 1.1.5 and use MySQL as database.
> Any suggestions for solving this issue?

There is plan to enhance the control over running Quartz jobs as per 
SYNCOPE-660 [1].

HTH
Regards.

[1] https://issues.apache.org/jira/browse/SYNCOPE-660

-- 
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC
http://people.apache.org/~ilgrosso/