[
https://issues.apache.org/jira/browse/MUSE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Waeldrich updated MUSE-307:
----------------------------------
Description: If a resource in a service group is destroyed, the destruction
of the resource fails. In the current trunk implementation the
SimpleServiceGroup#resourceRemoved() method tries to remove the service group
entry twice, by calling removeEntry(entry) and entry.shutdown().
entry.shutdown() implicitly calls removeEntry(entry) a second time, when the
resource is already removed. A patch for this issue is attached. (was: If a
resource in a service group is destroyed, the destruction of the resource
fails. In the current trunk implementation the
SimpleServiceGroup#resourceRemoved() method tries to remove the service group
entry twice, by calling removeEntry(entry) and entry.shutdown().
entry.shutdown() implicitly calls removeEntry(entry) a second time, when the
resource is already removed. A patch for this issue is applied.)
> destruction of a resource in a service group fails
> --------------------------------------------------
>
> Key: MUSE-307
> URL: https://issues.apache.org/jira/browse/MUSE-307
> Project: Muse
> Issue Type: Bug
> Components: WSRF WSSG ServiceGroup
> Affects Versions: 2.2.1, 2.3.0
> Reporter: Oliver Waeldrich
> Assignee: Dan Jemiolo
> Attachments: patch.txt
>
>
> If a resource in a service group is destroyed, the destruction of the
> resource fails. In the current trunk implementation the
> SimpleServiceGroup#resourceRemoved() method tries to remove the service group
> entry twice, by calling removeEntry(entry) and entry.shutdown().
> entry.shutdown() implicitly calls removeEntry(entry) a second time, when the
> resource is already removed. A patch for this issue is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
