[
https://issues.apache.org/jira/browse/QUARKS-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15337013#comment-15337013
]
Victor Dogaru commented on QUARKS-180:
--------------------------------------
{{IotProviderTest.testIotProviderCloseApplicationDirect()}} starts two jobs:
First it creates a Topology containing a source of commands connected to a sink
of device events. The IotProvider submits the topology into job {{appStarter}}
with id "Job_2".
The event emitted by {{appStarter}} submits "AppOne", for which the test gets
the
{{jobMbean}}, which controls the appOne job with id "Job_3".
The test uses {{jobMbean}} to close the "AppOne" job, but the {{appStarter}}
job remains in running state. The application which submitted {{appStarter}}
should explicitly close it, otherwise the job will remain in the RUNNING state.
I believe the system behaves as expected. The fix I propose:
* Update the test to correctly assert the states of the two jobs.
* Create a separate JIRA task for the other issue: "How to dispose of closed
Job controls".
> 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)
