Bug 895056 - Unable to use JDBCJobStore for ESB scheduler
Summary: Unable to use JDBCJobStore for ESB scheduler
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.3.0 GA
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-14 12:14 UTC by Martin Weiler
Modified: 2025-02-10 03:27 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:27:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Martin Weiler 2013-01-14 12:14:51 UTC
Description of problem:
Using the configuration properties at the <schedule-provider level>, I am trying to configure Quartz to use JDBCJobStore instead of RAMJobStore:


    <schedule-provider name="scheduler">
        <property name="org.quartz.dataSource.myds.jndiURL" value="java:/JBossESBDS"/>
        <property name="org.quartz.dataSource.myds.java.naming.factory.initial" value="org.jnp.interfaces.NamingContextFactory"/>
        <property name="org.quartz.dataSource.myds.java.naming.provider.url" value="jnp://127.0.0.1:1099"/>

        <property name="org.quartz.jobStore.class" value="org.quartz.impl.jdbcjobstore.JobStoreTX"/>
        <property name="org.quartz.jobStore.dataSource" value="myds"/>
        <property name="org.quartz.jobStore.driverDelegateClass" value="org.quartz.impl.jdbcjobstore.StdJDBCDelegate"/>			
        <cron-schedule scheduleid="cron-trigger" cronExpression="0 0 13 * * ?" />
    </schedule-provider>

The database schema already contains the Quartz tables.
  
Actual results:
Deploying an esb application with these settings is failing with a NotSerializableException:

org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Failed to start the scheduling job
	at org.jboss.soa.esb.listeners.lifecycle.AbstractScheduledManagedLifecycle.doStart(AbstractScheduledManagedLifecycle.java:179)
...

Caused by: org.jboss.soa.esb.schedule.SchedulingException: Failed to start scheduled job
	at org.jboss.soa.esb.schedule.SchedulerResource.start(SchedulerResource.java:110)
	at org.jboss.soa.esb.schedule.SchedulerJob.start(SchedulerJob.java:110)
	at org.jboss.soa.esb.listeners.lifecycle.AbstractScheduledManagedLifecycle.doStart(AbstractScheduledManagedLifecycle.java:175)
	... 58 more
Caused by: org.quartz.JobPersistenceException: Couldn't store job: org.jboss.soa.esb.listeners.lifecycle.AbstractScheduledManagedLifecycle$1 [See nested exception: java.io.NotSerializableException: org.jboss.soa.esb.listeners.lifecycle.AbstractScheduledManagedLifecycle$1]
	at org.quartz.impl.jdbcjobstore.JobStoreSupport.storeJob(JobStoreSupport.java:854)
	at org.quartz.impl.jdbcjobstore.JobStoreTX.storeJobAndTrigger(JobStoreTX.java:167)
	at org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.java:613)
	at org.quartz.impl.StdScheduler.scheduleJob(StdScheduler.java:238)
	at org.jboss.soa.esb.schedule.SchedulerResource.start(SchedulerResource.java:101)
	... 60 more

Expected results:
Quartz job is stored in the Quartz tables.

Comment 2 Red Hat Bugzilla 2025-02-10 03:27:16 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


Note You need to log in before you can comment on or make changes to this bug.