Announcement Announcement Module
No announcement yet.
Thread error - using Spring, CommonJ, Quartz Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Thread error - using Spring, CommonJ, Quartz


    I'm trying to set up Spring to use Quartz - but restrict Quartz's creation of threads by using CommonJ's WorkManagerTaskExecutor class. I can get Spring and Quartz to work by themselves, but when I add the WorkManagerTaskExecutor in.....I get the following error:

    [21/05/08 11:06:25:889 EST] 00000020 SystemErr R Exception in thread "QuartzScheduler_QuartzSchedulerThread" java.lang.AbstractMethodError: org/quartz/spi/ThreadPool.blockForAvailableThreads()I
    [21/05/08 11:06:25:889 EST] 00000020 SystemErr R at

    My spring configuration is as follows:

    <bean id="testJob" class="no.bekk.boss.commonj.TestJob"/>

    <bean id="jobDetail" class="org.springframework.scheduling.quartz.Metho dInvokingJobDetailFactoryBean">
    <property name="targetObject" ref="testJob" />
    <property name="targetMethod" value="execute" />
    <property name="concurrent" value="false" />

    <bean id="simpleTrigger" class="org.springframework.scheduling.quartz.Simpl eTriggerBean">
    <property name="jobDetail" ref="jobDetail" />
    <property name="startDelay" value="3000" />
    <property name="repeatInterval" value="2000" />

    <bean class="org.springframework.scheduling.quartz.Sched ulerFactoryBean">
    <property name="triggers">
    <ref bean="simpleTrigger" />
    <property name="taskExecutor" ref="taskExecutor" />

    <bean id="taskExecutor" class="org.springframework.scheduling.commonj.Work ManagerTaskExecutor">
    <property name="workManagerName" value="wm/default"/>
    <property name="resourceRef" value="false"/>

    Any ideas where I'm going wrong?


  • #2
    App versions

    If it helps......I'm using Spring 2.5, and Quartz 1.6.0, and am trying to deploy the app on to a Websphere Application Server (I have it set up as a web project).


    • #3
      Found the problem - I was incorrectly using jars from Spring 2.0 rather than Spring 2.5.....which was causing the issue.