[ 
https://issues.apache.org/jira/browse/SYNCOPE-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò resolved SYNCOPE-460.
--------------------------------------------

    Resolution: Fixed

[~wimmelg], thanks for your analysis, it pointed me in the right direction for 
investigation.

Basically, the observed delay of {{QuartzSchedulerThread}} seems to be due to 
the way how the trigger is looked up (in Quartz).
In Quartz's {{JobStoreSupport#acquireNextTriggers}}, in fact, the 
non-transactional DataSource is used for this purpose; since 
{{schedulingContext.xml}} does not specify {{nonTransactionalDataSource}}, the 
{{transactionalDataSource}} is used instead both for transactional and 
non-transactional operations.

This, together with {{READ_COMMITTED}}, leads to the observed delay (in fact, 
when defining an additional non-transactional DataSource, things go smoothly).
Anyway, this does not looks like a general production issue, but rather an 
integration test glitch: for this reason I have added a further Quartz 
parameter in {{schedulingContext.xml}}:
{code}
<prop 
key="org.quartz.scheduler.idleWaitTime">${quartz.scheduler.idleWaitTime:30000}</prop>
{code}
and set things in test's {{persistence.properties}} in order to instruct the 
{{QuartzSchedulerThread}} to wake up every 5 (instead of default 30) seconds.

> Default datasource uses BasicDataSource
> ---------------------------------------
>
>                 Key: SYNCOPE-460
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-460
>             Project: Syncope
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.1.5
>            Reporter: Oliver Wulff
>            Assignee: Francesco Chicchiriccò
>            Priority: Minor
>             Fix For: 1.1.6, 1.2.0
>
>         Attachments: patch.git, syncope-460_20121220.patch
>
>
> Replace org.springframework.jdbc.datasource.DriverManagerDataSource by 
> org.apache.commons.dbcp.BasicDataSource as recommended by spring:
> http://docs.spring.io/spring/docs/current/spring-framework-reference/html/jdbc.html#jdbc-connections
> Make property "isolationLevelName" configurable in persistence.properties 
> with default ISOLATION_READ_COMMITTED
> See full discussion in dev@ ML: http://markmail.org/message/33aheawb5irzl3xc



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to