Grouper Users - Open Discussion List

[Scott Koranda <>]

On Wed, Jul 9, 2014 at 2:02 PM, Chris Hyzer 
<>
 wrote:
> The webapp only looks in the loader config when doing status (doesn’t look 
> in DB for list of things to monitor)... Are you sure you are editing the 
> right file,

Yes, confirmed.

> browser is hitting the right node,

Yes, confirmed.

> service is really getting restarted etc?

Yes, confirmed.

Thanks,

Scott

>
> Thanks,
> Chris
>
> -----Original Message-----
> From: Scott Koranda 
> [mailto:]
> Sent: Wednesday, July 09, 2014 2:58 PM
> To: Chris Hyzer
> Cc: grouper-users
> Subject: Re: [grouper-users] deleted loader job causes monitoring servlet 
> to throw 500
>
> Hi,
>
> I have bounced the servlet webapp (the entire container actually)
> twice since restarting the loader. It has not changed the behavior.
>
> Thanks,
>
> Scott
>
> On Wed, Jul 9, 2014 at 1:55 PM, Chris Hyzer 
> <>
>  wrote:
>> Bounce the status servlet webapp?  Note, in 2.2 you shouldn’t need to 
>> bounce when changing most config information...
>>
>> Thanks,
>> Chris
>>
>> -----Original Message-----
>> From: 
>> 
>>  
>> [mailto:]
>>  On Behalf Of Scott Koranda
>> Sent: Wednesday, July 09, 2014 1:43 PM
>> To: grouper-users
>> Subject: [grouper-users] deleted loader job causes monitoring servlet to 
>> throw 500
>>
>> Hi,
>>
>> I edited grouper-loader.properties to delete a loader job that is no
>> longer needed and then ran
>>
>> DELETE FROM grouper_change_log_consumer WHERE name = 'name01';
>>
>> and restarted the loader.
>>
>> The monitoring servlet, however, continues to complain that it cannot
>> find a recent success for that loader job.
>>
>> What do I need to do so that the monitor will no longer look for any
>> details of that deleted loader job?
>>
>> Thanks,
>>
>> Scott