You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Martin Gross <m....@evolt.de> on 2004/01/29 18:20:05 UTC
Best Practice for long running tasks with status check
Hi,
I need to start an long running task by a struts action which will
run for maybe half an hour. I dont want the action to run for half
an hour. It should start the task and then respond that the task has
been started. Also it should be possible to check the
status of the task and see for example how many elements have already
been processed.
What would be the best practice to do this? Code examples would be
also appreciated.
Regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re[2]: Best Practice for long running tasks with status check
Posted by Martin Gross <m....@evolt.de>.
hi marco,
thanks for the information. I will check JMX.
Regards,
Martin
> Hi,
> My 2 cents..
> For the first half of your query, you can use JMX timer. Best way to do
> that
> Is to write an MBean that register itself with the timer and eventually
> receive notifications.
> You can make so that the 'object htat needs to be updated all the time'
> is
> A listener to notifications sent from the Timer. This 'object' should be
> inside your Mbean, and you can write a method on your MBean that returns
> the
> Current status.
> Ok, maybe I am giving u too much info, but please check JMX and the
> Timer service to see if it suits you
> Regards
> marco
> -----Original Message-----
> From: Martin Gross [mailto:m.gross@evolt.de]
> Sent: 29 January 2004 17:20
> To: Struts Users Mailing List
> Subject: Best Practice for long running tasks with status check
> Hi,
> I need to start an long running task by a struts action which will
> run for maybe half an hour. I dont want the action to run for half
> an hour. It should start the task and then respond that the task has
> been started. Also it should be possible to check the
> status of the task and see for example how many elements have already
> been processed.
> What would be the best practice to do this? Code examples would be
> also appreciated.
> Regards,
> Martin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-user-help@jakarta.apache.org
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
RE: Best Practice for long running tasks with status check
Posted by Marco Mistroni <mm...@waersystems.com>.
Hi,
My 2 cents..
For the first half of your query, you can use JMX timer. Best way to do
that
Is to write an MBean that register itself with the timer and eventually
receive notifications.
You can make so that the 'object htat needs to be updated all the time'
is
A listener to notifications sent from the Timer. This 'object' should be
inside your Mbean, and you can write a method on your MBean that returns
the
Current status.
Ok, maybe I am giving u too much info, but please check JMX and the
Timer service to see if it suits you
Regards
marco
-----Original Message-----
From: Martin Gross [mailto:m.gross@evolt.de]
Sent: 29 January 2004 17:20
To: Struts Users Mailing List
Subject: Best Practice for long running tasks with status check
Hi,
I need to start an long running task by a struts action which will
run for maybe half an hour. I dont want the action to run for half
an hour. It should start the task and then respond that the task has
been started. Also it should be possible to check the
status of the task and see for example how many elements have already
been processed.
What would be the best practice to do this? Code examples would be
also appreciated.
Regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org