edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Victor Dogaru (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QUARKS-180) Calling stateChange(CLOSE) on JobMXBean does not change its state fully.
Date Wed, 18 May 2016 21:50:12 GMT

    [ https://issues.apache.org/jira/browse/QUARKS-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289913#comment-15289913

Victor Dogaru commented on QUARKS-180:

See DirectJobTest.jobPeriodicSource():

EtiaoJob.stateChange(Action.CLOSE) calls 
   Executable.close()  calls 
      Executable.invokeAction() calls
         job.onActionComplete(); // sets job.currentState to CLOSED


Closing the job will not unregister the associated JobMXBean from the ControlService.  
- Is this something which should the Job implementation do when it changes state to CLOSED?
- Should this be asynchronously done N seconds after the job is CLOSED?
- Would a ControlService client want to get the control of a closed job?

> Calling stateChange(CLOSE) on JobMXBean does not change its state fully.
> ------------------------------------------------------------------------
>                 Key: QUARKS-180
>                 URL: https://issues.apache.org/jira/browse/QUARKS-180
>             Project: Quarks
>          Issue Type: Bug
>          Components: Runtime
>            Reporter: Daniel John Debrunner
> Trying to close a Job through its JobMXBean I'm not sure the process is being completed.
JobMXBean .stateChange just calls job.stateChange..
> I can trace it calling Executable.close() but I can't see any code that then changes
the state of the job and removes its JobMXBean.

This message was sent by Atlassian JIRA

View raw message