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

[JBoss JIRA] (JBOSGI-793) Can't deploy wab fragment

by Roman Smushkevich (JIRA)

Roman Smushkevich created JBOSGI-793: ---------------------------------------- Summary: Can't deploy wab fragment Key: JBOSGI-793 URL: https://issues.jboss.org/browse/JBOSGI-793 Project: JBoss OSGi Issue Type: Bug Components: wildfly Affects Versions: JBossOSGI 2.5.0 Reporter: Roman Smushkevich Assignee: Arcadiy Ivanov If you try to deploy a wab fragment to already deployed wab comes exception: {code:java} 00:26:42,178 INFO [org.jboss.osgi.framework] (MSC service thread 1-7) JBOSGI011001: Bundle installed: com.mrs.budget.portal:1.0.0 00:26:42,180 INFO [org.jboss.osgi.framework] (MSC service thread 1-8) JBOSGI011001: Bundle installed: com.mrs.budget.portal.resources:1.0.0 00:26:50,267 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."com.mrs.budget.portal.resources.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."com.mrs.budget.portal.resources.jar".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "com.mrs.budget.portal.resources.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: java.lang.NullPointerException at org.jboss.as.webservices.deployers.WSClassVerificationProcessor.deploy(WSClassVerificationProcessor.java:75) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) ... 5 more 00:26:55,362 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0021: Registered web context: /budget 00:26:55,374 INFO [org.jboss.osgi.framework] (MSC service thread 1-8) JBOSGI011002: Bundle started: com.mrs.budget.portal:1.0.0 00:26:55,376 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "com.mrs.budget.portal.resources.jar")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"com.mrs.budget.portal.resources.jar\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"com.mrs.budget.portal.resources.jar\".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"com.mrs.budget.portal.resources.jar\" Caused by: java.lang.NullPointerException"}} 00:26:55,393 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "com.mrs.budget.portal.resources.jar" (runtime-name : "com.mrs.budget.portal.resources.jar") 00:26:55,394 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "com.mrs.budget.portal.jar" (runtime-name : "com.mrs.budget.portal.jar") 00:26:55,397 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."com.mrs.budget.portal.resources.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."com.mrs.budget.portal.resources.jar".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "com.mrs.budget.portal.resources.jar" {code} Debugging showd, that the deployment of wab Fragment tryes to pass through WS verification, that needs a deployment unit module: {code:java} @Override public void deploy(DeploymentPhaseContext phaseContext) throws DeploymentUnitProcessingException { final DeploymentUnit unit = phaseContext.getDeploymentUnit(); final JAXWSDeployment wsDeployment = unit.getAttachment(JAXWS_ENDPOINTS_KEY); if (wsDeployment != null) { final Module module = unit.getAttachment(Attachments.MODULE); final DeploymentReflectionIndex deploymentReflectionIndex = unit .getAttachment(org.jboss.as.server.deployment.Attachments.REFLECTION_INDEX); final ClassLoader moduleClassLoader = module.getClassLoader(); for (AbstractEndpoint pojoEndpoint : wsDeployment.getPojoEndpoints()) { verifyEndpoint(pojoEndpoint, moduleClassLoader, deploymentReflectionIndex); } for (AbstractEndpoint ejbEndpoint : wsDeployment.getEjbEndpoints()) { verifyEndpoint(ejbEndpoint, moduleClassLoader, deploymentReflectionIndex); } verifyApacheCXFModuleDependencyRequirement(unit); } } {code} but according to ModelManager - fragment is not a module -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs

by Arcadiy Ivanov (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin... ] Arcadiy Ivanov resolved JBOSGI-792. ----------------------------------- Fix Version/s: JBossOSGI 2.5.1 JBossOSGI 2.4.1 Resolution: Done > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.1, JBossOSGI 2.4.1 > > Attachments: pom.xml, server.log > > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs

by Arcadiy Ivanov (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin... ] Arcadiy Ivanov updated JBOSGI-792: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi/pull/20, https://github.com/jbosgi/jbosgi/pull/21 (was: https://github.com/jbosgi/jbosgi/pull/18) > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > Attachments: pom.xml, server.log > > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs

by Sander Stoel (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin... ] Sander Stoel commented on JBOSGI-792: ------------------------------------- Added PR > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > Attachments: pom.xml, server.log > > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs

by Sander Stoel (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin... ] Sander Stoel updated JBOSGI-792: -------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi/pull/18 > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > Attachments: pom.xml, server.log > > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs

by Sander Stoel (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin... ] Sander Stoel updated JBOSGI-792: -------------------------------- Attachment: server.log pom.xml A test pom.xml and the resulting server.log This is triggered by following the steps to reproduce. I have not been able to create an automated test unfortunately > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > Attachments: pom.xml, server.log > > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs

by Arcadiy Ivanov (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin... ] Arcadiy Ivanov commented on JBOSGI-792: --------------------------------------- Certainly. Thanks! > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs

by Sander Stoel (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin... ] Sander Stoel commented on JBOSGI-792: ------------------------------------- It would require me to filter a lot our data from that, is it also ok if I attach a test case once I'm ready? > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs

by Arcadiy Ivanov (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin... ] Arcadiy Ivanov commented on JBOSGI-792: --------------------------------------- Also, if you're submitting a PR, could you please make sure it is contained in a feature branch and not master. Thanks a lot! > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs

by Sander Stoel (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin... ] Sander Stoel updated JBOSGI-792: -------------------------------- Description: If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. {code} [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" [Server:server] ], [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { [Server:server] "Services that were unable to start:" => [ [Server:server] "jbosgi.SystemBundle", [Server:server] "jbosgi.SystemContext", [Server:server] "jbosgi.framework.ACTIVE", [Server:server] "jbosgi.framework.INIT", [Server:server] "jbosgi.internal.framework.ACTIVE" [Server:server] ], {code} While this is in domain mode it also occurs in standalone mode was: If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. {code} [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" [Server:server] ], [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { [Server:server] "Services that were unable to start:" => [ [Server:server] "jbosgi.SystemBundle", [Server:server] "jbosgi.SystemContext", [Server:server] "jbosgi.framework.ACTIVE", [Server:server] "jbosgi.framework.INIT", [Server:server] "jbosgi.internal.framework.ACTIVE" [Server:server] ], {code} > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues April 2016