[jira] Reopened: (SMX4KNL-140) GShell commands references not cleaned up when bundle uninstalled

["Guillaume Nodet (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/SMX4KNL-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet reopened SMX4KNL-140:
-------------------------------------


The commands are correctly removed when the bundle is removed, however if the a new version of the bundle is installed again, the commands fail to work (though they are correctly registered):

{code}
ERROR CommandLineExecutionFailed: org.springframework.osgi.service.ServiceUnavailableException: service with id=[92] unavailable
{code}

The problem comes from the meta: vfs handler which keeps a reference to the old osgi service.  It may be just a matter of refreshing the cache of vfs, not sure though

> GShell commands references not cleaned up when bundle uninstalled
> -----------------------------------------------------------------
>
>                 Key: SMX4KNL-140
>                 URL: https://issues.apache.org/activemq/browse/SMX4KNL-140
>             Project: ServiceMix Kernel
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>            Reporter: Chris Custine
>            Assignee: Guillaume Nodet
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> When a gshell command bundle is updated or uninstalled/installed, there is a reference to the previously installed command service somewhere.  When you rn the command after the resinstall or update, you get something like the following error:
> smx@cgcmac1:sigar> help
> ERROR CommandLineExecutionFailed: org.apache.geronimo.gshell.command.CommandException: org.springframework.osgi.service.ServiceUnavailableException: service with id=[72] unavailable
> In this case, service ID 72 refers to the original service for this command.
> I assume that the command registry has a stale reference to the original service.  This isn't a major issue since reinstallation of command bundles will mostly be a developer issue, but documenting it here as a reminder.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.