Re: [quartznet:4119] Re: Triggers in database remain after removing from config

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: [quartznet:4119] Re: Triggers in database remain after removing from config

Ali Abbas
Have you got the answer? I also want to remove the Trigger from database

On Wednesday, 5 August 2009 20:57:12 UTC+4, Chris Eldredge wrote:
Oops, I missed this in the logs:

2009-08-05 12:51:07,783 [INFO ] Quartz.Impl.AdoJobStore.JobStoreSupport StoreTrigger note: volatile triggers are effectively non-volatile in a clustered environment.

So, next question: how do I remove volatile triggers in a cluster?  I can see how this would get very complicated.  Is it feasible to implement without shutting down the whole cluster?

On Wed, Jul 1, 2009 at 10:14 AM, Chris Eldredge <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="mWh30L6X6kEJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">chris.e...@...> wrote:
Durable is set to 0 (false).  Volatile had been set to false as well, but I have some stateful jobs.  I tried setting volatile to true on the triggers, but they still persist when I remove them from the spring config.


On Wed, Jul 1, 2009 at 5:00 AM, Marko Lahma <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="mWh30L6X6kEJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">marko...@...> wrote:

Have you set your jobs to be durable or triggers to be volatile?

-Marko

On Mon, Jun 22, 2009 at 7:51 PM, Chris Eldredge<<a href="javascript:" target="_blank" gdf-obfuscated-mailto="mWh30L6X6kEJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">chris.e...@gmail.com> wrote:
> No.  I'm using the Spring.NET integration to create and add triggers from
> xml context (using SchedulerFactoryObject).  I think maybe my question is
> more relevant on the Spring forums.
>
> Basically, if I remove a trigger from my spring configuration, I want the
> trigger in the database to go away on next startup.
>
> On Mon, Jun 22, 2009 at 11:22 AM, Ganesh Shivshankar
> <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="mWh30L6X6kEJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ganesh.sh...@...> wrote:
>>
>> Do you mean to say you had a RAMJObStore initially and now you have
>> changed it to AdoJobStore?
>>
>> On Mon, Jun 22, 2009 at 6:54 PM, Chris Eldredge <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="mWh30L6X6kEJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">chris.e...@...>
>> wrote:
>>>
>>> If I remove a job detail or a trigger from my configuration, but it was
>>> in the configuration before an upgrade, the old trigger and job detail will
>>> be loaded into the runtime.  How would GetTriggers tell me if a given
>>> trigger was loaded from the database or loaded from my configuration?
>>>
>>> On Sat, Jun 20, 2009 at 1:39 AM, Ganesh Shivshankar
>>> <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="mWh30L6X6kEJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ganesh.sh...@...> wrote:
>>>>
>>>> You could call the GetTriggers method on the IScheduler, and remove the
>>>> triggers that are no more in use, by looping or something.
>>>>
>>>> On Thu, Jun 18, 2009 at 3:34 AM, Chris Eldredge
>>>> <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="mWh30L6X6kEJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">chris.e...@...> wrote:
>>>>>
>>>>> I may not be understanding how database persistence is expected to
>>>>> work, but if I rename a trigger and upgrade my project, the old
>>>>> trigger and the new trigger will both end up running.
>>>>>
>>>>> Is there a way for Quartz to delete triggers that are not in the
>>>>> configuration (instead of loading them from the DB)?
>>>>>
>>>>> How are users supposed to remove/rename triggers with a persistent job
>>>>> store?
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
> >
>




--
You received this message because you are subscribed to the Google Groups "Quartz.NET" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/quartznet.
For more options, visit https://groups.google.com/d/optout.