March 2013 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] (JBOSGI-522) Update felix/equinox modules for meaningful performance data

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-522?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-522: ---------------------------------- Fix Version/s: Awaiting Volunteers (was: JBossOSGi 2.0.0 CR1) > Update felix/equinox modules for meaningful performance data > ------------------------------------------------------------ > > Key: JBOSGI-522 > URL: https://issues.jboss.org/browse/JBOSGI-522 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Distribution > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBOSGI-519) InitialContextFactoryBuilder already registered in AS

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-519?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-519: ---------------------------------- Fix Version/s: Awaiting Volunteers (was: JBossOSGi 2.0.0 CR1) > InitialContextFactoryBuilder already registered in AS > ----------------------------------------------------- > > Key: JBOSGI-519 > URL: https://issues.jboss.org/browse/JBOSGI-519 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JNDI > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > > In AS we see > {code} > 09:59:52,782 INFO [org.apache.aries.jndi.startup.Activator] (pool-4-thread-1) It was not possible to register an InitialContextFactoryBuilder with the NamingManager because another builder called org.jboss.as.naming.InitialContextFactoryBuilder was already registered. Support for calling new InitialContext() will not be enabled.: java.lang.IllegalStateException: InitialContextFactoryBuilder already set > at javax.naming.spi.NamingManager.setInitialContextFactoryBuilder(NamingManager.java:692) [rt.jar:1.6.0_29] > at org.apache.aries.jndi.startup.Activator.start(Activator.java:76) > at org.apache.aries.jndi.priv.Activator.start(Activator.java:38) > at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:300) > at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:223) > at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:488) > at org.jboss.test.osgi.NamingSupport.provideJNDIIntegration(NamingSupport.java:44) > at org.jboss.test.osgi.example.jndi.JNDITestCase.testOSGiNamingContext(JNDITestCase.java:91) > {code} -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBOSGI-638) ClassCircularityError with Aries Blueprint on JDK1.7

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-638?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-638: ---------------------------------- Fix Version/s: JBossOSGi 2.0.0 > ClassCircularityError with Aries Blueprint on JDK1.7 > ---------------------------------------------------- > > Key: JBOSGI-638 > URL: https://issues.jboss.org/browse/JBOSGI-638 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Blueprint > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.0 > > > {code} > [tdiesler@localhost jbosgi]$ mvn -Dtest=BlueprintTestCase test > 09:13:24,538 DEBUG [org.jboss.osgi.framework] (Blueprint Extender: 2) Register service: ServiceState{service.id=19, objectClass=[org.jboss.test.osgi.example.blueprint.bundle.ServiceB]} > 09:13:24,537 ERROR [org.jboss.osgi.framework] (Blueprint Extender: 1) JBOSGI011026: Framework Error: org.osgi.framework.ServiceException: Cannot get factory value > at org.jboss.osgi.framework.internal.ServiceStateImpl.getScopedValue(ServiceStateImpl.java:152) > at org.jboss.osgi.framework.internal.ServiceManagerImpl.getService(ServiceManagerImpl.java:266) > at org.jboss.osgi.framework.internal.AbstractBundleContext.getService(AbstractBundleContext.java:475) > at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl.addingService(NamespaceHandlerRegistryImpl.java:101) > at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:932) > at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:864) > at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256) > at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229) > at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:894) > at org.jboss.osgi.framework.internal.FrameworkEventsImpl.fireServiceEvent(FrameworkEventsImpl.java:606) > at org.jboss.osgi.framework.internal.ServiceManagerImpl.registerService(ServiceManagerImpl.java:149) > at org.jboss.osgi.framework.internal.AbstractBundleContext.registerService(AbstractBundleContext.java:383) > at org.apache.aries.blueprint.container.BlueprintContainerImpl$3.run(BlueprintContainerImpl.java:412) > at org.apache.aries.blueprint.container.BlueprintContainerImpl$3.run(BlueprintContainerImpl.java:410) > at java.security.AccessController.doPrivileged(Native Method) > at org.apache.aries.blueprint.container.BlueprintContainerImpl.registerService(BlueprintContainerImpl.java:410) > at org.apache.aries.blueprint.container.ServiceRecipe.register(ServiceRecipe.java:191) > at org.apache.aries.blueprint.container.BlueprintContainerImpl.registerServices(BlueprintContainerImpl.java:670) > at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:339) > at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:242) > at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:722) > Caused by: java.lang.ClassCircularityError: org/apache/aries/blueprint/container/BlueprintContainerImpl$5$1 > at org.apache.aries.blueprint.container.BlueprintContainerImpl$5.combine(BlueprintContainerImpl.java:435) > at java.security.AccessControlContext.goCombiner(AccessControlContext.java:493) > at java.security.AccessControlContext.optimize(AccessControlContext.java:401) > at java.security.AccessController.getContext(AccessController.java:502) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:406) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) > at org.apache.aries.blueprint.container.BlueprintContainerImpl.loadClass(BlueprintContainerImpl.java:391) > at org.apache.aries.blueprint.container.BlueprintRepository.loadClass(BlueprintRepository.java:410) > at org.apache.aries.blueprint.container.GenericType.parse(GenericType.java:113) > at org.apache.aries.blueprint.di.AbstractRecipe.doLoadType(AbstractRecipe.java:168) > at org.apache.aries.blueprint.di.AbstractRecipe.loadType(AbstractRecipe.java:161) > at org.apache.aries.blueprint.container.BeanRecipe.loadClass(BeanRecipe.java:245) > at org.apache.aries.blueprint.container.BeanRecipe.getType(BeanRecipe.java:891) > at org.apache.aries.blueprint.container.BeanRecipe.getInstance(BeanRecipe.java:319) > at org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:802) > at org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:783) > at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:106) > at org.apache.aries.blueprint.container.ServiceRecipe.createService(ServiceRecipe.java:280) > at org.apache.aries.blueprint.container.ServiceRecipe.internalGetService(ServiceRecipe.java:247) > at org.apache.aries.blueprint.container.ServiceRecipe.getService(ServiceRecipe.java:349) > at org.apache.aries.blueprint.container.ServiceRecipe$TriggerServiceFactory.getService(ServiceRecipe.java:502) > at org.jboss.osgi.framework.internal.ServiceStateImpl$ServiceFactoryHolder.getService(ServiceStateImpl.java:468) > at org.jboss.osgi.framework.internal.ServiceStateImpl.getScopedValue(ServiceStateImpl.java:141) > ... 28 more > {code} -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBOSGI-641) Verify that Felix Web Console works with R5

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-641: ------------------------------------- Summary: Verify that Felix Web Console works with R5 Key: JBOSGI-641 URL: https://issues.jboss.org/browse/JBOSGI-641 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Distribution Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 2.0.0 CR1 -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBOSGI-582) Update Aries JMX to 1.1.0

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-582?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-582: ---------------------------------- Fix Version/s: Approved / Unscheduled (was: JBossOSGi 2.0.0 CR1) > Update Aries JMX to 1.1.0 > ------------------------- > > Key: JBOSGI-582 > URL: https://issues.jboss.org/browse/JBOSGI-582 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMX > Reporter: David Bosschaert > Fix For: Approved / Unscheduled > > > The JMX integration should be updated to version 1.1.0 which maps to the jmx-next work done in Apache Aries. > The jmx-next work implements the OSGi Enterprise 5.0 JMX specification. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBOSGI-581) Update Aries Blueprint to 1.0.0

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-581?page=com.atlassian.jira.plugin... ] Thomas Diesler reassigned JBOSGI-581: ------------------------------------- Assignee: Thomas Diesler > Update Aries Blueprint to 1.0.0 > ------------------------------- > > Key: JBOSGI-581 > URL: https://issues.jboss.org/browse/JBOSGI-581 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Blueprint > Reporter: David Bosschaert > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.0 CR1 > > > Update the Blueprint integration to use Aries Blueprint 1.0.0. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBOSGI-581) Update Aries Blueprint to 1.0.0

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-581?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-581. ----------------------------------- Resolution: Done Done > Update Aries Blueprint to 1.0.0 > ------------------------------- > > Key: JBOSGI-581 > URL: https://issues.jboss.org/browse/JBOSGI-581 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Blueprint > Reporter: David Bosschaert > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.0 CR1 > > > Update the Blueprint integration to use Aries Blueprint 1.0.0. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBOSGI-493) Add support for weaving hooks

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-493?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-493. ----------------------------------- Resolution: Done Done > Add support for weaving hooks > ----------------------------- > > Key: JBOSGI-493 > URL: https://issues.jboss.org/browse/JBOSGI-493 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.0 CR1 > > -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBOSGI-640) Update Aries JNDI to 1.0.0

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-640?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-640. ----------------------------------- Resolution: Done Done > Update Aries JNDI to 1.0.0 > -------------------------- > > Key: JBOSGI-640 > URL: https://issues.jboss.org/browse/JBOSGI-640 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JNDI > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.0 CR1 > > -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBOSGI-640) Update Aries JNDI to 1.0.0

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-640?page=com.atlassian.jira.plugin... ] Work on JBOSGI-640 started by Thomas Diesler. > Update Aries JNDI to 1.0.0 > -------------------------- > > Key: JBOSGI-640 > URL: https://issues.jboss.org/browse/JBOSGI-640 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JNDI > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.0 CR1 > > -- 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

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues March 2013