[
https://issues.apache.org/jira/browse/GERONIMO-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-4495:
-----------------------------------
Patch Info: [Patch Available]
Affects Version/s: 2.1.3
Fix Version/s: 2.2
2.1.4
Assignee: Donald Woods
> Invoking stop method on a gbean whose instancestate is destoryed caused that
> gbean in the stopping state
> --------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-4495
> URL: https://issues.apache.org/jira/browse/GERONIMO-4495
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: kernel
> Affects Versions: 2.1.3, 2.2
> Reporter: Ivan
> Assignee: Donald Woods
> Fix For: 2.1.4, 2.2
>
> Attachments: Geronimo-4495.patch
>
>
> If one gbean's instancestate is in the destoryed state and its gbeanstate is
> in the failed state. Then we invoke the stop method on that gbean, then the
> gbean will in the stopping state.
> So, we never could start it by calling the startRecursive() method.
> Shall the stop method returns directly when the gbean state is in failed
> state ?
> Thanks for giving a comment !
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
