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

Mark Adamcin updated SLING-3057:
--------------------------------

    Environment: RHEL 6, Adobe CQ 5.6.1

I've added the details for the environment where this was observed. The 
uninstallation is occurring as part of CRX package deployments to staging and 
production environments, which involves uninstalling existing releases prior to 
installing new releases, in order to force the rebinding of OSGi configs when 
bundle locations change.
                
> Ghosted reference to dependent bundle after .java script compilation prevents 
> complete uninstallation
> -----------------------------------------------------------------------------------------------------
>
>                 Key: SLING-3057
>                 URL: https://issues.apache.org/jira/browse/SLING-3057
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting Java 2.0.6
>         Environment: RHEL 6, Adobe CQ 5.6.1
>            Reporter: Mark Adamcin
>
> It appears that a lock is established on the cache directory of any bundle 
> which is imported by a compiled .java script that prevents complete 
> uninstallation of the dependent bundle, even after reinstallation of the 
> bundle. 
> The reinstalled bundle creates a new distinct cache folder under 
> launchpad/felix, while the uninstalled cache folder remains write protected.
> Subsequent recompilation of the .java script after reinstallation of the 
> bundle fails due to missing .class files, with the message: "<some class> 
> resolves to a package.". 
> Restarting the Dynamic ClassLoader Support bundle or the Scripting Java 
> bundle fails to force a recompilation using the newly reinstalled bundle, 
> however a complete application restart will force the old cache folder to be 
> garbage collected, and the .java script will compile correctly.

--
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

Reply via email to