Re: JavaMonitor to start a blocking application?
Re: JavaMonitor to start a blocking application?
- Subject: Re: JavaMonitor to start a blocking application?
- From: Jesse Tayler <email@hidden>
- Date: Tue, 09 Oct 2018 07:46:46 -0400
Why not just start the instance in your startup script and blow WO off —
I suspect long tasks may prevent the heartbeat and that might be hard to run,
otherwise, there’s no trouble with monitor starting and app and leaving it
alone…
I’m not sure about backgrounding tasks, but I’m sure it would not be that hard
to get working if it really doesn’t throw heartbeats in the first place which I
don’t know if it does or not.
> On Oct 9, 2018, at 6:41 AM, John Pollard <email@hidden> wrote:
>
> Hello WOers,
> I use JavaMonitor for a number of web apps just fine.
> I have another app that is a WO app but it isn’t an event driven web app;
> when it runs is just gets on with a never ending task.
> Is there an easy way to use JavaMonitor to just start this when the machine
> first boots up, but not try to check it is still alive (no heartbeats)?
> This would be a bit easier than using cron for me.
> I suppose ideally I would like the app to be responsive to JavaMonitor so it
> can be shown to be alive / be killed & restarted, whilst also doing its never
> ending task. Is it possible to do this with a background thread in my
> ERXApplication class or will that now work nicely with EOF etc.
> Thanks
> John
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden