Donate Share

XPlanner

The forum address has changed, you have been automatically redirected. Please update any bookmarks to use the new URL.

Subscribe

Unable to store Job with name:

You are viewing a single message from this topic. View all messages.

  1. 2004-05-20 19:29:14 UTC
    Xplanner would consistently fail to start with this:
    ----- Root Cause -----
    org.quartz.ObjectAlreadyExistsException: Unable to store Job with name: 'xplanner.datasampling.job' and group: 'xplanner', because one already exists with this identification.
    at org.quartz.simpl.RAMJobStore.storeJob(RAMJobStore.java:166)
    at org.quartz.simpl.RAMJobStore.storeJobAndTrigger(RAMJobStore.java:141)
    at org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.java:472)
    at org.quartz.impl.StdScheduler.scheduleJob(StdScheduler.java:212)
    at com.technoetic.xplanner.actions.XPlannerInitializationPlugin.initializeQuartz(XPlannerInitializationPlugin.java:67)
    at com.technoetic.xplanner.actions.XPlannerInitializationPlugin.init(XPlannerInitializationPlugin.java:37)
    at com.technoetic.xplanner.actions.XPlannerInitializationPlugin.init(XPlannerInitializationPlugin.java:29)
    at org.apache.struts.action.ActionServlet.initModulePlugIns(ActionServlet.java:1158)

    when accessing the login screen.

    I commented the xplanner.datasampling.job property and it starts. Has anyone seen this behavior?
< Previous | 1 | Next >

Add a Reply

This forum does not allow anonymous participation.

Log in to add a reply. Not registered? Create an account to participate and receive email updates when replies are posted to this topic.