You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2014/06/02 11:31:04 UTC

[jira] [Resolved] (KARAF-2269) Servicemix Specs Activator/OsgiLocator Broken due to KARAF-2136

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

Guillaume Nodet resolved KARAF-2269.
------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.3.2)
                       (was: 3.0.0)
                   2.3.6
                   3.0.2
                   4.0.0

> Servicemix Specs Activator/OsgiLocator Broken due to KARAF-2136
> ---------------------------------------------------------------
>
>                 Key: KARAF-2269
>                 URL: https://issues.apache.org/jira/browse/KARAF-2269
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 2.3.1
>            Reporter: Kurt Westerfeld
>            Assignee: Jean-Baptiste Onofré
>            Priority: Critical
>             Fix For: 2.4.0, 4.0.0, 3.0.2, 2.3.6
>
>
> Bug https://issues.apache.org/jira/browse/KARAF-2136, KARAF-2136, "fixes" a misspelled configuration setting.  Unfortunately, the 1.9.0 version of specs, for example, JSR-311 (JAX-RS), stop working when this fix is in place.  The breakage is due to an invalid timeout value setting of zero (0).  A workaround is to simply set the value to non-zero, such as 100.
> What is happening is that the OsgiLocator provided by Servicemix specs locator, is having a timeout of 0 set.  When this is the case, no lookups occur whatsoever in its internal registry.  As a result, ClassNotFoundExceptions occur, when a usage of this class attempts to lookup any bundle that provides an implementation.



--
This message was sent by Atlassian JIRA
(v6.2#6252)