[
https://issues.apache.org/jira/browse/QUARKS-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289937#comment-15289937
]
Daniel John Debrunner commented on QUARKS-180:
----------------------------------------------
Fair point on the JobMXBean, but someone has to remove it at some point
otherwise it's a memory leak
But I wasn't clear enough on the state issue. After the job is closed
job.getState() continues to return RUNNING.
> 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
(v6.3.4#6332)
