Re: lifecycle exceptions

This has happened to use once or twice.  We are not sure why some
assumptions in the db was not there.  Either it was introduced while
putting in development or code or something.

Anyway looking at the root cause of the exception and fixing some rows
or columns on the db where the solutions that we did.

Are there cases where the site is under heavy load there seems to be a
state during a lifecycle run when a content item is it bad state?  We
seem to have encountered this but unable to reproduce it.


Jun

On Mon, 2004-04-26 at 16:07, Alan Pevec wrote:
> Hi
> 
> a quick fix would be to wrap Scheduler.run call in 
> c.a.cms.lifecycle.SchedulerTask
> with a try-catch(Throwable) block. Log the exception in the catch block, 
> so that it does not fail silently.
> 
> Hope this helps,
> 
> Alan Pevec
> 
> 
> Thomas, Mary wrote:
> 
> >Hi
> >Noticed that lifecycle in redhat cms breaks when an assertion throws the
> >exception and it is not caught.
> >And then one has to restart the server . This is not acceptable in
> >production environment.
> >Could you offer recommendations/modifications wherein errors are caught and
> >does not break the lifecycle during publishing of an item.
> >
> >Thanks
> >Mary
> >
> >public class AssertionError extends Error {
> >
> >    public AssertionError(String msg) {
> >        super(msg);
> >    }
> >}
> >  
> >
> 


-- 
Redhat-ccm-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/redhat-ccm-list
Archives: https://www.redhat.com/pipermail/redhat-ccm-list/