[
https://issues.apache.org/jira/browse/QUARKS-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347565#comment-15347565
]
ASF GitHub Bot commented on QUARKS-180:
---------------------------------------
GitHub user vdogaru opened a pull request:
https://github.com/apache/incubator-quarks/pull/150
QUARKS-180 test should assert state of jobMbean
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vdogaru/incubator-quarks QUARKS-180-vdogaru
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-quarks/pull/150.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #150
----
commit 0d1e52c358c950150fc9a2d2c877de49510e18cc
Author: Victor Dogaru <[email protected]>
Date: 2016-06-24T01:57:31Z
QUARKS-180 test should assert state of jobMbean
----
> 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)
