January 2012 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] Created: (JBOSGI-501) Retire standalone OSGi Runtime

by Thomas Diesler (JIRA)

Retire standalone OSGi Runtime ------------------------------ Key: JBOSGI-501 URL: https://issues.jboss.org/browse/JBOSGI-501 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Reporter: Thomas Diesler Assignee: Thomas Diesler -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-485) Blueprint bundle install

by Andreas Tauber (JIRA)

Blueprint bundle install ------------------------ Key: JBOSGI-485 URL: https://issues.jboss.org/browse/JBOSGI-485 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-osgi-blueprint Affects Versions: JBossOSGi 1.0.0 Reporter: Andreas Tauber Assignee: Thomas Diesler Installing blueprint bundles with multilevel service dependency which work fine on equinox/springDM and felix/aries. Receiving warning; The service's classloader has no visibility of the requested class XXX, though the class is exported in OSGI Manifest. After the warning the following stack trace appears: 20:56:45,939 WARN [FrameworkEventsPlugin] Framework WARNING org.osgi.framework.ServiceException: Cannot unget factory value at org.jboss.osgi.framework.internal.ServiceState.ungetScopedValue(ServiceState.java:195) at org.jboss.osgi.framework.internal.ServiceManagerPlugin.ungetService(ServiceManagerPlugin.java:428) at org.jboss.osgi.framework.internal.AbstractBundleContext.ungetService(AbstractBundleContext.java:360) at org.apache.aries.blueprint.container.ReferenceRecipe.bind(ReferenceRecipe.java:142) at org.apache.aries.blueprint.container.ReferenceRecipe.retrack(ReferenceRecipe.java:112) at org.apache.aries.blueprint.container.AbstractServiceReferenceRecipe.updateListeners(AbstractServiceReferenceRecipe.java:392) at org.apache.aries.blueprint.container.ReferenceRecipe.internalCreate(ReferenceRecipe.java:91) at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64) at org.apache.aries.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:60) at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64) at org.apache.aries.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:771) at org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:742) at org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:723) at org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:689) at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64) at org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:219) at org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:147) at org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:624) at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:315) at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:213) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.NullPointerException at org.jboss.osgi.framework.internal.ServiceState.ungetScopedValue(ServiceState.java:192) ... 27 more cause the bundles work fine, on the other two deployment enviroments something must be wrong with jboss osgi impl -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
11
0 / 0

[JBoss JIRA] Created: (JBOSGI-291) Allow wildcards in org.osgi.framework.system.packages.extra

by Thomas Diesler (JIRA)

Allow wildcards in org.osgi.framework.system.packages.extra ----------------------------------------------------------- Key: JBOSGI-291 URL: https://jira.jboss.org/jira/browse/JBOSGI-291 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: Framework 1.0.x Currently we have  org.jboss.osgi.spi;version=1.0, org.jboss.osgi.spi.capability;version=1.0, org.jboss.osgi.spi.framework;version=1.0, org.jboss.osgi.spi.management;version=1.0, org.jboss.osgi.spi.service;version=1.0, org.jboss.osgi.spi.util;version=1.0, org.jboss.osgi.testing;version=1.0 It should be possible to define this as  org.jboss.osgi.spi*;version=1.0, org.jboss.osgi.testing;version=1.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-467) Review concurrent access to collections

by Thomas Diesler (JIRA)

Review concurrent access to collections --------------------------------------- Key: JBOSGI-467 URL: https://issues.jboss.org/browse/JBOSGI-467 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-457) ConcurrentModificationException in UserBundleState.hasActiveWires

by Stuart Douglas (JIRA)

ConcurrentModificationException in UserBundleState.hasActiveWires ----------------------------------------------------------------- Key: JBOSGI-457 URL: https://issues.jboss.org/browse/JBOSGI-457 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Stuart Douglas Assignee: Thomas Diesler 10:36:30,347 WARN [org.jboss.msc.service.fail] MSC00004: Failure during stop of service jbosgi.bundle.9."org.apache.aries.jmx"."0.3.0".INSTALLED: java.util.ConcurrentModificationException at java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:373) [:1.6.0_22] at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:384) [:1.6.0_22] at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1010) [:1.6.0_22] at org.jboss.osgi.framework.internal.UserBundleState.hasActiveWires(UserBundleState.java:237) at org.jboss.osgi.framework.internal.BundleManager.uninstallBundle(BundleManager.java:462) at org.jboss.osgi.framework.internal.UserBundleInstalledService.stop(UserBundleInstalledService.java:88) at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1779) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] at java.lang.Thread.run(Thread.java:680) [:1.6.0_22] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (JBOSGI-460) Improve toString() for resolver objects

by Thomas Diesler (JIRA)

Improve toString() for resolver objects --------------------------------------- Key: JBOSGI-460 URL: https://issues.jboss.org/browse/JBOSGI-460 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Caused by: org.osgi.framework.BundleException: Cannot initialize XModule from: {Export-Package=[org.jboss.osgi.metadata.internal.AbstractPackageAttribute@24ebf068, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@7df44ec7, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@32602b6b, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@47c297a3, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@38717323, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@203e1bc8, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@4d91f801, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@2a313170, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@3a4c5b4, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@36afae4a, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@47db9852, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@21ed5459, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@643cb075, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@4c6504bc, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@7c19f9d2, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@d6089a5, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@3cecb67f, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@58c16b18], Bundle-SymbolicName=[org.jboss.osgi.metadata.internal.AbstractParameterizedAttribute@25e222e], Bundle-Activator=org.jboss.arquillian.osgi.ArquillianBundleActivator, Bundle-Version=1.0.0.CR1-as734-SNAPSHOT} at org.jboss.osgi.resolver.spi.AbstractModuleBuilder.load(AbstractModuleBuilder.java:202) at org.jboss.osgi.resolver.spi.AbstractModuleBuilder.createModule(AbstractModuleBuilder.java:56) at org.jboss.osgi.framework.internal.UserBundleState.createResolverModule(UserBundleState.java:152) at org.jboss.osgi.framework.internal.UserBundleInstalledService.start(UserBundleInstalledService.java:62) ... 4 more Caused by: java.lang.NumberFormatException: For input string: "${version" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:449) at java.lang.Integer.parseInt(Integer.java:499) at org.osgi.framework.Version.<init>(Version.java:125) at org.osgi.framework.Version.parseVersion(Version.java:218) at org.jboss.osgi.resolver.spi.AbstractPackageCapability.<init>(AbstractPackageCapability.java:48) at org.jboss.osgi.resolver.spi.AbstractModuleBuilder.addPackageCapability(AbstractModuleBuilder.java:100) at org.jboss.osgi.resolver.spi.AbstractModuleBuilder.load(AbstractModuleBuilder.java:163) ... 7 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
4
0 / 0

[JBoss JIRA] (JBOSGI-508) Declarative Services don't start if bundles are activated in different order

by Martin Ždila (JIRA)

Martin Ždila created JBOSGI-508: ----------------------------------- Summary: Declarative Services don't start if bundles are activated in different order Key: JBOSGI-508 URL: https://issues.jboss.org/browse/JBOSGI-508 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Compendium Services Reporter: Martin Ždila Assignee: Thomas Diesler I am using JBoss AS 7.1CR1b. I have two bundles each of them having one Declarative Service (Component). Bundle1 has Service1 and Bundle1 has Service2. Service2 Component is "immediate" and also has reference to Service1. If I have both Bundle1 and Bundle2 in RESOLVED state and start them in order Bundle1, Bundle2, then both services are started (Service1=registered, Service2=unsatisfied) and my testcase prints: {noformat} 16:34:27,124 INFO [org.jboss.osgi.framework.internal.HostBundleState] (qtp1633087118-107) Bundle started: gofer-sandbox1:1.0.0 16:34:28,646 INFO [stdout] (qtp1633087118-110) activate 1 16:34:28,646 INFO [stdout] (qtp1633087118-110) activate 2 16:34:28,656 INFO [org.jboss.osgi.framework.internal.HostBundleState] (qtp1633087118-110) Bundle started: gofer-sandbox2:1.0.0 {noformat} But if the startup order is reverse (Bundle2, Bundle1) then none of the services starts and the components are in the state Service1=registered, Service2=unsatisfied and in the logs I see: {noformat} 16:13:11,162 INFO [org.jboss.osgi.framework.internal.HostBundleState] (qtp1633087118-112) Bundle started: gofer-sandbox2:1.0.0 16:13:14,633 WARN [org.jboss.osgi.framework.internal.ServiceState] (qtp1633087118-107) The service's classloader has no visibility of the requested class: com.mwaysolutions.gofer2.sandbox1.Service1 16:13:14,634 WARN [org.jboss.osgi.framework.internal.ServiceState] (qtp1633087118-107) The service's classloader has no visibility of the requested class: com.mwaysolutions.gofer2.sandbox1.Service1 16:13:14,635 INFO [org.jboss.osgi.framework.internal.HostBundleState] (qtp1633087118-107) Bundle started: gofer-sandbox1:1.0.0 {noformat} The testcase works correctly when using Apache Felix OSGi Framework with Apache Felix Declarative Services. I also think that the problem is deeper than in Declarative Services implementation. I am attaching the testcase. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
8
0 / 0

