June 2010 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] Created: (JBOSGI-298) InstanceAlreadyExistsException: osgi.core:type=framework, version=1.5

by Thomas Diesler (JIRA)

InstanceAlreadyExistsException: osgi.core:type=framework,version=1.5 -------------------------------------------------------------------- Key: JBOSGI-298 URL: https://jira.jboss.org/jira/browse/JBOSGI-298 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta7 MBeans might get registered twice. 2010-03-04 20:40:11,113 INFO [org.apache.aries.jmx] Registering org.osgi.jmx.framework.ServiceStateMBean to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@ce16ad with name osgi.core:type=serviceState,version=1.5 2010-03-04 20:40:11,131 INFO [org.apache.aries.jmx] Registering org.osgi.jmx.framework.BundleStateMBean to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@ce16ad with name osgi.core:type=bundleState,version=1.5 2010-03-04 20:40:11,134 INFO [org.apache.aries.jmx] Registering org.osgi.jmx.framework.PackageStateMBean to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@ce16ad with name osgi.core:type=packageState,version=1.5 2010-03-04 20:40:11,136 ERROR [org.apache.aries.jmx] MBean is already registered org.apache.felix.log.LogException: javax.management.InstanceAlreadyExistsException: osgi.core:type=packageState,version=1.5 at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) at org.apache.aries.jmx.agent.JMXAgentImpl.registerMBeans(JMXAgentImpl.java:128) at org.apache.aries.jmx.agent.JMXAgentContext.registerMBeans(JMXAgentContext.java:58) at org.apache.aries.jmx.MBeanServiceTracker$1.run(MBeanServiceTracker.java:61) 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.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) This is probably due to a asynchronous delay of a previous unregister -- 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

15 years, 4 months

1
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-324) CAnnot start EventAdmin service in AS

by Thomas Diesler (JIRA)

CAnnot start EventAdmin service in AS ------------------------------------- Key: JBOSGI-324 URL: https://jira.jboss.org/jira/browse/JBOSGI-324 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 Caused by: java.lang.ClassNotFoundException: org.osgi.service.log.LogService from OSGiBundleClassLoader(a)104e3f1{org.apache.felix.eventadmin-1.0.0} at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:498) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316) Manifest-Version: 1.0 Built-By: cziegeler Bundle-Activator: org.apache.felix.eventadmin.impl.Activator Created-By: Apache Maven Bundle Plugin Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt Import-Package: org.osgi.framework;version="1.3",org.osgi.service.even t;version="1.1" Bnd-LastModified: 1202107364982 Export-Package: org.osgi.service.event;uses:="org.osgi.framework";vers ion="1.1" Bundle-Version: 1.0.0 Bundle-Name: Apache Felix EventAdmin Bundle-Description: This bundle provides an implementation of the OSGi R4 EventAdmin service. Build-Jdk: 1.5.0_13 Private-Package: org.apache.felix.eventadmin.impl,org.apache.felix.eve ntadmin.impl.adapter,org.apache.felix.eventadmin.impl.dispatch,org.ap ache.felix.eventadmin.impl.handler,org.apache.felix.eventadmin.impl.s ecurity,org.apache.felix.eventadmin.impl.tasks,org.apache.felix.event admin.impl.util Bundle-DocURL: http://www.apache.org/ Export-Service: org.osgi.service.event.EventAdmin Bundle-ManifestVersion: 2 Bundle-Vendor: The Apache Software Foundation Bundle-SymbolicName: org.apache.felix.eventadmin Tool: Bnd-0.0.227 Import-Service: org.osgi.service.event.EventHandler, org.osgi.service. log.LogService, org.osgi.service.log.LogReaderService DynamicImport-Package: org.osgi.service.log It uses the deprecated Import-Service and dynamically imports org.osgi.service.log -- 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

15 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-342) Bundle resolution depends on install order

by Thomas Diesler (JIRA)

Bundle resolution depends on install order ------------------------------------------ Key: JBOSGI-342 URL: https://jira.jboss.org/browse/JBOSGI-342 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 -- 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

15 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-341) Endless loop at AS server startup

by Thomas Diesler (JIRA)

Endless loop at AS server startup --------------------------------- Key: JBOSGI-341 URL: https://jira.jboss.org/browse/JBOSGI-341 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 Using the latest framework together with jboss-cl-2.2.0.Alpha5 gets into an endless loop See: http://community.jboss.org/thread/153006 -- 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

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-338) Cannot obtain EventAdmin service

by Thomas Diesler (JIRA)

