[
https://issues.apache.org/jira/browse/QUARKS-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352074#comment-15352074
]
Victor Dogaru commented on QUARKS-180:
--------------------------------------
See
[previous|https://issues.apache.org/jira/browse/QUARKS-180?focusedCommentId=15337013&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15337013]
comment:
* A new issue [QUARKS-215|https://issues.apache.org/jira/browse/QUARKS-215]
tracks issue: "How to dispose of closed Job controls".
* PR https://github.com/apache/incubator-quarks/pull/150 updates
IotProviderTest to correctly assert the state of the submitted job.
Marking this issue as fixed.
> 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
> Assignee: Victor Dogaru
>
> 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
(v6.3.4#6332)
