You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@tapestry.apache.org by Ilya Obshadko <il...@gmail.com> on 2014/06/27 09:19:58 UTC

service implementation reloading and background processes

I have a couple of services which use PeriodicExecutor to perform
background tasks.

When service implementation reloads in development mode, instantiated
background job isn't stopped. So, after implementation is reloaded, it
creates another background jobs while previous one still exists and
continues to run. What could you recommend to solve this problem?

Is there any explicit way to signal particular implementation that it's
about to be reloaded?

Thanks in advance.

-- 
Ilya Obshadko

Re: service implementation reloading and background processes

Posted by Ilya Obshadko <il...@gmail.com>.

Thanks! Exactly what I was looking for.


On Fri, Jun 27, 2014 at 6:30 PM, Dmitry Gusev <dm...@gmail.com>
wrote:

>
> http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/ioc/ReloadAware.html
>
> On Friday, June 27, 2014, Ilya Obshadko <il...@gmail.com> wrote:
>
> > I have a couple of services which use PeriodicExecutor to perform
> > background tasks.
> >
> > When service implementation reloads in development mode, instantiated
> > background job isn't stopped. So, after implementation is reloaded, it
> > creates another background jobs while previous one still exists and
> > continues to run. What could you recommend to solve this problem?
> >
> > Is there any explicit way to signal particular implementation that it's
> > about to be reloaded?
> >
> > Thanks in advance.
> >
> > --
> > Ilya Obshadko
> >
>
>
> --
> Dmitry Gusev
>
> AnjLab Team
> http://anjlab.com
>



-- 
Ilya Obshadko

Re: service implementation reloading and background processes

Posted by Dmitry Gusev <dm...@gmail.com>.

http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/ioc/ReloadAware.html

On Friday, June 27, 2014, Ilya Obshadko <il...@gmail.com> wrote:

> I have a couple of services which use PeriodicExecutor to perform
> background tasks.
>
> When service implementation reloads in development mode, instantiated
> background job isn't stopped. So, after implementation is reloaded, it
> creates another background jobs while previous one still exists and
> continues to run. What could you recommend to solve this problem?
>
> Is there any explicit way to signal particular implementation that it's
> about to be reloaded?
>
> Thanks in advance.
>
> --
> Ilya Obshadko
>


-- 
Dmitry Gusev

AnjLab Team
http://anjlab.com