Cannot obtain EventAdmin service -------------------------------- Key: JBOSGI-338 URL: https://jira.jboss.org/browse/JBOSGI-338 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 java.lang.IllegalArgumentException: Null reference at org.jboss.osgi.framework.bundle.ServiceManagerPluginImpl.getService(ServiceManagerPluginImpl.java:195) at org.jboss.osgi.framework.bundle.AbstractBundleState.getService(AbstractBundleState.java:521) at org.jboss.osgi.framework.bundle.OSGiBundleContextWrapper.getService(OSGiBundleContextWrapper.java:145) at org.jboss.test.osgi.example.event.EventAdminTestCase.testEventHandler(EventAdminTestCase.java:106) It seems that the test bundle and the service bundle wire to different exporters of the eventadmin API -- 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

15 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-316) Test integrity of the jboss-osgi-framework-all.jar

by Thomas Diesler (JIRA)

Test integrity of the jboss-osgi-framework-all.jar -------------------------------------------------- Key: JBOSGI-316 URL: https://jira.jboss.org/jira/browse/JBOSGI-316 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x The framework-all.jar combines the framework classes with all dependencies that are needed to run the framework in one huge jar. It is used in the TCK to simplify the framework setup Have a look at @Ignore FrameworkLaunchTestCase.testFrameworkAllLaunch -- 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

15 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-317) Context is already registered in domain DefaultDomain

by Thomas Diesler (JIRA)

Context is already registered in domain DefaultDomain ----------------------------------------------------- Key: JBOSGI-317 URL: https://jira.jboss.org/jira/browse/JBOSGI-317 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Integration (JBoss) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 10:29:50,349 ERROR [AbstractKernelController] Error installing to Describe: name=vfsfile:/home/tdiesler/svn/jbossas/tags/JBoss_6_0_0_M2/build/target/jboss-6.0.0.20100216-M2/server/default/deploy/ejb3-interceptors-aop.xml state=PreDescribe mode=Manual requiredState=Describe: org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/tdiesler/svn/jbossas/tags/JBoss_6_0_0_M2/build/target/jboss-6.0.0.20100216-M2/server/default/deploy/ejb3-interceptors-aop.xml at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:185) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1660) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1378) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1319) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:378) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2029) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1050) at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1289) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1213) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1107) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:918) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:633) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:898) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:677) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:378) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2029) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1050) at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1289) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1213) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1107) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:873) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:620) at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:259) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:100) at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:860) at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:441) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.IllegalArgumentException: The context vfsfile:/home/tdiesler/svn/jbossas/tags/JBoss_6_0_0_M2/build/target/jboss-6.0.0.20100216-M2/server/default/deploy/ejb3-interceptors-aop.xml is already registered in domain DefaultDomain at org.jboss.classloading.spi.dependency.Domain.addModule(Domain.java:138) at org.jboss.classloading.spi.dependency.ClassLoading.addModule(ClassLoading.java:78) at org.jboss.deployers.plugins.classloading.AbstractClassLoaderDescribeDeployer.deploy(AbstractClassLoaderDescribeDeployer.java:118) at org.jboss.deployers.plugins.classloading.AbstractClassLoaderDescribeDeployer.deploy(AbstractClassLoaderDescribeDeployer.java:39) at org.jboss.deployers.spi.deployer.helpers.AbstractOptionalRealDeployer.internalDeploy(AbstractOptionalRealDeployer.java:74) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) ... 31 more -- 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

15 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-213) Unexpected dependee state changes

by Thomas Diesler (JIRA)

Unexpected dependee state changes --------------------------------- Key: JBOSGI-213 URL: https://jira.jboss.org/jira/browse/JBOSGI-213 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler B --> X install(X) install(B) start(B) B == ACTIVE X == RESOLVED uninstall(X) B == ACTIVE The MC framework unexpectedly changes the state of B to RESOLVED -- 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

15 years, 5 months

2
8
0 / 0

[JBoss JIRA] Resolved: (JBOSGI-151) Cannot resolve circular dependencies

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/browse/JBOSGI-151?page=com.atlassian.jira.plugin.s... ] Thomas Diesler resolved JBOSGI-151. ----------------------------------- Resolution: Done Running org.jboss.test.osgi.jbosgi151.OSGi151TestCase Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.875 sec > Cannot resolve circular dependencies > ------------------------------------ > > Key: JBOSGI-151 > URL: https://jira.jboss.org/browse/JBOSGI-151 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 1.0.0 Beta8 > > > Unresolved bundle: Bundle{osgi.cmpn:4.2.0.200907101024} > OSGiPackageRequirement{org.osgi.service.http [1.2.0,2.0.0) OPTIONAL {resolution=optional, version="[1.2,2)"}} > Unresolved bundle: Bundle{org.apache.felix.http.jetty:1.0.1} > OSGiPackageRequirement{org.osgi.util.tracker [1.3.0,?) {version="1.3"}} > OSGiPackageRequirement{org.osgi.service.log [1.3.0,?) {version="1.3"}} > OSGiPackageRequirement{org.osgi.service.cm [1.2.0,?) {version="1.2"}} -- 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

15 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues June 2010