From issues at jboss.org Fri Oct 7 03:30:00 2016 From: issues at jboss.org (satish bhor (JIRA)) Date: Fri, 7 Oct 2016 03:30:00 -0400 (EDT) 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: satish bhor created JBOSGI-800: ---------------------------------- Summary: 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 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 (v6.4.11#64026) From issues at jboss.org Fri Oct 7 03:33:00 2016 From: issues at jboss.org (satish bhor (JIRA)) Date: Fri, 7 Oct 2016 03:33:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-801) 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: satish bhor created JBOSGI-801: ---------------------------------- Summary: On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered Key: JBOSGI-801 URL: https://issues.jboss.org/browse/JBOSGI-801 Project: JBoss OSGi Issue Type: Bug Reporter: satish bhor Assignee: Arcadiy Ivanov 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 (v6.4.11#64026) From issues at jboss.org Fri Oct 7 03:36:00 2016 From: issues at jboss.org (satish bhor (JIRA)) Date: Fri, 7 Oct 2016 03:36:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-801) 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-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] satish bhor closed JBOSGI-801. ------------------------------ Resolution: Duplicate 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-801 > URL: https://issues.jboss.org/browse/JBOSGI-801 > Project: JBoss OSGi > Issue Type: Bug > Reporter: satish bhor > Assignee: Arcadiy Ivanov > > 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 (v6.4.11#64026) From issues at jboss.org Mon Oct 10 13:16:02 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 10 Oct 2016 13:16:02 -0400 (EDT) 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=13305107#comment-13305107 ] Arcadiy Ivanov commented on JBOSGI-800: --------------------------------------- [~satish.bhor] Thanks for the report. 1. The bundles require explicit dependencies for proper linking (https://issues.jboss.org/browse/JBOSGI-794?focusedCommentId=13204574&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13204574). This is not JBOSGI requirement but OSGI. Please provide manifests for all three bundles involved. 2. JBOSGI is not certified WFLY 10.1 yet. I'll work on that in the near future. > 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 > > 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 (v6.4.11#64026) From issues at jboss.org Thu Oct 13 12:10:00 2016 From: issues at jboss.org (satish bhor (JIRA)) Date: Thu, 13 Oct 2016 12:10:00 -0400 (EDT) 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 ] satish bhor updated JBOSGI-800: ------------------------------- Attachment: OSGI.zip > 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 > 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 (v6.4.11#64026) From issues at jboss.org Thu Oct 13 12:18:00 2016 From: issues at jboss.org (satish bhor (JIRA)) Date: Thu, 13 Oct 2016 12:18:00 -0400 (EDT) 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=13306828#comment-13306828 ] satish bhor commented on JBOSGI-800: ------------------------------------ Hello [~arcivanov] I have attached maven project which include two osgi bundles base bundle and dependent bundle. Here are the steps to reproduce 1) First we deploy both(base and dependent) bundles 2) Undeploy Only base bundle 3) Redeploy base bundle, we will get following error, 21:36:26,160 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."base-1.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."base-1.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "base-1.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.base-1.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 21:36:26,167 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 6) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "base-1.0.jar")]) - failure description: { "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"base-1.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"base-1.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"base-1.0.jar\" Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.base-1.0.jar\".main is already registered"}, "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"base-1.0.jar\".CONFIGURE_MODULE"], "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined } 21:36:26,169 ERROR [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0021: Deploy of deployment "base-1.0.jar" was rolled back with the following failure message: { "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"base-1.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"base-1.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"base-1.0.jar\" Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.base-1.0.jar\".main is already registered"}, "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"base-1.0.jar\".CONFIGURE_MODULE"], "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined } > 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 > 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 (v6.4.11#64026) From issues at jboss.org Thu Oct 13 15:46:00 2016 From: issues at jboss.org (Hannu Lahtinen (JIRA)) Date: Thu, 13 Oct 2016 15:46:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-802) WAR deployments do not always manage to resolve OSGi dependencies during startup In-Reply-To: References: Message-ID: Hannu Lahtinen created JBOSGI-802: ------------------------------------- Summary: WAR deployments do not always manage to resolve OSGi dependencies during startup Key: JBOSGI-802 URL: https://issues.jboss.org/browse/JBOSGI-802 Project: JBoss OSGi Issue Type: Bug Environment: Wildfly 10.1, JBoss Modules 1.5.2.Final, JBoss OSGi 2.5.2 Final Reporter: Hannu Lahtinen Assignee: Arcadiy Ivanov Setup: - webapp.war has "Dependencies: deployment.OSGI_BUNDLE_A" defined in its MANIFEST.MF. - deployment.OSGI_BUNDLE_A has "Import-Package: foo.bar.osgi.bundle.b.path" in its MANIFEST.mf. - Standalone.xml has -- automatic deployment-scanner enabled -- OSGi bundles are eagerly started -- org.osgi.framework.startlevel.beginning is 2 -- OSGI_BUNDLE_A defined as a OSGi subsystem capability with startlevel=1. -- OSGI_BUNDLE_B defined as a OSGi subsystem capability with startlevel=1. - webapp.war is placed in deployments folder. When Wildfly is started deployment-scanner starts to deploy webapp.war and OSGi subsystem starts to install bundles and solve dependencies. OSGi subsystem logs on INFO level that bundle A and bundle B have been installed. At this point an ERROR is logged that informs that webapp.war failed to start due to an ModuleNotFoundException. deployment.OSGI_BUNDLE_B was not found. After this OSGi bundle A and B are started and Wildfly finishes starting up. At this point we can remove webapp.war.failed from deployments folder. Deployment scanner starts deploying webapp.war again. This time deployment succeeds without issues. All dependencies are resolved and system works without issues. This bug does not occur consistently. Sometimes webapp.war is deployed without issues when Wildfly is started. Also we can start Wildfly with the argument "-Djboss.msc.max.container.threads=1" and Wildfly always starts up cleanly (albeit slowly). This is highly simplified description of the scenario in which this bug occurs. In reality there are multiple WARs that are dependent on multiple OSGi bundles and those are dependent on multiple other OSGi bundles. Note that this has been mostly tested in an environment where every startup is on a "fresh" Wildfly installation. tmp and data directories have not been created and standalone.xml does not contain -tags. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 17 10:49:00 2016 From: issues at jboss.org (Hannu Lahtinen (JIRA)) Date: Mon, 17 Oct 2016 10:49:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-802) WAR deployments do not always manage to resolve OSGi dependencies during startup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hannu Lahtinen updated JBOSGI-802: ---------------------------------- Description: Originally discussion in thread: https://developer.jboss.org/thread/272591 Setup: - webapp.war has "Dependencies: deployment.OSGI_BUNDLE_A" defined in its MANIFEST.MF. - deployment.OSGI_BUNDLE_A has "Import-Package: foo.bar.osgi.bundle.b.path" in its MANIFEST.mf. - Standalone.xml has -- automatic deployment-scanner enabled -- OSGi bundles are eagerly started -- org.osgi.framework.startlevel.beginning is 2 -- OSGI_BUNDLE_A defined as a OSGi subsystem capability with startlevel=1. -- OSGI_BUNDLE_B defined as a OSGi subsystem capability with startlevel=1. - webapp.war is placed in deployments folder. When Wildfly is started deployment-scanner starts to deploy webapp.war and OSGi subsystem starts to install bundles and solve dependencies. OSGi subsystem logs on INFO level that bundle A and bundle B have been installed. At this point an ERROR is logged that informs that webapp.war failed to start due to an ModuleNotFoundException. deployment.OSGI_BUNDLE_B was not found. After this OSGi bundle A and B are started and Wildfly finishes starting up. At this point we can remove webapp.war.failed from deployments folder. Deployment scanner starts deploying webapp.war again. This time deployment succeeds without issues. All dependencies are resolved and system works without issues. This bug does not occur consistently. Sometimes webapp.war is deployed without issues when Wildfly is started. Also we can start Wildfly with the argument "-Djboss.msc.max.container.threads=1" and Wildfly always starts up cleanly (albeit slowly). This is highly simplified description of the scenario in which this bug occurs. In reality there are multiple WARs that are dependent on multiple OSGi bundles and those are dependent on multiple other OSGi bundles. Note that this has been mostly tested in an environment where every startup is on a "fresh" Wildfly installation. tmp and data directories have not been created and standalone.xml does not contain -tags. was: Setup: - webapp.war has "Dependencies: deployment.OSGI_BUNDLE_A" defined in its MANIFEST.MF. - deployment.OSGI_BUNDLE_A has "Import-Package: foo.bar.osgi.bundle.b.path" in its MANIFEST.mf. - Standalone.xml has -- automatic deployment-scanner enabled -- OSGi bundles are eagerly started -- org.osgi.framework.startlevel.beginning is 2 -- OSGI_BUNDLE_A defined as a OSGi subsystem capability with startlevel=1. -- OSGI_BUNDLE_B defined as a OSGi subsystem capability with startlevel=1. - webapp.war is placed in deployments folder. When Wildfly is started deployment-scanner starts to deploy webapp.war and OSGi subsystem starts to install bundles and solve dependencies. OSGi subsystem logs on INFO level that bundle A and bundle B have been installed. At this point an ERROR is logged that informs that webapp.war failed to start due to an ModuleNotFoundException. deployment.OSGI_BUNDLE_B was not found. After this OSGi bundle A and B are started and Wildfly finishes starting up. At this point we can remove webapp.war.failed from deployments folder. Deployment scanner starts deploying webapp.war again. This time deployment succeeds without issues. All dependencies are resolved and system works without issues. This bug does not occur consistently. Sometimes webapp.war is deployed without issues when Wildfly is started. Also we can start Wildfly with the argument "-Djboss.msc.max.container.threads=1" and Wildfly always starts up cleanly (albeit slowly). This is highly simplified description of the scenario in which this bug occurs. In reality there are multiple WARs that are dependent on multiple OSGi bundles and those are dependent on multiple other OSGi bundles. Note that this has been mostly tested in an environment where every startup is on a "fresh" Wildfly installation. tmp and data directories have not been created and standalone.xml does not contain -tags. > WAR deployments do not always manage to resolve OSGi dependencies during startup > -------------------------------------------------------------------------------- > > Key: JBOSGI-802 > URL: https://issues.jboss.org/browse/JBOSGI-802 > Project: JBoss OSGi > Issue Type: Bug > Environment: Wildfly 10.1, JBoss Modules 1.5.2.Final, JBoss OSGi 2.5.2 Final > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > > Originally discussion in thread: https://developer.jboss.org/thread/272591 > Setup: > - webapp.war has "Dependencies: deployment.OSGI_BUNDLE_A" defined in its MANIFEST.MF. > - deployment.OSGI_BUNDLE_A has "Import-Package: foo.bar.osgi.bundle.b.path" in its MANIFEST.mf. > - Standalone.xml has > -- automatic deployment-scanner enabled > -- OSGi bundles are eagerly started > -- org.osgi.framework.startlevel.beginning is 2 > -- OSGI_BUNDLE_A defined as a OSGi subsystem capability with startlevel=1. > -- OSGI_BUNDLE_B defined as a OSGi subsystem capability with startlevel=1. > - webapp.war is placed in deployments folder. > When Wildfly is started deployment-scanner starts to deploy webapp.war and OSGi subsystem starts to install bundles and solve dependencies. OSGi subsystem logs on INFO level that bundle A and bundle B have been installed. At this point an ERROR is logged that informs that webapp.war failed to start due to an ModuleNotFoundException. deployment.OSGI_BUNDLE_B was not found. After this OSGi bundle A and B are started and Wildfly finishes starting up. > At this point we can remove webapp.war.failed from deployments folder. Deployment scanner starts deploying webapp.war again. This time deployment succeeds without issues. All dependencies are resolved and system works without issues. > This bug does not occur consistently. Sometimes webapp.war is deployed without issues when Wildfly is started. Also we can start Wildfly with the argument "-Djboss.msc.max.container.threads=1" and Wildfly always starts up cleanly (albeit slowly). > This is highly simplified description of the scenario in which this bug occurs. In reality there are multiple WARs that are dependent on multiple OSGi bundles and those are dependent on multiple other OSGi bundles. > Note that this has been mostly tested in an environment where every startup is on a "fresh" Wildfly installation. tmp and data directories have not been created and standalone.xml does not contain -tags. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 23 22:05:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 23 Oct 2016 22:05:00 -0400 (EDT) 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 updated JBOSGI-800: ---------------------------------- Fix Version/s: JBossOSGI 2.5.3 > 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 (v6.4.11#64026) From issues at jboss.org Sun Oct 23 22:06:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 23 Oct 2016 22:06:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-802) WAR deployments do not always manage to resolve OSGi dependencies during startup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-802: ---------------------------------- Fix Version/s: JBossOSGI 2.5.3 > WAR deployments do not always manage to resolve OSGi dependencies during startup > -------------------------------------------------------------------------------- > > Key: JBOSGI-802 > URL: https://issues.jboss.org/browse/JBOSGI-802 > Project: JBoss OSGi > Issue Type: Bug > Environment: Wildfly 10.1, JBoss Modules 1.5.2.Final, JBoss OSGi 2.5.2 Final > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > > Originally discussion in thread: https://developer.jboss.org/thread/272591 > Setup: > - webapp.war has "Dependencies: deployment.OSGI_BUNDLE_A" defined in its MANIFEST.MF. > - deployment.OSGI_BUNDLE_A has "Import-Package: foo.bar.osgi.bundle.b.path" in its MANIFEST.mf. > - Standalone.xml has > -- automatic deployment-scanner enabled > -- OSGi bundles are eagerly started > -- org.osgi.framework.startlevel.beginning is 2 > -- OSGI_BUNDLE_A defined as a OSGi subsystem capability with startlevel=1. > -- OSGI_BUNDLE_B defined as a OSGi subsystem capability with startlevel=1. > - webapp.war is placed in deployments folder. > When Wildfly is started deployment-scanner starts to deploy webapp.war and OSGi subsystem starts to install bundles and solve dependencies. OSGi subsystem logs on INFO level that bundle A and bundle B have been installed. At this point an ERROR is logged that informs that webapp.war failed to start due to an ModuleNotFoundException. deployment.OSGI_BUNDLE_B was not found. After this OSGi bundle A and B are started and Wildfly finishes starting up. > At this point we can remove webapp.war.failed from deployments folder. Deployment scanner starts deploying webapp.war again. This time deployment succeeds without issues. All dependencies are resolved and system works without issues. > This bug does not occur consistently. Sometimes webapp.war is deployed without issues when Wildfly is started. Also we can start Wildfly with the argument "-Djboss.msc.max.container.threads=1" and Wildfly always starts up cleanly (albeit slowly). > This is highly simplified description of the scenario in which this bug occurs. In reality there are multiple WARs that are dependent on multiple OSGi bundles and those are dependent on multiple other OSGi bundles. > Note that this has been mostly tested in an environment where every startup is on a "fresh" Wildfly installation. tmp and data directories have not been created and standalone.xml does not contain -tags. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Oct 23 22:09:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 23 Oct 2016 22:09: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 ] Work on JBOSGI-803 started by Arcadiy Ivanov. --------------------------------------------- > 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 (v6.4.11#64026) From issues at jboss.org Sun Oct 23 22:09:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 23 Oct 2016 22:09:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-803) Upgrade dependencies to WildFly 10.1.0 In-Reply-To: References: Message-ID: Arcadiy Ivanov created JBOSGI-803: ------------------------------------- Summary: 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 (v6.4.11#64026) From issues at jboss.org Mon Oct 24 12:48:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 24 Oct 2016 12:48:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-802) WAR deployments do not always manage to resolve OSGi dependencies during startup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13310995#comment-13310995 ] Arcadiy Ivanov commented on JBOSGI-802: --------------------------------------- [~hannu1] FYI, I started JBOSGI-803 to upgrade to WildFly 10.1 and there are unit test failures in the repository processing with 2.5.2. It'll be fixed as part of JBOSGI-803, but you may be bumping into 10.1 issue. > WAR deployments do not always manage to resolve OSGi dependencies during startup > -------------------------------------------------------------------------------- > > Key: JBOSGI-802 > URL: https://issues.jboss.org/browse/JBOSGI-802 > Project: JBoss OSGi > Issue Type: Bug > Environment: Wildfly 10.1, JBoss Modules 1.5.2.Final, JBoss OSGi 2.5.2 Final > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > > Originally discussion in thread: https://developer.jboss.org/thread/272591 > Setup: > - webapp.war has "Dependencies: deployment.OSGI_BUNDLE_A" defined in its MANIFEST.MF. > - deployment.OSGI_BUNDLE_A has "Import-Package: foo.bar.osgi.bundle.b.path" in its MANIFEST.mf. > - Standalone.xml has > -- automatic deployment-scanner enabled > -- OSGi bundles are eagerly started > -- org.osgi.framework.startlevel.beginning is 2 > -- OSGI_BUNDLE_A defined as a OSGi subsystem capability with startlevel=1. > -- OSGI_BUNDLE_B defined as a OSGi subsystem capability with startlevel=1. > - webapp.war is placed in deployments folder. > When Wildfly is started deployment-scanner starts to deploy webapp.war and OSGi subsystem starts to install bundles and solve dependencies. OSGi subsystem logs on INFO level that bundle A and bundle B have been installed. At this point an ERROR is logged that informs that webapp.war failed to start due to an ModuleNotFoundException. deployment.OSGI_BUNDLE_B was not found. After this OSGi bundle A and B are started and Wildfly finishes starting up. > At this point we can remove webapp.war.failed from deployments folder. Deployment scanner starts deploying webapp.war again. This time deployment succeeds without issues. All dependencies are resolved and system works without issues. > This bug does not occur consistently. Sometimes webapp.war is deployed without issues when Wildfly is started. Also we can start Wildfly with the argument "-Djboss.msc.max.container.threads=1" and Wildfly always starts up cleanly (albeit slowly). > This is highly simplified description of the scenario in which this bug occurs. In reality there are multiple WARs that are dependent on multiple OSGi bundles and those are dependent on multiple other OSGi bundles. > Note that this has been mostly tested in an environment where every startup is on a "fresh" Wildfly installation. tmp and data directories have not been created and standalone.xml does not contain -tags. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 24 12:49:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 24 Oct 2016 12:49:00 -0400 (EDT) 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=13310996#comment-13310996 ] Arcadiy Ivanov commented on JBOSGI-800: --------------------------------------- [~satish.bhor] FYI, I started JBOSGI-803 to upgrade to WildFly 10.1 and there are unit test failures in the repository processing with 2.5.2. It'll be fixed as part of JBOSGI-803, but you may be bumping into 10.1 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 (v6.4.11#64026) From issues at jboss.org Tue Oct 25 01:21:00 2016 From: issues at jboss.org (Hannu Lahtinen (JIRA)) Date: Tue, 25 Oct 2016 01:21:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-802) WAR deployments do not always manage to resolve OSGi dependencies during startup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13311170#comment-13311170 ] Hannu Lahtinen commented on JBOSGI-802: --------------------------------------- Ok, thank you for the information. Currently, we circumvented the issue by deploying WARs after Wildfly has started. We will look to upgrade to 10.1 as soon as JBosgi has support for it. > WAR deployments do not always manage to resolve OSGi dependencies during startup > -------------------------------------------------------------------------------- > > Key: JBOSGI-802 > URL: https://issues.jboss.org/browse/JBOSGI-802 > Project: JBoss OSGi > Issue Type: Bug > Environment: Wildfly 10.1, JBoss Modules 1.5.2.Final, JBoss OSGi 2.5.2 Final > Reporter: Hannu Lahtinen > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.3 > > > Originally discussion in thread: https://developer.jboss.org/thread/272591 > Setup: > - webapp.war has "Dependencies: deployment.OSGI_BUNDLE_A" defined in its MANIFEST.MF. > - deployment.OSGI_BUNDLE_A has "Import-Package: foo.bar.osgi.bundle.b.path" in its MANIFEST.mf. > - Standalone.xml has > -- automatic deployment-scanner enabled > -- OSGi bundles are eagerly started > -- org.osgi.framework.startlevel.beginning is 2 > -- OSGI_BUNDLE_A defined as a OSGi subsystem capability with startlevel=1. > -- OSGI_BUNDLE_B defined as a OSGi subsystem capability with startlevel=1. > - webapp.war is placed in deployments folder. > When Wildfly is started deployment-scanner starts to deploy webapp.war and OSGi subsystem starts to install bundles and solve dependencies. OSGi subsystem logs on INFO level that bundle A and bundle B have been installed. At this point an ERROR is logged that informs that webapp.war failed to start due to an ModuleNotFoundException. deployment.OSGI_BUNDLE_B was not found. After this OSGi bundle A and B are started and Wildfly finishes starting up. > At this point we can remove webapp.war.failed from deployments folder. Deployment scanner starts deploying webapp.war again. This time deployment succeeds without issues. All dependencies are resolved and system works without issues. > This bug does not occur consistently. Sometimes webapp.war is deployed without issues when Wildfly is started. Also we can start Wildfly with the argument "-Djboss.msc.max.container.threads=1" and Wildfly always starts up cleanly (albeit slowly). > This is highly simplified description of the scenario in which this bug occurs. In reality there are multiple WARs that are dependent on multiple OSGi bundles and those are dependent on multiple other OSGi bundles. > Note that this has been mostly tested in an environment where every startup is on a "fresh" Wildfly installation. tmp and data directories have not been created and standalone.xml does not contain -tags. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 25 01:22:00 2016 From: issues at jboss.org (satish bhor (JIRA)) Date: Tue, 25 Oct 2016 01:22:00 -0400 (EDT) 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=13311172#comment-13311172 ] satish bhor commented on JBOSGI-800: ------------------------------------ [~arcivanov] Is there any patch or code change in 2.5.2 will fix this problem ? > 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 (v6.4.11#64026) From issues at jboss.org Tue Oct 25 01:43:00 2016 From: issues at jboss.org (satish bhor (JIRA)) Date: Tue, 25 Oct 2016 01:43:00 -0400 (EDT) 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=13311172#comment-13311172 ] satish bhor edited comment on JBOSGI-800 at 10/25/16 1:42 AM: -------------------------------------------------------------- [~arcivanov] I tested this on Wildfly 10.0.0.Final, it is reproducible. Is there any patch or code change in 2.5.2 will fix this problem ? was (Author: satish.bhor): [~arcivanov] Is there any patch or code change in 2.5.2 will fix this problem ? > 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 (v6.4.11#64026) From issues at jboss.org Tue Oct 25 22:27:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 25 Oct 2016 22:27:00 -0400 (EDT) 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=13311810#comment-13311810 ] Arcadiy Ivanov commented on JBOSGI-800: --------------------------------------- [~satish.bhor] Thanks for the info. Not yet, I'll update the status of the issue when I get to it. > 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.2#72004) From issues at jboss.org Tue Oct 25 22:31:01 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 25 Oct 2016 22:31:01 -0400 (EDT) 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=13311812#comment-13311812 ] Arcadiy Ivanov commented on JBOSGI-800: --------------------------------------- [~satish.bhor]Actually, I'm confused: {noformat} {"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"} {noformat} This means that the "undeployment" did not actually undeploy anything and you're trying to deploy this service again. Are you sure the undeploy is successful? > 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.2#72004) From issues at jboss.org Wed Oct 26 00:44:00 2016 From: issues at jboss.org (satish bhor (JIRA)) Date: Wed, 26 Oct 2016 00:44:00 -0400 (EDT) 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=13311917#comment-13311917 ] satish bhor commented on JBOSGI-800: ------------------------------------ [~arcivanov] undeployment was successful. Please ping below wildfly log of complete process I followed. You can also verify with attached source code. //////////////////////////////Deployed two bundles/////////////////////////////////////////// 10:10:06,242 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /home/satish/Downloads/wildfly-10.0.0.Final/standalone/data/content/81/bcc4d570b040b69e7b267b9992809200cd58b6/content 10:10:06,272 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "base-1.0.jar" (runtime-name: "base-1.0.jar") 10:10:06,536 INFO [org.jboss.osgi.framework] (MSC service thread 1-5) JBOSGI011001: Bundle installed: OSGI.base:1.0.0 10:10:06,701 INFO [org.jboss.osgi.framework] (MSC service thread 1-6) JBOSGI011002: Bundle started: OSGI.base:1.0.0 10:10:06,833 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "base-1.0.jar" (runtime-name : "base-1.0.jar") 10:10:07,426 INFO [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /home/satish/Downloads/wildfly-10.0.0.Final/standalone/data/content/57/498b7a7c57ec079372eb0f0e31540022b4cde8/content 10:10:07,430 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "dependent-1.0.jar" (runtime-name: "dependent-1.0.jar") 10:10:07,463 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: OSGI.dependent:1.0.0 10:10:07,492 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011002: Bundle started: OSGI.dependent:1.0.0 10:10:07,515 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "dependent-1.0.jar" (runtime-name : "dependent-1.0.jar") //////////////////////////////Undeployed Base bundle/////////////////////////////////////////// 10:10:27,512 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011003: Bundle stopped: OSGI.base:1.0.0 10:10:27,548 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-6) HV000001: Hibernate Validator 5.2.3.Final 10:10:27,605 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011005: Bundle uninstalled: OSGI.base:1.0.0 10:10:27,610 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment base-1.0.jar (runtime-name: base-1.0.jar) in 105ms 10:10:27,624 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0002: Content removed from location /home/satish/Downloads/wildfly-10.0.0.Final/standalone/data/content/81/bcc4d570b040b69e7b267b9992809200cd58b6/content 10:10:27,628 INFO [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0009: Undeployed "base-1.0.jar" (runtime-name: "base-1.0.jar") //////////////////////////////Redeployed Base bundle/////////////////////////////////////////// 10:10:47,437 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /home/satish/Downloads/wildfly-10.0.0.Final/standalone/data/content/0e/6bc6dd8139c584e49f8151b946adf9839f7ada/content 10:10:47,440 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "base-1.0.jar" (runtime-name: "base-1.0.jar") 10:10:47,463 INFO [org.jboss.osgi.framework] (MSC service thread 1-8) JBOSGI011001: Bundle installed: OSGI.base:1.0.0 10:10:47,468 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."base-1.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."base-1.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "base-1.0.jar" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) 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.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.base-1.0.jar".main is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) 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) ... 5 more 10:10:47,471 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "base-1.0.jar")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"base-1.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"base-1.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"base-1.0.jar\" Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.base-1.0.jar\".main is already registered"}} 10:10:47,472 ERROR [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0021: Deploy of deployment "base-1.0.jar" was rolled back with the following failure message: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"base-1.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"base-1.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"base-1.0.jar\" Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.base-1.0.jar\".main is already registered"}} 10:10:47,478 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011005: Bundle uninstalled: OSGI.base:1.0.0 10:10:47,481 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment base-1.0.jar (runtime-name: base-1.0.jar) in 9ms 10:10:47,483 INFO [org.jboss.osgi.framework] (MSC service thread 1-6) JBOSGI011003: Bundle stopped: OSGI.dependent:1.0.0 10:10:47,492 INFO [org.jboss.as.controller] (management-handler-thread - 4) WFLYCTL0183: Service status report WFLYCTL0184: New missing/unsatisfied dependencies: service jboss.module.spec.service."deployment.base-1.0.jar".main (missing) dependents: [service jboss.module.service."deployment.dependent-1.0.jar".main] WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."base-1.0.jar".CONFIGURE_MODULE > 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.2#72004) From issues at jboss.org Wed Oct 26 00:46:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Wed, 26 Oct 2016 00:46:00 -0400 (EDT) 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=13311918#comment-13311918 ] Arcadiy Ivanov commented on JBOSGI-800: --------------------------------------- [~satish.bhor]thanks! > 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.2#72004)