karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Reopened] (KARAF-2269) Servicemix Specs Activator/OsgiLocator Broken due to KARAF-2136
Date Wed, 19 Mar 2014 17:35:43 GMT

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

Jean-Baptiste Onofré reopened KARAF-2269:
-----------------------------------------

      Assignee: Jean-Baptiste Onofré  (was: Freeman Fang)

With the upgrade to ServiceMix Specs 2.4.0 (which contains fix about timeout), we can set
the default timeout to 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.3.2, 2.4.0, 3.0.0
>
>
> 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)

Mime
View raw message