You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2012/06/11 18:05:43 UTC

[jira] [Resolved] (FELIX-3414) BundleException: Unable to acquire global lock for resolve

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

Guillaume Nodet resolved FELIX-3414.
------------------------------------

       Resolution: Fixed
    Fix Version/s: fileinstall-3.2.4
         Assignee: Guillaume Nodet

URL: http://svn.apache.org/viewvc?rev=1348921&view=rev

Simple workaround until we can upgrade to the osgi wiring api.
If this is not sufficient, we may want to introduce a flag to disable the refresh completely.
                
> BundleException: Unable to acquire global lock for resolve
> ----------------------------------------------------------
>
>                 Key: FELIX-3414
>                 URL: https://issues.apache.org/jira/browse/FELIX-3414
>             Project: Felix
>          Issue Type: Bug
>          Components: File Install
>    Affects Versions: fileinstall-3.2.0
>         Environment: Windows 7. org.apache.felix.framework:4.0.2
>            Reporter: Leon
>            Assignee: Guillaume Nodet
>             Fix For: fileinstall-3.2.4
>
>
> After trying to use latest org.apache.felix.fileinstall-3.2.0 I always get the following error. The bundle that fails it not always the same. It changes.Downgrading back to org.apache.felix.fileinstall-3.1.10 always works fine.
> Installed C:\Users\user\install\versions\strategy-server-1.0-SNAPSHOT\instances\1-a\strategies\example-1.0-SNAPSHOT.jar
> ...
> Error while starting bundle: file:/C:/Users/user/install/versions/strategy-server-1.0-SNAPSHOT/instances/1-a/strategies/example-1.0-SNAPSHOT.jar: org.osgi.framework.BundleException: Unable to acquire global lock for resolve.
> org.osgi.framework.BundleException: Unable to acquire global lock for resolve.
> 	at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3832)
> 	at org.apache.felix.framework.Felix.startBundle(Felix.java:1868)
> 	at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:944)
> 	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1232)
> 	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1206)
> 	at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:491)
> 	at org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:219)
> 	at org.apache.felix.fileinstall.internal.FileInstall.updated(FileInstall.java:247)
> 	at org.apache.felix.fileinstall.internal.FileInstall.start(FileInstall.java:150)
> 	at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:641)
> 	at org.apache.felix.framework.Felix.activateBundle(Felix.java:1977)
> 	at org.apache.felix.framework.Felix.startBundle(Felix.java:1895)
> 	at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1191)
> 	at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:295)
> 	at java.lang.Thread.run(Thread.java:662)
> [2012-03-29 23:24:37,788][INFO][FelixDispatchQueue][server.osgi.StrategyEngineHost] FrameworkEvent: org.apache.felix.framework [0] PACKAGES_REFRESHED null

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira