From issues at jboss.org Thu Nov 3 14:04:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 3 Nov 2016 14:04:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-803) Upgrade dependencies to WildFly 10.1.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-803: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi-parent/pull/13, https://github.com/jbosgi/jbosgi-metadata/pull/9, https://github.com/jbosgi/jbosgi-vfs/pull/11, https://github.com/jbosgi/jbosgi-spi/pull/10, https://github.com/jbosgi/jbosgi-testing/pull/9, https://github.com/jbosgi/jbosgi-resolver/pull/15, https://github.com/jbosgi/jbosgi-logging/pull/8, https://github.com/jbosgi/jbosgi-deployment/pull/9, https://github.com/jbosgi/jbosgi-framework/pull/30, https://github.com/jbosgi/jbosgi-repository/pull/20, https://github.com/jbosgi/jbosgi-provision/pull/9, https://github.com/jbosgi/jbosgi/pull/27 > Upgrade dependencies to WildFly 10.1.0 > -------------------------------------- > > Key: JBOSGI-803 > URL: https://issues.jboss.org/browse/JBOSGI-803 > Project: JBoss OSGi > Issue Type: Component Upgrade > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > > Upgrade dependencies to WildFly 10.1.0 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 3 14:04:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 3 Nov 2016 14:04:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-803) Upgrade dependencies to WildFly 10.1.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-803. ----------------------------------- Resolution: Done > Upgrade dependencies to WildFly 10.1.0 > -------------------------------------- > > Key: JBOSGI-803 > URL: https://issues.jboss.org/browse/JBOSGI-803 > Project: JBoss OSGi > Issue Type: Component Upgrade > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > > Upgrade dependencies to WildFly 10.1.0 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 3 14:10:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 3 Nov 2016 14:10:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-797) Felix Resolver update to 1.8.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-797: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi-resolver/pull/14 > Felix Resolver update to 1.8.0 > ------------------------------ > > Key: JBOSGI-797 > URL: https://issues.jboss.org/browse/JBOSGI-797 > Project: JBoss OSGi > Issue Type: Component Upgrade > Components: resolver > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0, JBossOSGI 2.5.1, JBossOSGI 2.4.1, JBossOSGI 2.5.2, JBossOSGI 2.4.2 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > > Update Felix Resolver from upstream to 1.8.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 3 14:10:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 3 Nov 2016 14:10:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-797) Felix Resolver update to 1.8.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-797 started by Arcadiy Ivanov. --------------------------------------------- > Felix Resolver update to 1.8.0 > ------------------------------ > > Key: JBOSGI-797 > URL: https://issues.jboss.org/browse/JBOSGI-797 > Project: JBoss OSGi > Issue Type: Component Upgrade > Components: resolver > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0, JBossOSGI 2.5.1, JBossOSGI 2.4.1, JBossOSGI 2.5.2, JBossOSGI 2.4.2 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > > Update Felix Resolver from upstream to 1.8.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 3 14:26:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 3 Nov 2016 14:26:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-797) Felix Resolver update to 1.8.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-797. ----------------------------------- Resolution: Done > Felix Resolver update to 1.8.0 > ------------------------------ > > Key: JBOSGI-797 > URL: https://issues.jboss.org/browse/JBOSGI-797 > Project: JBoss OSGi > Issue Type: Component Upgrade > Components: resolver > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0, JBossOSGI 2.5.1, JBossOSGI 2.4.1, JBossOSGI 2.5.2, JBossOSGI 2.4.2 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > > Update Felix Resolver from upstream to 1.8.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 3 14:26:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 3 Nov 2016 14:26:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-804) Investigate potential race condition In-Reply-To: References: Message-ID: Arcadiy Ivanov created JBOSGI-804: ------------------------------------- Summary: Investigate potential race condition Key: JBOSGI-804 URL: https://issues.jboss.org/browse/JBOSGI-804 Project: JBoss OSGi Issue Type: Task Reporter: Arcadiy Ivanov Assignee: Arcadiy Ivanov {noformat} 14:11:01,912 INFO [org.jboss.as.server] (pool-4-thread-1) WFLYSRV0009: Undeployed "bundleSL" (runtime-name: "bundleSL") 14:11:01,914 INFO [org.jboss.osgi.framework] (pool-5-thread-1) JBOSGI011005: Bundle uninstalled: bundleSL:0.0.0 14:11:01,924 SEVERE [org.jboss.arquillian.protocol.jmx.JMXTestRunner] (pool-5-thread-1) Failed: org.jboss.test.osgi.ds.ServiceListenerTestCase.testServiceAccess: java.lang.IllegalStateException: JBOSGI011217: Cannot load module: deployment.bundleSL:main at org.jboss.osgi.framework.internal.BundleStateRevision.getModuleClassLoader(BundleStateRevision.java:143) at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:142) at org.jboss.modules.Module.loadModuleClass(Module.java:614) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) at org.jboss.test.osgi.ds.ServiceListenerTestCase.testServiceAccess(ServiceListenerTestCase.java:106) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:374) at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136) at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:367) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:426) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) at org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:319) at org.jboss.arquillian.container.test.impl.execution.BeforeLifecycleEventExecuter.on(BeforeLifecycleEventExecuter.java:35) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159) at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:312) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:426) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) at org.junit.runner.JUnitCore.run(JUnitCore.java:137) at org.junit.runner.JUnitCore.run(JUnitCore.java:115) at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:66) at org.jboss.arquillian.protocol.jmx.JMXTestRunner.doRunTestMethod(JMXTestRunner.java:180) at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.doRunTestMethod(ArquillianService.java:243) at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:162) at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:141) at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:219) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1503) at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:724) at org.jboss.as.jmx.BlockingNotificationMBeanServer.invoke(BlockingNotificationMBeanServer.java:168) at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:950) at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153) at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:75) at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:70) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149) at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:70) at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.jboss.modules.ModuleNotFoundException: deployment.bundleSL:main at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:223) at org.jboss.osgi.framework.internal.ModuleManagerImpl.loadModule(ModuleManagerImpl.java:539) at org.jboss.osgi.framework.internal.BundleStateRevision.getModuleClassLoader(BundleStateRevision.java:140) ... 144 more Nov 03, 2016 2:11:02 PM org.jboss.arquillian.protocol.jmx.JMXMethodExecutor invoke SEVERE: Failed: org.jboss.test.osgi.ds.ServiceListenerTestCase.testServiceAccess java.lang.IllegalStateException: JBOSGI011217: Cannot load module: deployment.bundleSL:main at org.jboss.osgi.framework.internal.BundleStateRevision.getModuleClassLoader(BundleStateRevision.java:143) at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:142) at org.jboss.modules.Module.loadModuleClass(Module.java:614) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) at org.jboss.test.osgi.ds.ServiceListenerTestCase.testServiceAccess(ServiceListenerTestCase.java:106) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:374) at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136) at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:367) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:426) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) at org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:319) at org.jboss.arquillian.container.test.impl.execution.BeforeLifecycleEventExecuter.on(BeforeLifecycleEventExecuter.java:35) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159) at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:312) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:426) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) at org.junit.runner.JUnitCore.run(JUnitCore.java:137) at org.junit.runner.JUnitCore.run(JUnitCore.java:115) at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:66) at org.jboss.arquillian.protocol.jmx.JMXTestRunner.doRunTestMethod(JMXTestRunner.java:180) at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.doRunTestMethod(ArquillianService.java:243) at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:162) at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:141) at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:219) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1503) at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:724) at org.jboss.as.jmx.BlockingNotificationMBeanServer.invoke(BlockingNotificationMBeanServer.java:168) at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:950) at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153) at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:75) at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:70) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149) at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:70) at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.jboss.modules.ModuleNotFoundException: deployment.bundleSL:main at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:223) at org.jboss.osgi.framework.internal.ModuleManagerImpl.loadModule(ModuleManagerImpl.java:539) at org.jboss.osgi.framework.internal.BundleStateRevision.getModuleClassLoader(BundleStateRevision.java:140) ... 144 more 14:11:02,012 INFO [org.jboss.osgi.framework] (MSC service thread 1-5) JBOSGI011003: Bundle stopped: reference-tests:0.0.0 14:11:02,016 INFO [org.jboss.osgi.framework] (MSC service thread 1-5) JBOSGI011005: Bundle uninstalled: reference-tests:0.0.0 14:11:02,016 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment reference-tests (runtime-name: reference-tests) in 5ms 14:11:02,045 WARN [org.jboss.as.controller] (management-handler-thread - 1) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address [] 14:11:02,046 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location /home/arcivanov/Documents/src/jbosgi/jbosgi/testsuite/functional/target/wildfly-10.1.0.Final/standalone/data/content/2e/94441f33e9471fb9e9134ade8d17cc0b8e17cf/content 14:11:02,046 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0009: Undeployed "reference-tests" (runtime-name: "reference-tests") Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.461 sec <<< FAILURE! - in org.jboss.test.osgi.ds.ServiceListenerTestCase testServiceAccess(org.jboss.test.osgi.ds.ServiceListenerTestCase) Time elapsed: 0.35 sec <<< ERROR! java.lang.IllegalStateException: JBOSGI011217: Cannot load module: deployment.bundleSL:main at org.jboss.test.osgi.ds.ServiceListenerTestCase.testServiceAccess(ServiceListenerTestCase.java:106) Caused by: org.jboss.modules.ModuleNotFoundException: deployment.bundleSL:main at org.jboss.test.osgi.ds.ServiceListenerTestCase.testServiceAccess(ServiceListenerTestCase.java:106) {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 3 14:28:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 3 Nov 2016 14:28:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-796) Integration desynce'd with javax.api packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-796: ---------------------------------- Fix Version/s: JBossOSGI 2.5.3 Git Pull Request: https://github.com/jbosgi/jbosgi/pull/26 > Integration desynce'd with javax.api packages > --------------------------------------------- > > Key: JBOSGI-796 > URL: https://issues.jboss.org/browse/JBOSGI-796 > Project: JBoss OSGi > Issue Type: Bug > Components: wildfly > Affects Versions: JBossOSGI 2.4.0, JBossOSGI 2.5.0, JBossOSGI 2.5.1, JBossOSGI 2.4.1, JBossOSGI 2.5.2, JBossOSGI 2.4.2 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Minor > Fix For: JBossOSGI 2.5.3 > > > Missing javax.processing.annotations from javax.api packages integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 3 15:10:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 3 Nov 2016 15:10:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-796) Integration desynce'd with javax.api packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov closed JBOSGI-796. --------------------------------- Resolution: Done > Integration desynce'd with javax.api packages > --------------------------------------------- > > Key: JBOSGI-796 > URL: https://issues.jboss.org/browse/JBOSGI-796 > Project: JBoss OSGi > Issue Type: Bug > Components: wildfly > Affects Versions: JBossOSGI 2.4.0, JBossOSGI 2.5.0, JBossOSGI 2.5.1, JBossOSGI 2.4.1, JBossOSGI 2.5.2, JBossOSGI 2.4.2 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Minor > Fix For: JBossOSGI 2.5.3 > > > Missing javax.processing.annotations from javax.api packages integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 3 15:23:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 3 Nov 2016 15:23:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-798) WildFly Framework Lock integration uses incorrect locking In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-798: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi-framework/pull/29, https://github.com/jbosgi/jbosgi/pull/28 > WildFly Framework Lock integration uses incorrect locking > --------------------------------------------------------- > > Key: JBOSGI-798 > URL: https://issues.jboss.org/browse/JBOSGI-798 > Project: JBoss OSGi > Issue Type: Bug > Components: wildfly > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0, JBossOSGI 2.5.1, JBossOSGI 2.4.1, JBossOSGI 2.5.2, JBossOSGI 2.4.2 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Minor > Fix For: JBossOSGI 2.5.3 > > > # WildFly LockManagerIntegration should synchronize on a delegate and not self. > # The skipLocking and delegate.lockItems should be under the same delegate synchronization to prevent a potential race. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 3 15:23:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 3 Nov 2016 15:23:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-798) WildFly Framework Lock integration uses incorrect locking In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-798 started by Arcadiy Ivanov. --------------------------------------------- > WildFly Framework Lock integration uses incorrect locking > --------------------------------------------------------- > > Key: JBOSGI-798 > URL: https://issues.jboss.org/browse/JBOSGI-798 > Project: JBoss OSGi > Issue Type: Bug > Components: wildfly > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0, JBossOSGI 2.5.1, JBossOSGI 2.4.1, JBossOSGI 2.5.2, JBossOSGI 2.4.2 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Minor > Fix For: JBossOSGI 2.5.3 > > > # WildFly LockManagerIntegration should synchronize on a delegate and not self. > # The skipLocking and delegate.lockItems should be under the same delegate synchronization to prevent a potential race. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 3 15:27:01 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 3 Nov 2016 15:27:01 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-798) WildFly Framework Lock integration uses incorrect locking In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov closed JBOSGI-798. --------------------------------- Resolution: Done > WildFly Framework Lock integration uses incorrect locking > --------------------------------------------------------- > > Key: JBOSGI-798 > URL: https://issues.jboss.org/browse/JBOSGI-798 > Project: JBoss OSGi > Issue Type: Bug > Components: wildfly > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0, JBossOSGI 2.5.1, JBossOSGI 2.4.1, JBossOSGI 2.5.2, JBossOSGI 2.4.2 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Minor > Fix For: JBossOSGI 2.5.3 > > > # WildFly LockManagerIntegration should synchronize on a delegate and not self. > # The skipLocking and delegate.lockItems should be under the same delegate synchronization to prevent a potential race. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 10 02:26:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 10 Nov 2016 02:26:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-800) On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-800 started by Arcadiy Ivanov. --------------------------------------------- > On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBOSGI-800 > URL: https://issues.jboss.org/browse/JBOSGI-800 > Project: JBoss OSGi > Issue Type: Bug > Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04 > Reporter: satish bhor > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > Attachments: OSGI.zip > > > There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error. > 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > ... 5 more > 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > } > 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message: > { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 10 23:58:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 10 Nov 2016 23:58:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-800) On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13320755#comment-13320755 ] Arcadiy Ivanov commented on JBOSGI-800: --------------------------------------- [~satish.bhor] Here's the deal. When you undeploy the OSGI.base without stopping OSGI.dependent first, the base.jar gets essentially scheduled for undeployment but is not undeployed, since it's still in use (see WFLY-150) until the dependent is stopped too. What would, in your mind, be a desirable behavior? > On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBOSGI-800 > URL: https://issues.jboss.org/browse/JBOSGI-800 > Project: JBoss OSGi > Issue Type: Bug > Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04 > Reporter: satish bhor > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > Attachments: OSGI.zip > > > There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error. > 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > ... 5 more > 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > } > 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message: > { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 14 12:23:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 14 Nov 2016 12:23:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-800) On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13322154#comment-13322154 ] Arcadiy Ivanov commented on JBOSGI-800: --------------------------------------- [~satish.bhor] bump? > On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBOSGI-800 > URL: https://issues.jboss.org/browse/JBOSGI-800 > Project: JBoss OSGi > Issue Type: Bug > Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04 > Reporter: satish bhor > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > Attachments: OSGI.zip > > > There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error. > 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > ... 5 more > 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > } > 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message: > { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Nov 16 06:13:00 2016 From: issues at jboss.org (satish bhor (JIRA)) Date: Wed, 16 Nov 2016 06:13:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-800) On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13323563#comment-13323563 ] satish bhor commented on JBOSGI-800: ------------------------------------ [~arcivanov] I was expecting when it shows in logs as base bundle gets undeployed it should be undeployed ? Is this behavior according to osgi specification ? > On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBOSGI-800 > URL: https://issues.jboss.org/browse/JBOSGI-800 > Project: JBoss OSGi > Issue Type: Bug > Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04 > Reporter: satish bhor > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > Attachments: OSGI.zip > > > There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error. > 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > ... 5 more > 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > } > 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message: > { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Nov 16 06:24:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Wed, 16 Nov 2016 06:24:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-800) On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13323576#comment-13323576 ] Arcadiy Ivanov commented on JBOSGI-800: --------------------------------------- [~satish.bhor]Here's the deal. Yes, generally when you undeploy this is what will happen. However when you undeploy *base* without undeploying *dependent*, what happens is that *dependent* is still running and is still using classes from *base*. The current behavior undeploys the *base* bundle and the module with the bundle revision is hanging in the limbo +until it stops being used+, in which case it is undeployed for good. The reason you're experiencing this behavior, is because you're undeploying the bundle that has dependencies. I'll see what the prescribed behavior is by OSGi specification, but there is also an issue of WildFly container to consider. > On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBOSGI-800 > URL: https://issues.jboss.org/browse/JBOSGI-800 > Project: JBoss OSGi > Issue Type: Bug > Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04 > Reporter: satish bhor > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > Attachments: OSGI.zip > > > There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error. > 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > ... 5 more > 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > } > 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message: > { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Nov 16 06:25:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Wed, 16 Nov 2016 06:25:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-800) On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13323576#comment-13323576 ] Arcadiy Ivanov edited comment on JBOSGI-800 at 11/16/16 6:24 AM: ----------------------------------------------------------------- [~satish.bhor]Here's the deal. Yes, generally when you undeploy this is what will happen. However when you undeploy *base* without undeploying *dependent*, what happens is that *dependent* is still running and is still using classes from *base*. The current behavior undeploys the *base* bundle and the module with the bundle revision is hanging in the limbo +until it stops being used+, in which case it is undeployed for good. The reason you're experiencing this behavior, is because you're undeploying the bundle that has dependencies. So my question is: do you want *dependent* to be undeployed too? Or stopped? Or something else? I'll see what the prescribed behavior is by OSGi specification (if any), but there is also an issue of WildFly container to consider. was (Author: arcivanov): [~satish.bhor]Here's the deal. Yes, generally when you undeploy this is what will happen. However when you undeploy *base* without undeploying *dependent*, what happens is that *dependent* is still running and is still using classes from *base*. The current behavior undeploys the *base* bundle and the module with the bundle revision is hanging in the limbo +until it stops being used+, in which case it is undeployed for good. The reason you're experiencing this behavior, is because you're undeploying the bundle that has dependencies. I'll see what the prescribed behavior is by OSGi specification, but there is also an issue of WildFly container to consider. > On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBOSGI-800 > URL: https://issues.jboss.org/browse/JBOSGI-800 > Project: JBoss OSGi > Issue Type: Bug > Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04 > Reporter: satish bhor > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > Attachments: OSGI.zip > > > There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error. > 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > ... 5 more > 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > } > 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message: > { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Nov 16 06:28:01 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Wed, 16 Nov 2016 06:28:01 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-800) On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13323576#comment-13323576 ] Arcadiy Ivanov edited comment on JBOSGI-800 at 11/16/16 6:27 AM: ----------------------------------------------------------------- [~satish.bhor] Here's the deal. Yes, generally when you undeploy this is what will happen. However when you undeploy *base* without undeploying *dependent*, what happens is that *dependent* is still running and is still using classes from *base*. The current behavior undeploys the *base* bundle and the module with the bundle revision is hanging in the limbo +until it stops being used+, in which case it is undeployed for good. The reason you're experiencing this behavior, is because you're undeploying the bundle that has dependencies. So my question is: do you want *dependent* to be undeployed too? Or stopped? Or something else? I'll see what the prescribed behavior is by OSGi specification (if any), but there is also an issue of WildFly container to consider. was (Author: arcivanov): [~satish.bhor]Here's the deal. Yes, generally when you undeploy this is what will happen. However when you undeploy *base* without undeploying *dependent*, what happens is that *dependent* is still running and is still using classes from *base*. The current behavior undeploys the *base* bundle and the module with the bundle revision is hanging in the limbo +until it stops being used+, in which case it is undeployed for good. The reason you're experiencing this behavior, is because you're undeploying the bundle that has dependencies. So my question is: do you want *dependent* to be undeployed too? Or stopped? Or something else? I'll see what the prescribed behavior is by OSGi specification (if any), but there is also an issue of WildFly container to consider. > On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBOSGI-800 > URL: https://issues.jboss.org/browse/JBOSGI-800 > Project: JBoss OSGi > Issue Type: Bug > Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04 > Reporter: satish bhor > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > Attachments: OSGI.zip > > > There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error. > 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > ... 5 more > 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > } > 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message: > { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 17 00:40:00 2016 From: issues at jboss.org (Hannu Lahtinen (JIRA)) Date: Thu, 17 Nov 2016 00:40:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class In-Reply-To: References: Message-ID: Hannu Lahtinen created JBOSGI-805: ------------------------------------- Summary: ConcurrentModificationException from AbstractWiring when loading a dynamically imported class Key: JBOSGI-805 URL: https://issues.jboss.org/browse/JBOSGI-805 Project: JBoss OSGi Issue Type: Feature Request Components: framework, resolver Affects Versions: JBossOSGI 2.5.2 Reporter: Hannu Lahtinen Assignee: Arcadiy Ivanov {code} java.util ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102] at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102] at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120) at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165) at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final] ... {code} Steps that cause the exception to occur: 1. bundle with DIP: * in MANIFEST. 2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically. This exception is timing based and does not happen every time but in our environment happens about 20% of the time. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 17 01:57:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 17 Nov 2016 01:57:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-805 started by Arcadiy Ivanov. --------------------------------------------- > ConcurrentModificationException from AbstractWiring when loading a dynamically imported class > --------------------------------------------------------------------------------------------- > > Key: JBOSGI-805 > URL: https://issues.jboss.org/browse/JBOSGI-805 > Project: JBoss OSGi > Issue Type: Feature Request > Components: framework, resolver > Affects Versions: JBossOSGI 2.5.2 > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > > {code} > java.util ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102] > at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102] > at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120) > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165) > at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final] > ... > {code} > Steps that cause the exception to occur: > 1. bundle with DIP: * in MANIFEST. > 2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically. > This exception is timing based and does not happen every time but in our environment happens about 20% of the time. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 17 02:28:00 2016 From: issues at jboss.org (Hannu Lahtinen (JIRA)) Date: Thu, 17 Nov 2016 02:28:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hannu Lahtinen updated JBOSGI-805: ---------------------------------- Issue Type: Bug (was: Feature Request) > ConcurrentModificationException from AbstractWiring when loading a dynamically imported class > --------------------------------------------------------------------------------------------- > > Key: JBOSGI-805 > URL: https://issues.jboss.org/browse/JBOSGI-805 > Project: JBoss OSGi > Issue Type: Bug > Components: framework, resolver > Affects Versions: JBossOSGI 2.5.2 > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > > {code} > java.util ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102] > at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102] > at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120) > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165) > at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final] > ... > {code} > Steps that cause the exception to occur: > 1. bundle with DIP: * in MANIFEST. > 2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically. > This exception is timing based and does not happen every time but in our environment happens about 20% of the time. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 17 02:29:00 2016 From: issues at jboss.org (Hannu Lahtinen (JIRA)) Date: Thu, 17 Nov 2016 02:29:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13324081#comment-13324081 ] Hannu Lahtinen commented on JBOSGI-805: --------------------------------------- Had accidentally marked this as a feature request. Sorry about that. > ConcurrentModificationException from AbstractWiring when loading a dynamically imported class > --------------------------------------------------------------------------------------------- > > Key: JBOSGI-805 > URL: https://issues.jboss.org/browse/JBOSGI-805 > Project: JBoss OSGi > Issue Type: Bug > Components: framework, resolver > Affects Versions: JBossOSGI 2.5.2 > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > > {code} > java.util ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102] > at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102] > at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120) > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165) > at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final] > ... > {code} > Steps that cause the exception to occur: > 1. bundle with DIP: * in MANIFEST. > 2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically. > This exception is timing based and does not happen every time but in our environment happens about 20% of the time. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 17 04:50:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 17 Nov 2016 04:50:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-805 stopped by Arcadiy Ivanov. --------------------------------------------- > ConcurrentModificationException from AbstractWiring when loading a dynamically imported class > --------------------------------------------------------------------------------------------- > > Key: JBOSGI-805 > URL: https://issues.jboss.org/browse/JBOSGI-805 > Project: JBoss OSGi > Issue Type: Bug > Components: framework, resolver > Affects Versions: JBossOSGI 2.5.2 > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > > {code} > java.util ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102] > at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102] > at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120) > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165) > at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final] > ... > {code} > Steps that cause the exception to occur: > 1. bundle with DIP: * in MANIFEST. > 2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically. > This exception is timing based and does not happen every time but in our environment happens about 20% of the time. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 17 04:53:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 17 Nov 2016 04:53:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-805: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi-resolver/pull/16 > ConcurrentModificationException from AbstractWiring when loading a dynamically imported class > --------------------------------------------------------------------------------------------- > > Key: JBOSGI-805 > URL: https://issues.jboss.org/browse/JBOSGI-805 > Project: JBoss OSGi > Issue Type: Bug > Components: framework, resolver > Affects Versions: JBossOSGI 2.5.2 > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > > {code} > java.util ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102] > at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102] > at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120) > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165) > at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final] > ... > {code} > Steps that cause the exception to occur: > 1. bundle with DIP: * in MANIFEST. > 2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically. > This exception is timing based and does not happen every time but in our environment happens about 20% of the time. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 17 04:54:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 17 Nov 2016 04:54:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13324129#comment-13324129 ] Arcadiy Ivanov commented on JBOSGI-805: --------------------------------------- [~hannu1] The SNAPSHOT JBOSGI 2.5.2 has been uploaded. Please test with it and let me know if you find any other problems that may be related. > ConcurrentModificationException from AbstractWiring when loading a dynamically imported class > --------------------------------------------------------------------------------------------- > > Key: JBOSGI-805 > URL: https://issues.jboss.org/browse/JBOSGI-805 > Project: JBoss OSGi > Issue Type: Bug > Components: framework, resolver > Affects Versions: JBossOSGI 2.5.2 > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > > {code} > java.util ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102] > at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102] > at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120) > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165) > at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final] > ... > {code} > Steps that cause the exception to occur: > 1. bundle with DIP: * in MANIFEST. > 2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically. > This exception is timing based and does not happen every time but in our environment happens about 20% of the time. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 17 06:00:01 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 17 Nov 2016 06:00:01 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-800) On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13324172#comment-13324172 ] Arcadiy Ivanov commented on JBOSGI-800: --------------------------------------- [~satish.bhor] Here's the authoritative word from OSGI 5 Spec (emphasis added): The framework never eagerly disconnects the wires between Bundle Wirings, a disconnect happens only under control of the management agent when the refreshBundles(Collection, FrameworkListener...) *method is called or when all requiring bundles become uninstalled*. When a bundle is updated, its existing BundleWiring objects will continue to serve classes and resources to bundles that use it. The update, even though it provides a new revision, has no effect on resolved bundles with respect to class loading. Also, the installation of a new bundle could allow new wires but they must not affect the existing wiring until refreshBundles(Collection,FrameworkListener...) is called (with the exception for dynamic imports). Though the class loading wires remain in place, proper bundles should react to the changes in the dynamic state. That is, when a bundle is updated it will be stopped, allowing others to remove any references they have to that bundle. However, even in those cases the wirings will remain until the bundle is unresolved during a refresh cycle. Since it does not seem possible to install a new revision of the deployment +base+ into WildFly while the wirings from the old +base+ exist, you have to stop dependent first and then redeploy the +base+, per OSGi. The forceful stop of +dependent+ when you undeploy +base+ would be contrary to spec. > On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBOSGI-800 > URL: https://issues.jboss.org/browse/JBOSGI-800 > Project: JBoss OSGi > Issue Type: Bug > Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04 > Reporter: satish bhor > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > Attachments: OSGI.zip > > > There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error. > 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > ... 5 more > 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > } > 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message: > { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 18 02:55:00 2016 From: issues at jboss.org (Hannu Lahtinen (JIRA)) Date: Fri, 18 Nov 2016 02:55:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13324612#comment-13324612 ] Hannu Lahtinen commented on JBOSGI-805: --------------------------------------- That was fast. :) Thank you! I will try to get it tested today, Monday at the latest. > ConcurrentModificationException from AbstractWiring when loading a dynamically imported class > --------------------------------------------------------------------------------------------- > > Key: JBOSGI-805 > URL: https://issues.jboss.org/browse/JBOSGI-805 > Project: JBoss OSGi > Issue Type: Bug > Components: framework, resolver > Affects Versions: JBossOSGI 2.5.2 > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > > {code} > java.util ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102] > at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102] > at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120) > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165) > at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final] > ... > {code} > Steps that cause the exception to occur: > 1. bundle with DIP: * in MANIFEST. > 2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically. > This exception is timing based and does not happen every time but in our environment happens about 20% of the time. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 18 04:23:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Fri, 18 Nov 2016 04:23:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13324661#comment-13324661 ] Arcadiy Ivanov commented on JBOSGI-805: --------------------------------------- [~hannu1] You're welcome. This type of issue is easy since the problem is trivial. Just please make sure you're using a snapshot, since it's sitting in a PR. > ConcurrentModificationException from AbstractWiring when loading a dynamically imported class > --------------------------------------------------------------------------------------------- > > Key: JBOSGI-805 > URL: https://issues.jboss.org/browse/JBOSGI-805 > Project: JBoss OSGi > Issue Type: Bug > Components: framework, resolver > Affects Versions: JBossOSGI 2.5.2 > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > > {code} > java.util ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102] > at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102] > at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120) > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165) > at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final] > ... > {code} > Steps that cause the exception to occur: > 1. bundle with DIP: * in MANIFEST. > 2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically. > This exception is timing based and does not happen every time but in our environment happens about 20% of the time. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 18 05:33:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Fri, 18 Nov 2016 05:33:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-805: ---------------------------------- Fix Version/s: JBossOSGI 2.5.3 > ConcurrentModificationException from AbstractWiring when loading a dynamically imported class > --------------------------------------------------------------------------------------------- > > Key: JBOSGI-805 > URL: https://issues.jboss.org/browse/JBOSGI-805 > Project: JBoss OSGi > Issue Type: Bug > Components: framework, resolver > Affects Versions: JBossOSGI 2.5.2 > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > > {code} > java.util ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102] > at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102] > at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120) > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165) > at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final] > ... > {code} > Steps that cause the exception to occur: > 1. bundle with DIP: * in MANIFEST. > 2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically. > This exception is timing based and does not happen every time but in our environment happens about 20% of the time. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 18 05:33:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Fri, 18 Nov 2016 05:33:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13324129#comment-13324129 ] Arcadiy Ivanov edited comment on JBOSGI-805 at 11/18/16 5:32 AM: ----------------------------------------------------------------- [~hannu1] The SNAPSHOT JBOSGI 2.5.3 has been uploaded. Please test with it and let me know if you find any other problems that may be related. was (Author: arcivanov): [~hannu1] The SNAPSHOT JBOSGI 2.5.2 has been uploaded. Please test with it and let me know if you find any other problems that may be related. > ConcurrentModificationException from AbstractWiring when loading a dynamically imported class > --------------------------------------------------------------------------------------------- > > Key: JBOSGI-805 > URL: https://issues.jboss.org/browse/JBOSGI-805 > Project: JBoss OSGi > Issue Type: Bug > Components: framework, resolver > Affects Versions: JBossOSGI 2.5.2 > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > > {code} > java.util ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102] > at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102] > at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120) > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165) > at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final] > ... > {code} > Steps that cause the exception to occur: > 1. bundle with DIP: * in MANIFEST. > 2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically. > This exception is timing based and does not happen every time but in our environment happens about 20% of the time. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 18 09:29:00 2016 From: issues at jboss.org (Hannu Lahtinen (JIRA)) Date: Fri, 18 Nov 2016 09:29:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13324911#comment-13324911 ] Hannu Lahtinen commented on JBOSGI-805: --------------------------------------- I had a hard time reproducing the bug with the old version, so my testing is not complete. I can tell you I reproduced it only once in ~20 boot ups with the old version and 0 times in 3 boots with the new version. I reviewed your changes and I don't see any reason why it wouldn't fix this. I will test further on Monday and try to make a test case so I can hopefully reproduce it more consistently. > ConcurrentModificationException from AbstractWiring when loading a dynamically imported class > --------------------------------------------------------------------------------------------- > > Key: JBOSGI-805 > URL: https://issues.jboss.org/browse/JBOSGI-805 > Project: JBoss OSGi > Issue Type: Bug > Components: framework, resolver > Affects Versions: JBossOSGI 2.5.2 > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > > {code} > java.util ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102] > at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102] > at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120) > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165) > at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final] > ... > {code} > Steps that cause the exception to occur: > 1. bundle with DIP: * in MANIFEST. > 2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically. > This exception is timing based and does not happen every time but in our environment happens about 20% of the time. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 18 10:29:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Fri, 18 Nov 2016 10:29:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13324972#comment-13324972 ] Arcadiy Ivanov commented on JBOSGI-805: --------------------------------------- Great! I'm going to merge this as my concern was primarily not lack of fix per se, but rather a class-loading regression failure. > ConcurrentModificationException from AbstractWiring when loading a dynamically imported class > --------------------------------------------------------------------------------------------- > > Key: JBOSGI-805 > URL: https://issues.jboss.org/browse/JBOSGI-805 > Project: JBoss OSGi > Issue Type: Bug > Components: framework, resolver > Affects Versions: JBossOSGI 2.5.2 > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > > {code} > java.util ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102] > at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102] > at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120) > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165) > at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final] > ... > {code} > Steps that cause the exception to occur: > 1. bundle with DIP: * in MANIFEST. > 2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically. > This exception is timing based and does not happen every time but in our environment happens about 20% of the time. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 18 10:29:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Fri, 18 Nov 2016 10:29:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-805 started by Arcadiy Ivanov. --------------------------------------------- > ConcurrentModificationException from AbstractWiring when loading a dynamically imported class > --------------------------------------------------------------------------------------------- > > Key: JBOSGI-805 > URL: https://issues.jboss.org/browse/JBOSGI-805 > Project: JBoss OSGi > Issue Type: Bug > Components: framework, resolver > Affects Versions: JBossOSGI 2.5.2 > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > > {code} > java.util ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102] > at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102] > at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120) > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165) > at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final] > ... > {code} > Steps that cause the exception to occur: > 1. bundle with DIP: * in MANIFEST. > 2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically. > This exception is timing based and does not happen every time but in our environment happens about 20% of the time. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 18 10:57:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Fri, 18 Nov 2016 10:57:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-805. ----------------------------------- Release Notes Text: AbstractWiring guards against modification with synchronization on self. Resolution: Done > ConcurrentModificationException from AbstractWiring when loading a dynamically imported class > --------------------------------------------------------------------------------------------- > > Key: JBOSGI-805 > URL: https://issues.jboss.org/browse/JBOSGI-805 > Project: JBoss OSGi > Issue Type: Bug > Components: framework, resolver > Affects Versions: JBossOSGI 2.5.2 > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > > {code} > java.util ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102] > at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102] > at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120) > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165) > at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final] > ... > {code} > Steps that cause the exception to occur: > 1. bundle with DIP: * in MANIFEST. > 2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically. > This exception is timing based and does not happen every time but in our environment happens about 20% of the time. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 21 00:33:00 2016 From: issues at jboss.org (satish bhor (JIRA)) Date: Mon, 21 Nov 2016 00:33:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-800) On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13325317#comment-13325317 ] satish bhor commented on JBOSGI-800: ------------------------------------ Thanks [~arcivanov] for clarification I will close this issue. > On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBOSGI-800 > URL: https://issues.jboss.org/browse/JBOSGI-800 > Project: JBoss OSGi > Issue Type: Bug > Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04 > Reporter: satish bhor > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > Attachments: OSGI.zip > > > There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error. > 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > ... 5 more > 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > } > 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message: > { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 21 00:35:00 2016 From: issues at jboss.org (satish bhor (JIRA)) Date: Mon, 21 Nov 2016 00:35:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-800) On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13325317#comment-13325317 ] satish bhor edited comment on JBOSGI-800 at 11/21/16 12:34 AM: --------------------------------------------------------------- Thanks [~arcivanov] for clarification you can close this issue. was (Author: satish.bhor): Thanks [~arcivanov] for clarification I will close this issue. > On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBOSGI-800 > URL: https://issues.jboss.org/browse/JBOSGI-800 > Project: JBoss OSGi > Issue Type: Bug > Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04 > Reporter: satish bhor > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > Attachments: OSGI.zip > > > There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error. > 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > ... 5 more > 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > } > 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message: > { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 21 10:20:00 2016 From: issues at jboss.org (Hannu Lahtinen (JIRA)) Date: Mon, 21 Nov 2016 10:20:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13325742#comment-13325742 ] Hannu Lahtinen commented on JBOSGI-805: --------------------------------------- Great. We tested this further today and managed to reproduce the bug steadily with the old version and had no issues after switching to the new snapshot version. > ConcurrentModificationException from AbstractWiring when loading a dynamically imported class > --------------------------------------------------------------------------------------------- > > Key: JBOSGI-805 > URL: https://issues.jboss.org/browse/JBOSGI-805 > Project: JBoss OSGi > Issue Type: Bug > Components: framework, resolver > Affects Versions: JBossOSGI 2.5.2 > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > > {code} > java.util ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102] > at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102] > at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120) > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165) > at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final] > ... > {code} > Steps that cause the exception to occur: > 1. bundle with DIP: * in MANIFEST. > 2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically. > This exception is timing based and does not happen every time but in our environment happens about 20% of the time. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 21 12:03:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 21 Nov 2016 12:03:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-800) On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-800 stopped by Arcadiy Ivanov. --------------------------------------------- > On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBOSGI-800 > URL: https://issues.jboss.org/browse/JBOSGI-800 > Project: JBoss OSGi > Issue Type: Bug > Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04 > Reporter: satish bhor > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > Attachments: OSGI.zip > > > There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error. > 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > ... 5 more > 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > } > 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message: > { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 21 12:05:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 21 Nov 2016 12:05:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-800) On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-800. ----------------------------------- Resolution: Won't Fix Works according to OSGi Spec. > On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBOSGI-800 > URL: https://issues.jboss.org/browse/JBOSGI-800 > Project: JBoss OSGi > Issue Type: Bug > Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04 > Reporter: satish bhor > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > Attachments: OSGI.zip > > > There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error. > 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final] > at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325) > at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164) > at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81) > at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final] > ... 5 more > 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > } > 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message: > { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\" > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"], > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 21 12:06:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 21 Nov 2016 12:06:00 -0500 (EST) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-799) Blooming dependency resolution with Spring bundles In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-799: ---------------------------------- Fix Version/s: (was: JBossOSGI 2.5.3) > Blooming dependency resolution with Spring bundles > -------------------------------------------------- > > Key: JBOSGI-799 > URL: https://issues.jboss.org/browse/JBOSGI-799 > Project: JBoss OSGi > Issue Type: Bug > Components: wildfly > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0, JBossOSGI 2.5.1, JBossOSGI 2.4.1, JBossOSGI 2.5.2, JBossOSGI 2.4.2 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > -- This message was sent by Atlassian JIRA (v7.2.3#72005)