[
https://issues.apache.org/jira/browse/DOSGI-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amichai Rothman updated DOSGI-177:
----------------------------------
Description:
Sometimes TopologyManagerImport receives more than one endpointAdded event for
the same endpoint and filter. Currently this causes it to add the endpoint
multiple times to an internal list. However when the endpoint is removed, only
one endpointRemoved event is triggered, one instance is removed from the list,
and the other copies remain. The rest of the code treats this as the endpoint
still being available, which is what the clients see as well (the import is
never closed).
The patch simply adds a check so that the endpoint will not be added to the
list if it's already there. It also removes empty import lists when all imports
are removed, preventing a leak.
was:
Sometimes TopologyManagerImport receives more than one endpointAdded event for
the same endpoint and filter. Currently this causes it to add the endpoint
multiple times to an internal list. However when the endpoint is removed, only
one endpointRemoved event is triggered, one instance is removed from the list,
and the other copies remain. The rest of the code treats this as the endpoint
still being available, which is what the clients see as well (the import is
never closed).
The patch simply adds a check so that the endpoint will not be added to the
list if it already there. It also removes empty import lists when all imports
are removed, preventing a leak.
> stopped services still appear as available to clients
> -----------------------------------------------------
>
> Key: DOSGI-177
> URL: https://issues.apache.org/jira/browse/DOSGI-177
> Project: CXF Distributed OSGi
> Issue Type: Bug
> Components: DSW
> Affects Versions: 1.5
> Reporter: Amichai Rothman
> Attachments: fix_services_not_removed.diff
>
>
> Sometimes TopologyManagerImport receives more than one endpointAdded event
> for the same endpoint and filter. Currently this causes it to add the
> endpoint multiple times to an internal list. However when the endpoint is
> removed, only one endpointRemoved event is triggered, one instance is removed
> from the list, and the other copies remain. The rest of the code treats this
> as the endpoint still being available, which is what the clients see as well
> (the import is never closed).
> The patch simply adds a check so that the endpoint will not be added to the
> list if it's already there. It also removes empty import lists when all
> imports are removed, preventing a leak.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
