[JBoss JIRA] (WFLY-843) Cannot restart webapp bundle after activation failure
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-843?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler resolved WFLY-843.
---------------------------------
Resolution: Won't Fix
Won't Fix - OSGi is going to get removed
> Cannot restart webapp bundle after activation failure
> -----------------------------------------------------
>
> Key: WFLY-843
> URL: https://issues.jboss.org/browse/WFLY-843
> Project: WildFly
> Issue Type: Bug
> Components: OSGi
> Reporter: Thomas Diesler
>
> {code}
> Caused by: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.as.connector.deployers.ra.processors.CachedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.setup(CachedConnectionManagerSetupProcessor.java:74)
> at org.jboss.as.web.ThreadSetupBindingListener.bind(ThreadSetupBindingListener.java:50)
> at org.apache.catalina.core.StandardContext.bindThread(StandardContext.java:4234)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3740)
> at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:102)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (WFLY-787) Cannot restart jpa bundle after activation failure
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-787?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler resolved WFLY-787.
---------------------------------
Resolution: Won't Fix
Won't Fix - OSGi is going to get removed
> Cannot restart jpa bundle after activation failure
> --------------------------------------------------
>
> Key: WFLY-787
> URL: https://issues.jboss.org/browse/WFLY-787
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate, OSGi
> Reporter: Thomas Diesler
>
> {code}
> Caused by: java.lang.IllegalStateException: JBAS014666: Duplicate resource persistence-bundle-b.jar#simple-persistence
> at org.jboss.as.controller.registry.AbstractModelResource$DefaultResourceProvider.register(AbstractModelResource.java:225)
> at org.jboss.as.controller.registry.AbstractModelResource.registerChild(AbstractModelResource.java:135)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addManagementConsole(PersistenceUnitServiceHandler.java:727)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deployPersistenceUnit(PersistenceUnitServiceHandler.java:406)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addPuService(PersistenceUnitServiceHandler.java:274)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.handleJarDeployment(PersistenceUnitServiceHandler.java:142)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deploy(PersistenceUnitServiceHandler.java:117)
> at org.jboss.as.jpa.processor.PersistenceCompleteInstallProcessor.deploy(PersistenceCompleteInstallProcessor.java:48)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (WFLY-1557) DuplicateServiceException on undertow deployment replace
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-1557?page=com.atlassian.jira.plugin.... ]
Thomas Diesler resolved WFLY-1557.
----------------------------------
Resolution: Won't Fix
Won't Fix - OSGi is going to get removed
> DuplicateServiceException on undertow deployment replace
> --------------------------------------------------------
>
> Key: WFLY-1557
> URL: https://issues.jboss.org/browse/WFLY-1557
> Project: WildFly
> Issue Type: Bug
> Components: OSGi, Web (Undertow)
> Reporter: Thomas Diesler
> Assignee: Stuart Douglas
> Fix For: 8.0.0.Alpha3
>
>
> {code}
> 07:21:52,095 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "webapp-v101.wab" (runtime-name: "webapp-v101.wab")
> 07:21:52,119 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001: Bundle installed: webapp-v101.wab:1.0.1
> 07:21:52,119 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS018224: Unregister web context: /simple-bundle
> 07:21:52,119 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011003: Bundle stopped: webapp-v100.wab:1.0.0
> 07:21:52,124 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."webapp-v101.wab".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."webapp-v101.wab".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "webapp-v101.wab"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1942) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1875) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.undertow.deployment.default-host./simple-bundle.UndertowDeploymentInfoService is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2382) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2382) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentProcessor.processDeployment(UndertowDeploymentProcessor.java:235)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentProcessor.deploy(UndertowDeploymentProcessor.java:102)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> {code}
> http://teamcity.cafe-babe.org/viewLog.html?buildId=5380&tab=buildResultsD...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (WFLY-1125) Karaf configuration through ConfigAdmin
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-1125?page=com.atlassian.jira.plugin.... ]
Thomas Diesler resolved WFLY-1125.
----------------------------------
Resolution: Won't Fix
Won't Fix - OSGi is going to get removed
> Karaf configuration through ConfigAdmin
> ---------------------------------------
>
> Key: WFLY-1125
> URL: https://issues.jboss.org/browse/WFLY-1125
> Project: WildFly
> Issue Type: Feature Request
> Components: OSGi
> Reporter: Thomas Diesler
>
> Currently we add these props to standalone.conf
> {code}
> -Dkaraf.home=.../jboss-as-karaf-7.2.0.Alpha1-SNAPSHOT/standalone/data/karaf -Dkaraf.base=.../jboss-as-karaf-7.2.0.Alpha1-SNAPSHOT/standalone/data/karaf -Dkaraf.startRemoteShell=true -Dkaraf.startLocalConsole=false
> {code}
> For this we should have sensible defaults as well as make the SSH port (and possibly other options) configurable through ConfigAdmin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (WFLY-1233) Decouple naming & transaction from OSGi
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-1233?page=com.atlassian.jira.plugin.... ]
Thomas Diesler resolved WFLY-1233.
----------------------------------
Resolution: Won't Fix
Won't Fix - OSGi is going to get removed
> Decouple naming & transaction from OSGi
> ---------------------------------------
>
> Key: WFLY-1233
> URL: https://issues.jboss.org/browse/WFLY-1233
> Project: WildFly
> Issue Type: Task
> Components: OSGi
> Reporter: Thomas Diesler
>
> Currently the naming & transaction subsystem register services on behalf of OSGi
> {code}
> [tdiesler@tdvaio jboss-as]$ git grep "\"xservice\""
> naming/src/main/java/org/jboss/as/naming/subsystem/NamingSubsystemOSGiService.java: ServiceName serviceName = ServiceName.of("jbosgi", "xservice", regi
> transactions/src/main/java/org/jboss/as/txn/service/TransactionManagerService.java: serviceBuilder.addAliases(ServiceName.of("jbosgi", "xservice", Tran
> transactions/src/main/java/org/jboss/as/txn/service/UserTransactionService.java: serviceBuilder.addAliases(ServiceName.of("jbosgi", "xservice", UserTra
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (WFLY-1258) Http Service TCK testBundleStopping() failing
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-1258?page=com.atlassian.jira.plugin.... ]
Thomas Diesler resolved WFLY-1258.
----------------------------------
Resolution: Won't Fix
Won't Fix - OSGi is going to get removed
> Http Service TCK testBundleStopping() failing
> ---------------------------------------------
>
> Key: WFLY-1258
> URL: https://issues.jboss.org/browse/WFLY-1258
> Project: WildFly
> Issue Type: Sub-task
> Components: OSGi
> Reporter: David Bosschaert
>
> The OSGi HTTP Service TCK test testBundleStopping() fails with the following exception:
> {code}org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: tb1:4.2.0
> at org.jboss.osgi.framework.internal.DefaultBundleLifecycleHandler.start(DefaultBundleLifecycleHandler.java:110)
> at org.jboss.as.osgi.service.BundleLifecycleIntegration.start(BundleLifecycleIntegration.java:181)
> at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:292)
> at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:228)
> at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:522)
> at org.jboss.as.osgi.deployment.BundleActivateProcessor$BundleActivateService.start(BundleActivateProcessor.java:127)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: java.lang.LinkageError: loader constraint violation: when resolving interface method "org.osgi.service.http.HttpService.registerServlet(Ljava/lang/String;Ljavax/servlet/Servlet;Ljava/util/Dictionary;Lorg/osgi/service/http/HttpContext;)V" the class loader (instance of org/jboss/osgi/framework/internal/HostBundleClassLoader) of the current class, org/osgi/test/cases/http/tb1/HttpTestBundle2, and the class loader (instance of org/jboss/modules/ModuleClassLoader) for resolved class, org/osgi/service/http/HttpService, have different Class objects for the type javax/servlet/Servlet used in the signature
> at org.osgi.test.cases.http.tb1.HttpTestBundle2.start(HttpTestBundle2.java:30)
> at org.jboss.osgi.framework.internal.DefaultBundleLifecycleHandler.start(DefaultBundleLifecycleHandler.java:84)
> ... 10 more{code}
> Seems like a resolution error, it could be related to how the TCK is set up.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years