[JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-805?page=com.atlassian.jira.plugin... ]
Work on JBOSGI-805 started by Arcadiy Ivanov.
---------------------------------------------
> ConcurrentModificationException from AbstractWiring when loading a dynamically imported class
> ---------------------------------------------------------------------------------------------
>
> Key: JBOSGI-805
> URL: https://issues.jboss.org/browse/JBOSGI-805
> Project: JBoss OSGi
> Issue Type: Feature Request
> Components: framework, resolver
> Affects Versions: JBossOSGI 2.5.2
> Reporter: Hannu Lahtinen
> Assignee: Arcadiy Ivanov
>
> {code}
> java.util ConcurrentModificationException
> at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102]
> at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102]
> at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120)
> at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165)
> at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final]
> ...
> {code}
> Steps that cause the exception to occur:
> 1. bundle with DIP: * in MANIFEST.
> 2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically.
> This exception is timing based and does not happen every time but in our environment happens about 20% of the time.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBOSGI-805) ConcurrentModificationException from AbstractWiring when loading a dynamically imported class
by Hannu Lahtinen (JIRA)
Hannu Lahtinen created JBOSGI-805:
-------------------------------------
Summary: ConcurrentModificationException from AbstractWiring when loading a dynamically imported class
Key: JBOSGI-805
URL: https://issues.jboss.org/browse/JBOSGI-805
Project: JBoss OSGi
Issue Type: Feature Request
Components: framework, resolver
Affects Versions: JBossOSGI 2.5.2
Reporter: Hannu Lahtinen
Assignee: Arcadiy Ivanov
{code}
java.util ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) [rt.jar:1.8.0_102]
at java.util.ArrayList$Itr.next(ArrayList.java:851) [rt.jar:1.8.0_102]
at org.jboss.osgi.resolver.spi.AbstractWiring.addProvidedWire(AbstractWiring.java:120)
at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal (FallbackLoader.java:165)
at org.jboss.modules.Module.loadModuleClass(Module.java:613) [jboss-modules.jar:1.5.1.Final]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.5.1.Final]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) [jboss-modules.jar:1.5.1.Final]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) [jboss-modules.jar:1.5.1.Final]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) [jboss-modules.jar:1.5.1.Final]
...
{code}
Steps that cause the exception to occur:
1. bundle with DIP: * in MANIFEST.
2. 2 different threads call above mentioned bundle with the same class that needs to be imported dynamically.
This exception is timing based and does not happen every time but in our environment happens about 20% of the time.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[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
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin... ]
Arcadiy Ivanov edited comment on JBOSGI-800 at 11/16/16 6:27 AM:
-----------------------------------------------------------------
[~satish.bhor] Here's the deal. Yes, generally when you undeploy this is what will happen. However when you undeploy *base* without undeploying *dependent*, what happens is that *dependent* is still running and is still using classes from *base*. The current behavior undeploys the *base* bundle and the module with the bundle revision is hanging in the limbo +until it stops being used+, in which case it is undeployed for good. The reason you're experiencing this behavior, is because you're undeploying the bundle that has dependencies.
So my question is: do you want *dependent* to be undeployed too? Or stopped? Or something else?
I'll see what the prescribed behavior is by OSGi specification (if any), but there is also an issue of WildFly container to consider.
was (Author: arcivanov):
[~satish.bhor]Here's the deal. Yes, generally when you undeploy this is what will happen. However when you undeploy *base* without undeploying *dependent*, what happens is that *dependent* is still running and is still using classes from *base*. The current behavior undeploys the *base* bundle and the module with the bundle revision is hanging in the limbo +until it stops being used+, in which case it is undeployed for good. The reason you're experiencing this behavior, is because you're undeploying the bundle that has dependencies.
So my question is: do you want *dependent* to be undeployed too? Or stopped? Or something else?
I'll see what the prescribed behavior is by OSGi specification (if any), but there is also an issue of WildFly container to consider.
> On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBOSGI-800
> URL: https://issues.jboss.org/browse/JBOSGI-800
> Project: JBoss OSGi
> Issue Type: Bug
> Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04
> Reporter: satish bhor
> Assignee: Arcadiy Ivanov
> Fix For: JBossOSGI 2.5.3
>
> Attachments: OSGI.zip
>
>
> There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error.
> 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91]
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208)
> at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325)
> at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109)
> at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81)
> at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> ... 5 more
> 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\"
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> }
> 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message:
> {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\"
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"],
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[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
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin... ]
Arcadiy Ivanov edited comment on JBOSGI-800 at 11/16/16 6:24 AM:
-----------------------------------------------------------------
[~satish.bhor]Here's the deal. Yes, generally when you undeploy this is what will happen. However when you undeploy *base* without undeploying *dependent*, what happens is that *dependent* is still running and is still using classes from *base*. The current behavior undeploys the *base* bundle and the module with the bundle revision is hanging in the limbo +until it stops being used+, in which case it is undeployed for good. The reason you're experiencing this behavior, is because you're undeploying the bundle that has dependencies.
So my question is: do you want *dependent* to be undeployed too? Or stopped? Or something else?
I'll see what the prescribed behavior is by OSGi specification (if any), but there is also an issue of WildFly container to consider.
was (Author: arcivanov):
[~satish.bhor]Here's the deal. Yes, generally when you undeploy this is what will happen. However when you undeploy *base* without undeploying *dependent*, what happens is that *dependent* is still running and is still using classes from *base*. The current behavior undeploys the *base* bundle and the module with the bundle revision is hanging in the limbo +until it stops being used+, in which case it is undeployed for good. The reason you're experiencing this behavior, is because you're undeploying the bundle that has dependencies.
I'll see what the prescribed behavior is by OSGi specification, but there is also an issue of WildFly container to consider.
> On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBOSGI-800
> URL: https://issues.jboss.org/browse/JBOSGI-800
> Project: JBoss OSGi
> Issue Type: Bug
> Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04
> Reporter: satish bhor
> Assignee: Arcadiy Ivanov
> Fix For: JBossOSGI 2.5.3
>
> Attachments: OSGI.zip
>
>
> There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error.
> 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91]
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208)
> at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325)
> at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109)
> at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81)
> at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> ... 5 more
> 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\"
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> }
> 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message:
> {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\"
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"],
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[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
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin... ]
Arcadiy Ivanov commented on JBOSGI-800:
---------------------------------------
[~satish.bhor]Here's the deal. Yes, generally when you undeploy this is what will happen. However when you undeploy *base* without undeploying *dependent*, what happens is that *dependent* is still running and is still using classes from *base*. The current behavior undeploys the *base* bundle and the module with the bundle revision is hanging in the limbo +until it stops being used+, in which case it is undeployed for good. The reason you're experiencing this behavior, is because you're undeploying the bundle that has dependencies.
I'll see what the prescribed behavior is by OSGi specification, but there is also an issue of WildFly container to consider.
> On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBOSGI-800
> URL: https://issues.jboss.org/browse/JBOSGI-800
> Project: JBoss OSGi
> Issue Type: Bug
> Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04
> Reporter: satish bhor
> Assignee: Arcadiy Ivanov
> Fix For: JBossOSGI 2.5.3
>
> Attachments: OSGI.zip
>
>
> There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error.
> 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91]
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208)
> at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325)
> at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109)
> at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81)
> at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> ... 5 more
> 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\"
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> }
> 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message:
> {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\"
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"],
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[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
by satish bhor (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin... ]
satish bhor commented on JBOSGI-800:
------------------------------------
[~arcivanov] I was expecting when it shows in logs as base bundle gets undeployed it should be undeployed ? Is this behavior according to osgi specification ?
> On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBOSGI-800
> URL: https://issues.jboss.org/browse/JBOSGI-800
> Project: JBoss OSGi
> Issue Type: Bug
> Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04
> Reporter: satish bhor
> Assignee: Arcadiy Ivanov
> Fix For: JBossOSGI 2.5.3
>
> Attachments: OSGI.zip
>
>
> There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error.
> 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91]
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208)
> at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325)
> at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109)
> at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81)
> at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> ... 5 more
> 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\"
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> }
> 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message:
> {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\"
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"],
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[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
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin... ]
Arcadiy Ivanov commented on JBOSGI-800:
---------------------------------------
[~satish.bhor] bump?
> On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBOSGI-800
> URL: https://issues.jboss.org/browse/JBOSGI-800
> Project: JBoss OSGi
> Issue Type: Bug
> Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04
> Reporter: satish bhor
> Assignee: Arcadiy Ivanov
> Fix For: JBossOSGI 2.5.3
>
> Attachments: OSGI.zip
>
>
> There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error.
> 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91]
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208)
> at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325)
> at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109)
> at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81)
> at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> ... 5 more
> 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\"
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> }
> 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message:
> {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\"
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"],
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[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
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin... ]
Arcadiy Ivanov commented on JBOSGI-800:
---------------------------------------
[~satish.bhor] Here's the deal. When you undeploy the OSGI.base without stopping OSGI.dependent first, the base.jar gets essentially scheduled for undeployment but is not undeployed, since it's still in use (see WFLY-150) until the dependent is stopped too.
What would, in your mind, be a desirable behavior?
> On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBOSGI-800
> URL: https://issues.jboss.org/browse/JBOSGI-800
> Project: JBoss OSGi
> Issue Type: Bug
> Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04
> Reporter: satish bhor
> Assignee: Arcadiy Ivanov
> Fix For: JBossOSGI 2.5.3
>
> Attachments: OSGI.zip
>
>
> There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error.
> 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91]
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208)
> at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325)
> at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109)
> at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81)
> at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> ... 5 more
> 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\"
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> }
> 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message:
> {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\"
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"],
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[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
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-800?page=com.atlassian.jira.plugin... ]
Work on JBOSGI-800 started by Arcadiy Ivanov.
---------------------------------------------
> On Redeploy of osgi bundle getting DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBOSGI-800
> URL: https://issues.jboss.org/browse/JBOSGI-800
> Project: JBoss OSGi
> Issue Type: Bug
> Environment: JBOSSOSGI 2.5.2.Final, apache felix as dependency manager,Wildfly-10.1.0.Final with openjdk 1.8 on ubuntu 16.04
> Reporter: satish bhor
> Assignee: Arcadiy Ivanov
> Fix For: JBossOSGI 2.5.3
>
> Attachments: OSGI.zip
>
>
> There are two osgi bundles base bundle and dependent bundle. When I undeploy base bundle it works fine without any error but when I tried it redeploy application it throwing below error.
> 12:48:48,807 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basebundle-1.0.0.jar".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment "basebundle-1.0.0.jar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91]
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service."deployment.basebundle-1.0.0.jar".main is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.as.osgi.service.ModuleLoaderIntegration$FrameworkModuleLoaderImpl.addModuleSpec(ModuleLoaderIntegration.java:208)
> at org.jboss.osgi.framework.internal.ModuleManagerImpl.createHostModule(ModuleManagerImpl.java:325)
> at org.jboss.osgi.framework.internal.ModuleManagerImpl.addModule(ModuleManagerImpl.java:207)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.addModules(FrameworkResolverImpl.java:304)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.applyResolverResults(FrameworkResolverImpl.java:249)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveInternal(FrameworkResolverImpl.java:164)
> at org.jboss.osgi.framework.internal.FrameworkResolverImpl.resolveAndApply(FrameworkResolverImpl.java:109)
> at org.jboss.as.osgi.deployment.BundleResolveProcessor.resolveBundle(BundleResolveProcessor.java:81)
> at org.jboss.as.osgi.deployment.BundleResolveProcessor.deploy(BundleResolveProcessor.java:68)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> ... 5 more
> 12:48:48,841 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "basebundle-1.0.0.jar")]) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\"
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> }
> 12:48:48,842 ERROR [org.jboss.as.server] (management-handler-thread - 9) WFLYSRV0021: Deploy of deployment "basebundle-1.0.0.jar" was rolled back with the following failure message:
> {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE: WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"basebundle-1.0.0.jar\"
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.module.spec.service.\"deployment.basebundle-1.0.0.jar\".main is already registered"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"basebundle-1.0.0.jar\".CONFIGURE_MODULE"],
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBOSGI-798) WildFly Framework Lock integration uses incorrect locking
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-798?page=com.atlassian.jira.plugin... ]
Arcadiy Ivanov closed JBOSGI-798.
---------------------------------
Resolution: Done
> WildFly Framework Lock integration uses incorrect locking
> ---------------------------------------------------------
>
> Key: JBOSGI-798
> URL: https://issues.jboss.org/browse/JBOSGI-798
> Project: JBoss OSGi
> Issue Type: Bug
> Components: wildfly
> Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0, JBossOSGI 2.5.1, JBossOSGI 2.4.1, JBossOSGI 2.5.2, JBossOSGI 2.4.2
> Reporter: Arcadiy Ivanov
> Assignee: Arcadiy Ivanov
> Priority: Minor
> Fix For: JBossOSGI 2.5.3
>
>
> # WildFly LockManagerIntegration should synchronize on a delegate and not self.
> # The skipLocking and delegate.lockItems should be under the same delegate synchronization to prevent a potential race.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months