Hi Subhadeep, I see. Strange situation indeed, sounds like either a badly designed probe or a badly behaving app or both.
The strange part being that starting the application is always OK, even though SC (rather the Agents built by Agent builder) typically would probe the app at start time as well to make sure it really did start. It must be related to load, as you suggested. Badly designed app/probe or not, it would be good to have a knob in SC which can get you the behavior of getting the application into an errored/offline state if it keeps failing after successfully starting. I do not believe that today we have such a knob in SC, but perhaps someone else on the list would prove be happily wrong. -ashu Subhadeep Sinha wrote: > Hey Ashu, > > In my case the resource doesn't fail to start ever. The probe fails due to > some rough weather the application runs into after it is started and then SC > restarts the resource for retry_count times. It is then that the resource > enters a faulted/unmonitored state where probing is stopped. But the final > state of the resource is still "online". > > Thanks, > - Shubho.