[JBoss JIRA] (JBOSGI-509) IllegalStateException when service is unregistered twice

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-509: ------------------------------------- Summary: IllegalStateException when service is unregistered twice Key: JBOSGI-509 URL: https://issues.jboss.org/browse/JBOSGI-509 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Check whether this exception is required by spec/tck -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-413) Xerces bundle defines invalid dependency on wutka.dtdparser

by Thomas Diesler (JIRA)

Xerces bundle defines invalid dependency on wutka.dtdparser ----------------------------------------------------------- Key: JBOSGI-413 URL: https://jira.jboss.org/browse/JBOSGI-413 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Currently we need to exclude the dependency on wutka.dtdparser because it is not in the public jboss repository Builds with a clea mvn repo fail. Try a build after rm -rf ~/.m2/repository/wutka-dtdparser https://repository.jboss.org/nexus/content/groups/public-jboss/wutka-dtdp... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
4
0 / 0

[JBoss JIRA] (JBOSGI-504) DOMWebXmlParser fails if jsp-file is used

by Rico Neubauer (Created) (JIRA)

DOMWebXmlParser fails if jsp-file is used ----------------------------------------- Key: JBOSGI-504 URL: https://issues.jboss.org/browse/JBOSGI-504 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-osgi-webapp Affects Versions: JBossOSGi 1.0.0 Reporter: Rico Neubauer Assignee: Thomas Diesler OSGi-deployment fails if web.xml defines a jsp-file entry. This is actually a bug in the used pax-web component. Opened up here: http://team.ops4j.org/browse/PAXWEB-328 This is for information, maybe thinking about a workaround and to upgrade, once it is fixed. Stacktrace including JBoss classes as well: [org.jboss.msc.service] (MSC service thread 1-7) MSC00002: Invocation of listener "org.jboss.as.osgi.deployment.BundleStartTracker$1@6d5535b7" failed: org.ops4j.lang.NullArgumentException: Servlet class is null. at org.ops4j.lang.NullArgumentException.validateNotNull(NullArgumentException.java:75) at org.ops4j.pax.web.extender.war.internal.model.WebAppServlet.setServletClass(WebAppServlet.java:115) at org.ops4j.pax.web.extender.war.internal.parser.dom.DOMWebXmlParser.parseServlets(DOMWebXmlParser.java:284) at org.ops4j.pax.web.extender.war.internal.parser.dom.DOMWebXmlParser.parse(DOMWebXmlParser.java:76) at org.jboss.osgi.webapp.internal.WebXMLParserInterceptor.createWebAppMetadata(WebXMLParserInterceptor.java:82) at org.jboss.osgi.webapp.internal.WebXMLParserInterceptor.invoke(WebXMLParserInterceptor.java:66) at org.jboss.osgi.deployment.interceptor.AbstractLifecycleInterceptorService.handleStateChange(AbstractLifecycleInterceptorService.java:281) [jbosgi-deployment-1.0.10.jar:] at org.jboss.osgi.framework.internal.LifecycleInterceptorPlugin.handleStateChange(LifecycleInterceptorPlugin.java:125) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:183) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:172) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:282) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:223) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:144) [jboss-as-osgi-service-7.1.0.Beta1.jar:] at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:119) [jboss-as-osgi-service-7.1.0.Beta1.jar:] at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1429) [jboss-msc-1.0.1.GA.jar:] at org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:49) [jboss-msc-1.0.1.GA.jar:] at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1952) [jboss-msc-1.0.1.GA.jar:] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues January 2012