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

[JBoss JIRA] Created: (JBOSGI-301) Enable VFS3 leak detection in runtime and jbossas

by Thomas Diesler (JIRA)

Enable VFS3 leak detection in runtime and jbossas ------------------------------------------------- Key: JBOSGI-301 URL: https://jira.jboss.org/jira/browse/JBOSGI-301 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta7 Code which does not properly cleanup a mount point can be detected by enabling leak detection. Leak detection can be enabled by setting the jboss.vfs.leakDebugging system property to true. -- 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

13 years, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-94) Remove DeploymentProvidedDeploymentUnitFilter

by Thomas Diesler (JIRA)

Remove DeploymentProvidedDeploymentUnitFilter --------------------------------------------- Key: JBOSGI-94 URL: https://jira.jboss.org/jira/browse/JBOSGI-94 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Remove this class when this functionallity is natively supported by all target containers -- 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

13 years, 10 months

1
2
0 / 0

[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

13 years, 10 months

1
5
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

13 years, 10 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

13 years, 11 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

13 years, 11 months

2
8
0 / 0

[JBoss JIRA] Created: (JBOSGI-306) Invalic classloader policy created

by Thomas Diesler (JIRA)

Invalic classloader policy created ---------------------------------- Key: JBOSGI-306 URL: https://jira.jboss.org/jira/browse/JBOSGI-306 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: Framework 1.0.0 Alpha4 * OSGiClassLoaderFactory.createClassLoader() sets the ClassLoaderPolicyFactory on the Module * ClassLoaderPolicyModule.registerClassLoaderPolicy() calls getPolicy() on itself * getPolicy() should call policyFactory.createClassLoaderPolicy() on the factory that was set above However the policyFactory is null so it falls back to ClassLoaderPolicyModule.createClassLoaderPolicy(), which results in the wrong policy being created. Caused by: java.lang.IllegalArgumentException: Invalid policy: VFSClassLoaderPolicy@190d536{vfs:///home/tdiesler/svn/jboss-osgi/trunk/reactor/framework/bundle/target/osgi-store/bundle-0/bundle-1269577893252.jar/} at org.jboss.osgi.framework.classloading.OSGiBundleClassLoader.<init>(OSGiBundleClassLoader.java:46) at org.jboss.osgi.framework.classloading.OSGiClassLoaderSystem.createClassLoader(OSGiClassLoaderSystem.java:71) at org.jboss.classloader.spi.base.BaseClassLoaderSystem$1.run(BaseClassLoaderSystem.java:126) at org.jboss.classloader.spi.base.BaseClassLoaderSystem$1.run(BaseClassLoaderSystem.java:123) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.classloader.spi.base.BaseClassLoaderSystem.registerClassLoaderPolicy(BaseClassLoaderSystem.java:122) at org.jboss.classloader.spi.ClassLoaderSystem.registerClassLoaderPolicy(ClassLoaderSystem.java:494) at org.jboss.classloader.spi.ClassLoaderSystem.registerClassLoaderPolicy(ClassLoaderSystem.java:436) at org.jboss.classloading.spi.dependency.policy.ClassLoaderPolicyModule.registerClassLoaderPolicy(ClassLoaderPolicyModule.java:147) at org.jboss.osgi.framework.classloading.OSGiClassLoaderFactory.createClassLoader(OSGiClassLoaderFactory.java:88) -- 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

1
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-235) Verify system classpath access

by Thomas Diesler (JIRA)

Verify system classpath access ------------------------------ Key: JBOSGI-235 URL: https://jira.jboss.org/jira/browse/JBOSGI-235 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Create a test case that verifies that bundle classes cannot access packages that are not defined by the framework system packages. Non OSGi deployments need to see packages on the default domain. -- 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

1
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-318) Linkage error for javax.servlet.Servlet in AS600

by Thomas Diesler (JIRA)

Linkage error for javax.servlet.Servlet in AS600 ------------------------------------------------ Key: JBOSGI-318 URL: https://jira.jboss.org/jira/browse/JBOSGI-318 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 Caused by: java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "org.ops4j.pax.web.service.internal.HttpServiceProxy.registerServlet(Ljava/lang/String;Ljavax/servlet/Servlet;Ljava/util/Dictionary;Lorg/osgi/service/http/HttpContext;)V" the class loader (instance of org/jboss/osgi/framework/classloading/OSGiBundleClassLoader) of the current class, org/ops4j/pax/web/service/internal/HttpServiceProxy, and the class loader (instance of org/jboss/osgi/framework/classloading/OSGiBundleClassLoader) for interface org/osgi/service/http/HttpService have different Class objects for the type javax/servlet/Servlet used in the signature at org.ops4j.pax.web.service.internal.Activator$2.createService(Activator.java:104) at org.ops4j.pax.web.service.internal.HttpServiceFactoryImpl.getService(HttpServiceFactoryImpl.java:34) at org.jboss.osgi.framework.bundle.OSGiServiceState.getService(OSGiServiceState.java:391) ... 20 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

14 years

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-319) LinkageError for the type javax/servlet/Servlet

by Thomas Diesler (JIRA)

LinkageError for the type javax/servlet/Servlet ------------------------------------------------ Key: JBOSGI-319 URL: https://jira.jboss.org/jira/browse/JBOSGI-319 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 Caused by: java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "org.ops4j.pax.web.service.internal.HttpServiceProxy.registerServlet(Ljava/lang/String;Ljavax/servlet/Servlet;Ljava/util/Dictionary;Lorg/osgi/service/http/HttpContext;)V" the class loader (instance of org/jboss/osgi/framework/classloading/OSGiBundleClassLoader) of the current class, org/ops4j/pax/web/service/internal/HttpServiceProxy, and the class loader (instance of org/jboss/osgi/framework/classloading/OSGiBundleClassLoader) for interface org/osgi/service/http/HttpService have different Class objects for the type javax/servlet/Servlet used in the signature at org.ops4j.pax.web.service.internal.Activator$2.createService(Activator.java:104) at org.ops4j.pax.web.service.internal.HttpServiceFactoryImpl.getService(HttpServiceFactoryImpl.java:34) at org.jboss.osgi.framework.bundle.OSGiServiceState.getService(OSGiServiceState.java:391) ... 20 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

14 years

1
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues April 2010